OCR my PDF Error Messages

Hello,

i have many PDf Files on my Sever and would these files Scan. But i get a lot of messages in the personal backend.

M__ller1 001.jpg	FAILED	ENOENT: no such file or directory, unlink '/home/node/output/ocr_UtczFf.pdf'		
Löschen
Scan_20150311.png	FAILED	ENOENT: no such file or directory, unlink '/home/node/output/ocr_GcutkA.pdf'		
Löschen
M__ller 001.jpg	FAILED	ENOENT: no such file or directory, unlink '/home/node/output/ocr_6NEi9U.pdf'		
Löschen
Kündigung M-net.pdf	FAILED	The execution of 'ocrmypdf' command failed: INFO - 1: page has no images - skipping all processing on this page ERROR - Traceback (most recent call last): File "/usr/lib/python3/dist-packages/ruffus/task.py", line 751, in run_pooled_job_without_exceptions register_cleanup, touch_files_only) File "/usr/lib/python3/dist-packages/ruffus/task.py", line 567, in job_wrapper_io_files ret_val = user_defined_work_func(*params) File "/usr/lib/python3/dist-packages/ocrmypdf/__main__.py",		
Löschen
Maler_kullmann.pdf	FAILED	The execution of 'ocrmypdf' command failed: WARNING - 1: [tesseract] unsure about page orientation ERROR - Traceback (most recent call last): File "/usr/lib/python3/dist-packages/ruffus/task.py", line 751, in run_pooled_job_without_exceptions register_cleanup, touch_files_only) File "/usr/lib/python3/dist-packages/ruffus/task.py", line 567, in job_wrapper_io_files ret_val = user_defined_work_func(*params) File "/usr/lib/python3/dist-packages/ocrmypdf/__main__.py", line 1354, i		
Löschen
Scan_20150218.png	FAILED	ENOENT: no such file or directory, unlink '/home/node/output/ocr_KZZaXW.pdf'

What is wrong with it?

Did you install the docker containers @Lars_M?

Yes, but I Stuck now here https://github.com/janis91/ocr/issues/157

What does the docker logs of those 2 containers (redis and ocr worker container) say?

docker ps -a

docker log XXXXXXXXXXXX
docker log YYYYYYYYYYYY

Experiencing the same issue.

Redis Container Log

1:C 11 May 08:51:32.002 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 11 May 08:51:32.002 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 11 May 08:51:32.002 # Configuration loaded
1:M 11 May 08:51:32.005 * Running mode=standalone, port=6379.
1:M 11 May 08:51:32.005 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 11 May 08:51:32.005 # Server initialized
1:M 11 May 08:51:32.005 # 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.
1:M 11 May 08:51:32.005 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 11 May 08:51:32.005 * Ready to accept connections
1:M 11 May 08:59:35.789 * 10 changes in 300 seconds. Saving…
1:M 11 May 08:59:35.789 * Background saving started by pid 13
13:C 11 May 08:59:35.934 * DB saved on disk
13:C 11 May 08:59:35.935 * RDB: 0 MB of memory used by copy-on-write
1:M 11 May 08:59:35.990 * Background saving terminated with success
1:M 11 May 09:04:36.042 * 10 changes in 300 seconds. Saving…
1:M 11 May 09:04:36.042 * Background saving started by pid 19
19:C 11 May 09:04:36.187 * DB saved on disk
19:C 11 May 09:04:36.188 * RDB: 0 MB of memory used by copy-on-write
1:M 11 May 09:04:36.243 * Background saving terminated with success
1:M 11 May 09:24:37.548 * 1 changes in 900 seconds. Saving…
1:M 11 May 09:24:37.548 * Background saving started by pid 20
20:C 11 May 09:24:37.638 * DB saved on disk
20:C 11 May 09:24:37.639 * RDB: 0 MB of memory used by copy-on-write
1:M 11 May 09:24:37.649 * Background saving terminated with success
1:M 11 May 09:29:38.025 * 10 changes in 300 seconds. Saving…
1:M 11 May 09:29:38.025 * Background saving started by pid 21
21:C 11 May 09:29:38.149 * DB saved on disk
21:C 11 May 09:29:38.150 * RDB: 0 MB of memory used by copy-on-write
1:M 11 May 09:29:38.226 * Background saving terminated with success
1:signal-handler (1526031313) Received SIGTERM scheduling shutdown…
1:M 11 May 09:35:13.664 # User requested shutdown…
1:M 11 May 09:35:13.664 * Saving the final RDB snapshot before exiting.
1:M 11 May 09:35:13.754 * DB saved on disk
1:M 11 May 09:35:13.754 * Removing the pid file.
1:M 11 May 09:35:13.754 # Redis is now ready to exit, bye bye…
1:C 11 May 09:35:16.287 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 11 May 09:35:16.287 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 11 May 09:35:16.287 # Configuration loaded
1:M 11 May 09:35:16.289 * Running mode=standalone, port=6379.
1:M 11 May 09:35:16.289 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 11 May 09:35:16.289 # Server initialized
1:M 11 May 09:35:16.289 # 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.
1:M 11 May 09:35:16.293 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 11 May 09:35:16.293 * DB loaded from disk: 0.000 seconds
1:M 11 May 09:35:16.293 * Ready to accept connections
1:M 11 May 09:50:17.091 * 1 changes in 900 seconds. Saving…
1:M 11 May 09:50:17.091 * Background saving started by pid 18
18:C 11 May 09:50:17.182 * DB saved on disk
18:C 11 May 09:50:17.182 * RDB: 0 MB of memory used by copy-on-write
1:M 11 May 09:50:17.192 * Background saving terminated with success

OCR Container Logs

2018-05-11T09:03:40.950Z - error: Job errored: ENOENT: no such file or directory, unlink '/home/node/output/ocr_2D4bxi.pdf’
2018-05-11T09:24:41.000Z - error: Job errored: ENOENT: no such file or directory, unlink '/home/node/output/ocr_G9IL9t.pdf’
2018-05-11T09:28:28.898Z - error: Job errored: ENOENT: no such file or directory, unlink '/home/node/output/ocr_ra1Ktu.pdf’
2018-05-11T09:28:28.996Z - error: Job errored: ENOENT: no such file or directory, unlink '/home/node/output/ocr_KVsyFu.pdf’
2018-05-11T09:31:24.141Z - error: Job errored: ENOENT: no such file or directory, unlink '/home/node/output/ocr_z5a6DZ.pdf’
2018-05-11T09:35:13.757Z - warn: Connection closed to redis server.
2018-05-11T09:35:13.810Z - error: ERROR: read ECONNRESET.
2018-05-11T09:35:13.811Z - warn: Connection closed to redis server.
2018-05-11T09:35:13.912Z - error: ERROR: connect ECONNREFUSED 192.168.3.28:6379.
2018-05-11T09:35:13.913Z - warn: Connection closed to redis server.
2018-05-11T09:35:14.064Z - error: ERROR: connect ECONNREFUSED 192.168.3.28:6379.
2018-05-11T09:35:14.065Z - warn: Connection closed to redis server.
2018-05-11T09:35:14.266Z - error: ERROR: connect ECONNREFUSED 192.168.3.28:6379.
2018-05-11T09:35:14.267Z - warn: Connection closed to redis server.
2018-05-11T09:35:14.519Z - error: ERROR: connect ECONNREFUSED 192.168.3.28:6379.
2018-05-11T09:35:14.519Z - warn: Connection closed to redis server.
2018-05-11T09:35:14.821Z - error: ERROR: connect ECONNREFUSED 192.168.3.28:6379.
2018-05-11T09:35:14.821Z - warn: Connection closed to redis server.
2018-05-11T09:35:15.173Z - error: ERROR: connect ECONNREFUSED 192.168.3.28:6379.
2018-05-11T09:35:15.173Z - warn: Connection closed to redis server.
2018-05-11T09:35:27.924Z - error: Job errored: ENOENT: no such file or directory, unlink ‘/home/node/output/ocr_Mgb63x.pdf’

I have it too

Has anyone an idea how we can fix it? The files are available at the docker Container.