-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cvat_redis_inmem restart loop #8892
Comments
Forgot to attach the output of
|
Hi, I think some of the redis files might be corrupted because of the system restarts. Have you tried following this message: |
@zhiltsov-max thanks for looking into this
I tried running
and then, inside the container
So I don't know how to follow that message unfortunately! |
Have you tried to remove the volume? |
I did run |
Actions before raising this issue
Steps to Reproduce
Download cvat
Run it for an undefinite time and reboot your machine. For some reason, now I do get the error (it;s not the first time I reboot the machine though)
Output of
docker logs cvat_redis_inmem
1:C 30 Dec 2024 15:17:12.930 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see jemalloc/jemalloc#1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 30 Dec 2024 15:17:12.930 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 30 Dec 2024 15:17:12.930 * Redis version=7.2.3, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 30 Dec 2024 15:17:12.930 * Configuration loaded
1:M 30 Dec 2024 15:17:12.930 * monotonic clock: POSIX clock_gettime
1:M 30 Dec 2024 15:17:12.931 * Running mode=standalone, port=6379.
1:M 30 Dec 2024 15:17:12.932 * Server initialized
1:M 30 Dec 2024 15:17:12.932 * Reading RDB base file on AOF loading...
1:M 30 Dec 2024 15:17:12.932 * Loading RDB produced by version 7.2.3
1:M 30 Dec 2024 15:17:12.932 * RDB age 1554244 seconds
1:M 30 Dec 2024 15:17:12.932 * RDB memory usage when created 1.80 Mb
1:M 30 Dec 2024 15:17:12.932 * RDB is base AOF
1:M 30 Dec 2024 15:17:12.932 * Done loading RDB, keys loaded: 33, keys expired: 0.
1:M 30 Dec 2024 15:17:12.932 * DB loaded from base file appendonly.aof.6.base.rdb: 0.000 seconds
1:M 30 Dec 2024 15:17:13.206 # Bad file format reading the append only file appendonly.aof.6.incr.aof: make a backup of your AOF file, then use ./redis-check-aof --fix <filename.manifest>
Expected Behavior
No response
Possible Solution
Stop cvat with
docker-compose down
Comment out the custom command under
cvat_redis_inmem
in the docker compose file.I have no idea what are the repercussions of not running the custom command. But it seems commenting it makes cvat works again. I would like to have confirmation to be sure.
docker-compose up -d
Context
I am unable to use cvat because work is not being saved anymore and I get an error notification in the GUI
Environment
The text was updated successfully, but these errors were encountered: