paperless-ngx - Redis Status Error & Celery Status Error

strama · 29. Sep 2024

Guten Morgen zusammen,

nach meiner, ich denke, 8ten Neuinstallation inkl. Anpassung mehrerer Parameter stehe ich immernoch vor dem identischen Problem, dass paperless anfangs läuft, ca 10-18 Dokumente erkennt und dann urplötzlich aufhört. Wenn ich mich zu diesem Zeitounkt aus-/einlogge bekomme ich einen Fehler 500.

Alles läuft auf einer DS923+ über Portainer eingerichtet

Code:

version: "3.4"
services:
  broker:
    image: docker.io/library/redis:7
    restart: unless-stopped
    volumes:
      - /volume2/docker/paperless-ngx/redisdata:/data

  webserver:
    image: ghcr.io/paperless-ngx/paperless-ngx:latest
    restart: unless-stopped
    depends_on:
      - broker
    ports:
      - 8810:8000
    healthcheck:
      test: ["CMD", "curl", "-fs", "-S", "--max-time", "2", "http://localhost:8000"]
      interval: 30s
      timeout: 10s
      retries: 5
    volumes:
      - /volume2/docker/paperless-ngx/data:/usr/src/paperless/data
      - /volume2/docker/paperless-ngx/media:/usr/src/paperless/media
      - /volume2/docker/paperless-ngx/export:/usr/src/paperless/export
      - /volume2/docker/paperless-ngx/consume:/usr/src/paperless/consume
    environment:
      PAPERLESS_REDIS: redis://broker:6379
      PAPERLESS_SECRET_KEY: super11geheim
      PAPERLESS_ADMIN_USER: admin
      PAPERLESS_ADMIN_PASSWORD: 123456
      PAPERLESS_OCR_LANGUAGE: deu+eng
      PAPERLESS_CONSUMER_DELETE_DUPLICATES: true
      PAPERLESS_CONSUMER_ENABLE_BARCODES: true
      PAPERLESS_TIKA_ENABLED: 1
      PAPERLESS_TIKA_GOTENBERG_ENDPOINT: http://gotenberg:3000
      PAPERLESS_TIKA_ENDPOINT: http://tika:9998
      USERMAP_UID: 1028
      USERMAP_GID: 65536

  gotenberg:
    image: docker.io/gotenberg/gotenberg:8
    restart: unless-stopped
    command:
      - "gotenberg"
      - "--chromium-disable-javascript=true"
      - "--chromium-allow-list=file:///tmp/.*"

  tika:
    image: ghcr.io/paperless-ngx/tika:latest
    restart: unless-stopped

volumes:
  data:
  media:
  redisdata:

siehe paperless Status im Anhang

dazu erscheint immer wieder die identische Fehlermeldung im LOG:

Code:

[2024-09-28 23:55:36,618] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-28 23:55:36,621] [ERROR] [paperless.api] System status detected a possible problem while loading the classifier: Classifier file does not exist (yet). Re-training may be pending.

Traceback (most recent call last):

File "/usr/src/paperless/src/documents/views.py", line 2007, in get

raise FileNotFoundError(classifier_error)

FileNotFoundError: Classifier file does not exist (yet). Re-training may be pending.

[2024-09-29 00:02:01,681] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:02:01,685] [ERROR] [paperless.api] System status detected a possible problem while loading the classifier: Classifier file does not exist (yet). Re-training may be pending.

Traceback (most recent call last):

File "/usr/src/paperless/src/documents/views.py", line 2007, in get

raise FileNotFoundError(classifier_error)

FileNotFoundError: Classifier file does not exist (yet). Re-training may be pending.

[2024-09-29 00:02:02,727] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:02:02,730] [ERROR] [paperless.api] System status detected a possible problem while loading the classifier: Classifier file does not exist (yet). Re-training may be pending.

Traceback (most recent call last):

File "/usr/src/paperless/src/documents/views.py", line 2007, in get

raise FileNotFoundError(classifier_error)

FileNotFoundError: Classifier file does not exist (yet). Re-training may be pending.

[2024-09-29 00:02:33,374] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:02:36,937] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:02:38,787] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:02:41,087] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:02:44,583] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:03:55,282] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:03:56,631] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:03:57,561] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:03:58,560] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:04:02,505] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:04:02,508] [ERROR] [paperless.api] System status detected a possible problem while loading the classifier: Classifier file does not exist (yet). Re-training may be pending.

Traceback (most recent call last):

File "/usr/src/paperless/src/documents/views.py", line 2007, in get

raise FileNotFoundError(classifier_error)

FileNotFoundError: Classifier file does not exist (yet). Re-training may be pending.

[2024-09-29 00:04:03,598] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:04:03,601] [ERROR] [paperless.api] System status detected a possible problem while loading the classifier: Classifier file does not exist (yet). Re-training may be pending.

Traceback (most recent call last):

File "/usr/src/paperless/src/documents/views.py", line 2007, in get

raise FileNotFoundError(classifier_error)

FileNotFoundError: Classifier file does not exist (yet). Re-training may be pending.

[2024-09-29 00:05:00,043] [DEBUG] [paperless.classifier] Document classification model does not exist (yet), not performing automatic matching.

[2024-09-29 00:05:00,046] [DEBUG] [paperless.classifier] Gathering data from database...

[2024-09-29 00:05:00,090] [DEBUG] [paperless.classifier] 39 documents, 1 tag(s), 0 correspondent(s), 3 document type(s). 0 storage path(es)

[2024-09-29 00:05:00,170] [DEBUG] [paperless.classifier] Vectorizing data...

[2024-09-29 00:05:00,929] [DEBUG] [paperless.classifier] Training tags classifier...

[2024-09-29 00:05:02,089] [DEBUG] [paperless.classifier] There are no correspondents. Not training correspondent classifier.

[2024-09-29 00:05:02,089] [DEBUG] [paperless.classifier] Training document type classifier...

[2024-09-29 00:05:03,551] [DEBUG] [paperless.classifier] There are no storage paths. Not training storage path classifier.

[2024-09-29 00:05:03,554] [INFO] [paperless.tasks] Saving updated classifier model to /usr/src/paperless/data/classification_model.pickle...

[2024-09-29 08:43:41,829] [ERROR] [paperless.api] System status detected a possible problem while connecting to redis: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

Traceback (most recent call last):

File "/usr/src/paperless/src/documents/views.py", line 1947, in get

client.ping()

File "/usr/local/lib/python3.11/site-packages/redis/commands/core.py", line 1208, in ping

return self.execute_command("PING", **kwargs)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 548, in execute_command

return conn.retry.call_with_retry(

^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/retry.py", line 62, in call_with_retry

return do()

^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 549, in <lambda>

lambda: self._send_command_parse_response(

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 525, in _send_command_parse_response

return self.parse_response(conn, command_name, **options)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 565, in parse_response

response = connection.read_response()

^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/connection.py", line 536, in read_response

raise response

redis.exceptions.ResponseError: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

[2024-09-29 08:43:42,242] [ERROR] [paperless.api] System status detected a possible problem while connecting to redis: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

Traceback (most recent call last):

File "/usr/src/paperless/src/documents/views.py", line 1947, in get

client.ping()

File "/usr/local/lib/python3.11/site-packages/redis/commands/core.py", line 1208, in ping

return self.execute_command("PING", **kwargs)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 548, in execute_command

return conn.retry.call_with_retry(

^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/retry.py", line 62, in call_with_retry

return do()

^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 549, in <lambda>

lambda: self._send_command_parse_response(

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 525, in _send_command_parse_response

return self.parse_response(conn, command_name, **options)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 565, in parse_response

response = connection.read_response()

^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/redis/connection.py", line 536, in read_response

raise response

redis.exceptions.ResponseError: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

Ich hoffe mir kann geholfen werden

Danke

Laola1 · 02. Okt 2024

Ich bekomme mein Paperless auch nicht mehr ans laufen, seit der Neuinstallation der DS920+.
Die gleiche Docker Compose läuft (mit geändertem Volume) auf der DS224+ einwandfrei.

Liegt es evtl, daran, das Docker nun auf einen M.2 Volume liegt, und hier evtl. irgendwelche internen Mountpoints fehlen?
Auf dem M.2 liegt ja offensichtlich kein DSM.

Paperless-ngx docker container starting...
Mapping UID and GID for paperless

aperless to 0:0
Creating directory scratch directory /tmp/paperless
mkdir: created directory '/tmp/paperless'
Adjusting permissions of paperless files. This may take a while.
Waiting for Redis...

vcdg23 · 07. Okt 2024

Moin,

ich habe das gleiche Problem, da ich durch ein Postgressupdate alles neu installieren musste, bin ich auf Maria-DB umgestiegen. Sofern so gut, Installation ohne Probleme, doch noch einigen Minuten erscheint bei mir der gleiche Fehler. Erst nach neustart von Redis läuft es einige Minuten.

DS224+

Hellraiser123 · 07. Okt 2024

Postet so ein Problem doch einfach mal bei Github als Issue. Wenn hier keine Antworten direkt kommen, dann wird das wahrscheinlich auch so bleiben. Daher einfach mal ein Issue aufmachen.

Laola1 · 07. Okt 2024

Bei mir lag es an der Firewall, Asche auf mein Haupt

Es war der 172.xxx. IP-Bereich nicht eingetragen und wurde somit vollständig geblockt.
Sorry hab´s ganz vergessen zu posten, Problem besteht nicht mehr.

vcdg23 · 08. Okt 2024

Kann es evtl daran liegen, dass redis 2x in Benutzung ist? Bei mir einmal für immich und einmal für paperless.

Hellraiser123 · 08. Okt 2024

Aber die Instanzen sind doch bestimmt anders konfiguriert? Also Pfade und Ports oder?

vcdg23 · 08. Okt 2024

Ja, da hast du recht Pfade und Ports sind anders konfiguriert. In der Übersicht wird auch nur angezeigt, welche Tags dieses Image nutzen und dass ist ja in dem Fall dann richtig.

Hellraiser123 · 08. Okt 2024

Dafür sind Container auch da. Also das man mehrere Instanzen betreiben kann.

vcdg23 · 08. Okt 2024

So, hab den Fehler jetzt bei mir behoben. Es lag wirklich an Schreibrechten, wieso auch immer die nicht vergeben wurden, obwohl in der .yaml hinterlegt.

Bin wie folgt vorgegangen:

Verzeichnis finden: Bestimmen, wo die RDB-Datei gespeichert werden soll (z.B. /volume1/docker/paperlessngx/redis).
Berechtigungen anpassen:
chown -R 1026:100 /volume1/docker/paperlessngx/redis
chmod -R 755 /volume1/docker/paperlessngx/redis
Container neu starten

1026:100 ist meine UID/GID, die muss, sowie der Pfad evtl. angepasst werden.

Suche

paperless-ngx - Redis Status Error & Celery Status Error

strama

Benutzer

Anhänge

Laola1

Benutzer

vcdg23

Benutzer

Hellraiser123

Benutzer

Laola1

Benutzer

vcdg23

Benutzer

Hellraiser123

Benutzer

vcdg23

Benutzer

Hellraiser123

Benutzer

vcdg23

Benutzer

Kaffeautomat