artwodeetwo

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by artwodeetwo

  1. I didn’t find any docs on what each status code meant, but I was able to root cause my issue by setting the ocrmypdf docker to run in debug mode. Environment variable: OCR_VERBOSITY set to “debug”.
  2. Answering my own question: status 2 means it's not a PDF. I found out that NC was encrypting files placed into external storage, so while it still had a .pdf extension the file was no longer readable outside of my Nextcloud instance. I found the setting for external storage encryption and disabled that. Working well now.
  3. What does "status 2" mean? I'm trying to integrate ocrmypdf into my Nextcloud by presenting the input & output directories as external storage (SMB) shares within Nextcloud directory structure. file1.pdf and file2.pdf are two copies of the same file, the first placed through Nextcloud and the second copied directly to the SMB share. The second one produces an output but the first one does not. For both files the SMB user is the same. 2021-11-02 09:43:13 - Processing: /input/file1.pdf -> /output/file1.pdf 2021-11-02 09:43:16 - Processing complete in 3.750000 seconds with status 2: /input/file1.pdf TESTOCR_PROCESS_RESULT/input/file1.pdf/output/file1.pdf��.750000 2021-11-02 09:46:18 - Processing: /input/file2.pdf -> /output/file2.pdf 2021-11-02 09:46:33 - Processing complete in 14.970000 seconds with status 0: /input/file2.pdf TESTOCR_PROCESS_RESULT/input/file2.pdf/output/file2.pdf�.970000
  4. Undraid 6.9.2 I had this start being an issue for me too, and I'd just recently switched over to using Safari on a Mac. I always keep a tab open to my Unraid machine. After I found this and the query re: Safari I switched to Brave (was just giving Safari a chance really), rebooted the server to clear the log storage and haven't seen the message or an increase in logs (still on 1%) in the last ~6d.
  5. Thank you for the db-backup docker. Just what I was looking for to do regular unattended mariadb backups. So far I've only run manual backups and I get an error saying it can't stat the backup file, yet the backup was successfully created: / # backup-now ** Performing Manual Backup [INFO] ** [db-backup] Initialized on Wed Jun 10 11:02:08 AEST 2020 stat: can't stat '/backup/mysql__192.168.1.8_20200610-110208.sql.gz': No such file or directory / # ls -al /backup/mysql__192.168.1.8_20200610-110208.sql.gz -rw-r--r-- 1 root root 28013991 Jun 10 11:02 /backup/mysql__192.168.1.8_20200610-110208.sql.gz Is it safe to disregard as a cosmetic issue?