Geow

I've tried different Redis images (just in case) but still have the same problem; That is, everything works fine initially, then when I come back to it the following day it no longer works. Paperless correctly detects a new file in the watch folder and the log shows it has added it to the task queue, but nothing else happens unless I restart the paperless-ng container. I do not need to restart the redis container to get it working again, just the paperless-ng one. Has anyone found a solution for this? TIA

The thing is, the redis connection works initially, and again if you restart the paperless-ng container (no need to restart redis).

Hi all, This works perfectly after setup, but then when I come back to it the following day it will not consume new documents. I can see an entry in the paperless-ng logs showing it detected the new file and says it has added it to the task queue, but nothing more happens, unless I restart the container. Any ideas? Thanks, G UPDATE: It seems the issue is with connecting to Redis. The Paperless-ng container logs are filed with: [Q] ERROR Error 111 connecting to 10.0.0.90:6379. Connection refused. The Redis container logs show: WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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. but not sure if relevant. TIA