Urlaub ist offensichtlich nichts für mich. War jetzt mal 14 Tage weg. Habe natürlich ordentlich alles vorher nach unten gefahren und ausgeschaltet. Jetzt alles wieder eingeschaltet, aber paperless erkennt meine Zugangsdaten nicht mehr. Die Container weißen alle die grüne Markierung aus. Bin ja kein Profi und würde mich aus diesem Grund über Hilfe freuen. Natürlich habe ich auch die zwei Videokurse |
Paperless-ngx auf Synology-NAS (Masterclass) - kompatibel mit DSM 7.2 (Container Manager
und
1|Videokurs: Synology NAS Masterclass DSM 7.2|
Hi,
Firewall aktiviert? Wenn ja deaktivieren und Paperless neu starten.
Auch mal ins LOG vom Paperless Container schaun ob dort fehler hinterlegt sind.
Guten Abend, Jake
also, wenn ich das richtig sehe, ist der Firewall ausgeschaltet.
Wenn ich den Container Manager öffne, sehe ich u.a. diese 2 Container.
paperless-broker-1 und paperless-db-1
Wenn ich auf diese beiden zugreifen möchte, bekomme ich folgende Meldung:
Dieser Vorgang kann nicht ausgeführt werden. Möglicherweise ist die Netzwerkverbindung instabil oder das System ausgelastet. Bitte versuchen Sie es später erneut.
Es läuft aber auf dem Mac sonst kein anderes Programm. Wie schon geschrieben, ich bin nur Nutzer und leider kein PC Spezi.
Hallo Tomms,
ich würde dir empfehlen, wie im Kurs beschrieben die Container über SSH zu starten und zu stoppen. Die grafische Oberfläche von Synology ist zwar nett, aber ich habe dort schon öfters Probleme gesehen.
Also am besten genau wie hier beschrieben vorgehen:
https://kurse.digitalisierung-mit-kopf.de/lesson/85/
Solltest du dann Fehlermeldungen bekommen, poste sie gerne hier.
Also ich bin so vorgegangen wie angegeben. Keine Ahnung ob da ein Fehler ist und wie ich da wieder rauskomme.
Thomas@NAS-Fred:~$ cd /volume1/docker/paperless-ngx/config/
Thomas@NAS-Fred:/volume1/docker/paperless-ngx/config$ sudo docker-compose down
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
Yfsudo: 3 incorrect password attempts
Thomas@NAS-Fred:/volume1/docker/paperless-ngx/config$ Yfl$#gz3fB#%R2Tm
-sh: Yfl0gz3fB#%R2Tm: command not found
Thomas@NAS-Fred:/volume1/docker/paperless-ngx/config$ sudo docker-compose down
Password:
[+] Running 4/4
Container paperless-webserver-1 R… 9.6s
Container paperless-db-1 Removed 2.1s
Container paperless-broker-1 Remo… 1.7s
Network paperless_default Removed 0.5s
Thomas@NAS-Fred:/volume1/docker/paperless-ngx/config$ sudo docker-compose up
[+] Running 4/3
Network paperless_default Created 0.3s
Container paperless-broker-1 Crea… 0.1s
Container paperless-db-1 Created 0.1s
Container paperless-webserver-1 C… 0.1s
Attaching to paperless-broker-1, paperless-db-1, paperless-webserver-1
paperless-broker-1 | 1:C 16 Apr 2025 18:21:00.596 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
paperless-broker-1 | 1:C 16 Apr 2025 18:21:00.596 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=1, just started
paperless-broker-1 | 1:C 16 Apr 2025 18:21:00.596 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.596 * monotonic clock: POSIX clock_gettime
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.597 * Running mode=standalone, port=6379.
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.597 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.597 # Server initialized
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.598 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub. 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.
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.598 * Loading RDB produced by version 7.0.15
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.598 * RDB age 155 seconds
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.598 * RDB memory usage when created 1.29 Mb
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.598 * Done loading RDB, keys loaded: 4, keys expired: 0.
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.599 * DB loaded from disk: 0.000 seconds
paperless-broker-1 | 1:M 16 Apr 2025 18:21:00.599 * Ready to accept connections
paperless-db-1 |
paperless-db-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
paperless-db-1 |
paperless-db-1 |
paperless-db-1 | 2025-04-16 18:21:00.939 UTC [1] LOG: starting PostgreSQL 16.6 (Debian 16.6-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
paperless-db-1 | 2025-04-16 18:21:00.941 UTC [1] LOG: listening on IPv4 address „0.0.0.0“, port 5432
paperless-db-1 | 2025-04-16 18:21:00.941 UTC [1] LOG: listening on IPv6 address „::“, port 5432
paperless-db-1 | 2025-04-16 18:21:00.958 UTC [1] LOG: listening on Unix socket „/var/run/postgresql/.s.PGSQL.5432“
paperless-db-1 | 2025-04-16 18:21:00.975 UTC [30] LOG: database system was shut down at 2025-04-16 18:18:25 UTC
paperless-db-1 | 2025-04-16 18:21:00.991 UTC [1] LOG: database system is ready to accept connections
paperless-webserver-1 | Paperless-ngx docker container starting…
paperless-webserver-1 | Mapping UID and GID for paperless:paperless to 1027:100
paperless-webserver-1 | Creating directory scratch directory /tmp/paperless
paperless-webserver-1 | mkdir: created directory ‚/tmp/paperless‘
paperless-webserver-1 | Adjusting permissions of paperless files. This may take a while.
paperless-webserver-1 | Waiting for PostgreSQL to start…
paperless-webserver-1 | Connected to PostgreSQL
paperless-webserver-1 | Waiting for Redis…
paperless-webserver-1 | Connected to Redis broker.
paperless-webserver-1 | Apply database migrations…
paperless-webserver-1 | Operations to perform:
paperless-webserver-1 | Apply all migrations: account, admin, auditlog, auth, authtoken, contenttypes, django_celery_results, documents, guardian, paperless, paperless_mail, sessions, socialaccount
paperless-webserver-1 | Running migrations:
paperless-webserver-1 | No migrations to apply.
paperless-webserver-1 | Running Django checks
paperless-webserver-1 | System check identified no issues (0 silenced).
paperless-webserver-1 | Executing /usr/local/bin/paperless_cmd.sh
paperless-webserver-1 | 2025-04-16 18:21:15,597 INFO Set uid to user 0 succeeded
paperless-webserver-1 | 2025-04-16 18:21:15,604 INFO supervisord started with pid 1
paperless-webserver-1 | 2025-04-16 18:21:16,608 INFO spawned: ‚gunicorn‘ with pid 95
paperless-webserver-1 | 2025-04-16 18:21:16,610 INFO spawned: ‚celery‘ with pid 96
paperless-webserver-1 | 2025-04-16 18:21:16,612 INFO spawned: ‚celery-beat‘ with pid 97
paperless-webserver-1 | 2025-04-16 18:21:16,615 INFO spawned: ‚consumer‘ with pid 98
paperless-webserver-1 | 2025-04-16 18:21:16,616 INFO spawned: ‚celery-flower‘ with pid 99
paperless-webserver-1 | Checking if we should start flower…
paperless-webserver-1 | Not starting flower
paperless-webserver-1 | 2025-04-16 18:21:16,649 INFO success: celery-flower entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
paperless-webserver-1 | 2025-04-16 18:21:16,650 INFO exited: celery-flower (exit status 0; expected)
paperless-webserver-1 | 2025-04-16 18:21:17,652 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
paperless-webserver-1 | 2025-04-16 18:21:17,652 INFO success: celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
paperless-webserver-1 | 2025-04-16 18:21:17,652 INFO success: celery-beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
paperless-webserver-1 | 2025-04-16 18:21:17,652 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
paperless-webserver-1 | celery beat v5.4.0 (opalescent) is starting.
paperless-webserver-1 |
paperless-webserver-1 |
paperless-webserver-1 | [2025-04-16 20:21:22,273] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/consume
paperless-webserver-1 | [2025-04-16 20:21:22 +0200] [95] [INFO] Starting gunicorn 23.0.0
paperless-webserver-1 | [2025-04-16 20:21:22 +0200] [95] [INFO] Listening at: http://[::]:8000 (95)
paperless-webserver-1 | [2025-04-16 20:21:22 +0200] [95] [INFO] Using worker: paperless.workers.ConfigurableWorker
paperless-webserver-1 | [2025-04-16 20:21:22 +0200] [95] [INFO] Server is ready. Spawning workers
paperless-webserver-1 | __ - … __ - _
paperless-webserver-1 | LocalTime → 2025-04-16 20:21:22
paperless-webserver-1 | Configuration →
paperless-webserver-1 | . broker → redis://broker:6379//
paperless-webserver-1 | . loader → celery.loaders.app.AppLoader
paperless-webserver-1 | . scheduler → celery.beat.PersistentScheduler
paperless-webserver-1 | . db → /usr/src/paperless/data/celerybeat-schedule.db
paperless-webserver-1 | . logfile → [stderr]@%INFO
paperless-webserver-1 | . maxinterval → 5.00 minutes (300s)
paperless-webserver-1 | [2025-04-16 20:21:22,975] [INFO] [celery.beat] beat: Starting…
paperless-webserver-1 | [2025-04-16 20:21:23,070] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
paperless-webserver-1 |
paperless-webserver-1 | -------------- celery@4b58319e5bcd v5.4.0 (opalescent)
paperless-webserver-1 | — ***** -----
paperless-webserver-1 | – ******* ---- Linux-4.4.302±x86_64-with-glibc2.36 2025-04-16 20:21:23
paperless-webserver-1 | - *** — * —
paperless-webserver-1 | - ** ---------- [config]
paperless-webserver-1 | - ** ---------- .> app: paperless:0x7f161f735df0
paperless-webserver-1 | - ** ---------- .> transport: redis://broker:6379//
paperless-webserver-1 | - ** ---------- .> results:
paperless-webserver-1 | - *** — * — .> concurrency: 1 (prefork)
paperless-webserver-1 | – ******* ---- .> task events: ON
paperless-webserver-1 | — ***** -----
paperless-webserver-1 | -------------- [queues]
paperless-webserver-1 | .> celery exchange=celery(direct) key=celery
paperless-webserver-1 |
paperless-webserver-1 |
paperless-webserver-1 | [tasks]
paperless-webserver-1 | . documents.bulk_edit.delete
paperless-webserver-1 | . documents.tasks.bulk_update_documents
paperless-webserver-1 | . documents.tasks.consume_file
paperless-webserver-1 | . documents.tasks.empty_trash
paperless-webserver-1 | . documents.tasks.index_optimize
paperless-webserver-1 | . documents.tasks.sanity_check
paperless-webserver-1 | . documents.tasks.train_classifier
paperless-webserver-1 | . documents.tasks.update_document_archive_file
paperless-webserver-1 | . paperless_mail.mail.apply_mail_action
paperless-webserver-1 | . paperless_mail.mail.error_callback
paperless-webserver-1 | . paperless_mail.tasks.process_mail_accounts
paperless-webserver-1 |
paperless-webserver-1 |
paperless-webserver-1 | [2025-04-16 20:21:23,267] [INFO] [celery.worker.consumer.connection] Connected to redis://broker:6379//
paperless-webserver-1 | [2025-04-16 20:21:23,292] [INFO] [celery.apps.worker] celery@4b58319e5bcd ready.
paperless-webserver-1 | [2025-04-16 20:21:23,297] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[2f8d29c9-b188-46e1-ab63-c55f381c79ef] received
paperless-webserver-1 | [2025-04-16 20:21:23,658] [ERROR] [paperless_mail] Unable to access folder Verarbeitete Mail, attempting folder listing
paperless-webserver-1 | [2025-04-16 20:21:23,679] [INFO] [paperless_mail] Located folder: Archiv
paperless-webserver-1 | [2025-04-16 20:21:23,680] [INFO] [paperless_mail] Located folder: Entwürfe
paperless-webserver-1 | [2025-04-16 20:21:23,680] [INFO] [paperless_mail] Located folder: Gesendete Objekte
paperless-webserver-1 | [2025-04-16 20:21:23,681] [INFO] [paperless_mail] Located folder: INBOX
paperless-webserver-1 | [2025-04-16 20:21:23,681] [INFO] [paperless_mail] Located folder: INBOX/C. Mayer
paperless-webserver-1 | [2025-04-16 20:21:23,682] [INFO] [paperless_mail] Located folder: INBOX/Captrader
paperless-webserver-1 | [2025-04-16 20:21:23,682] [INFO] [paperless_mail] Located folder: INBOX/Grüner Fisher
paperless-webserver-1 | [2025-04-16 20:21:23,682] [INFO] [paperless_mail] Located folder: INBOX/Lueddeman Inv.
paperless-webserver-1 | [2025-04-16 20:21:23,683] [INFO] [paperless_mail] Located folder: INBOX/Thomas Dahlmann
paperless-webserver-1 | [2025-04-16 20:21:23,683] [INFO] [paperless_mail] Located folder: INBOX/TradingView
paperless-webserver-1 | [2025-04-16 20:21:23,683] [INFO] [paperless_mail] Located folder: INBOX/Verarbeitete Mail
paperless-webserver-1 | [2025-04-16 20:21:23,684] [INFO] [paperless_mail] Located folder: INBOX/Welt
paperless-webserver-1 | [2025-04-16 20:21:23,684] [INFO] [paperless_mail] Located folder: INBOX/justETF
paperless-webserver-1 | [2025-04-16 20:21:23,684] [INFO] [paperless_mail] Located folder: INBOX/wiki
paperless-webserver-1 | [2025-04-16 20:21:23,685] [INFO] [paperless_mail] Located folder: Papierkorb
paperless-webserver-1 | [2025-04-16 20:21:23,685] [INFO] [paperless_mail] Located folder: Spam
paperless-webserver-1 | [2025-04-16 20:21:23,686] [ERROR] [paperless_mail] Rule Thomas Hofmann.Posteingang Thomas: Error while processing rule: Rule Thomas Hofmann.Posteingang Thomas: Folder Verarbeitete Mail does not exist in account Thomas Hofmann
paperless-webserver-1 | Traceback (most recent call last):
paperless-webserver-1 | File „/usr/src/paperless/src/paperless_mail/mail.py“, line 601, in _handle_mail_rule
paperless-webserver-1 | M.folder.set(folder)
paperless-webserver-1 | File „/usr/local/lib/python3.12/site-packages/imap_tools/folder.py“, line 44, in set
paperless-webserver-1 | check_command_status(result, MailboxFolderSelectError)
paperless-webserver-1 | File „/usr/local/lib/python3.12/site-packages/imap_tools/utils.py“, line 46, in check_command_status
paperless-webserver-1 | raise exception(command_result=command_result, expected=expected)
paperless-webserver-1 | imap_tools.errors.MailboxFolderSelectError: Response status „OK“ expected, but „NO“ received. Data: [b’unknown folder’]
paperless-webserver-1 |
paperless-webserver-1 | The above exception was the direct cause of the following exception:
paperless-webserver-1 |
paperless-webserver-1 | Traceback (most recent call last):
paperless-webserver-1 | File „/usr/src/paperless/src/paperless_mail/mail.py“, line 564, in handle_mail_account
paperless-webserver-1 | total_processed_files += self._handle_mail_rule(
paperless-webserver-1 | ^^^^^^^^^^^^^^^^^^^^^^^
paperless-webserver-1 | File „/usr/src/paperless/src/paperless_mail/mail.py“, line 615, in _handle_mail_rule
paperless-webserver-1 | raise MailError(
paperless-webserver-1 | paperless_mail.mail.MailError: Rule Thomas Hofmann.Posteingang Thomas: Folder Verarbeitete Mail does not exist in account Thomas Hofmann
paperless-webserver-1 |
paperless-webserver-1 | [2025-04-16 20:21:23,737] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[2f8d29c9-b188-46e1-ab63-c55f381c79ef] succeeded in 0.40520805900450796s: ‚No new documents were added.‘
sudo docker-compose down
sudo docker-compose up
ssh sudo docker-compose down
paperless-db-1 | 2025-04-16 18:26:01.057 UTC [28] LOG: checkpoint starting: time
paperless-db-1 | 2025-04-16 18:26:02.224 UTC [28] LOG: checkpoint complete: wrote 13 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.004 s, sync=0.113 s, total=1.168 s; sync files=12, longest=0.023 s, average=0.010 s; distance=46 kB, estimate=46 kB; lsn=0/2B8EC608, redo lsn=0/2B8EC5D0
Vielleicht hilft das Bild noch weiter. Wenn ich das umsetze was in der Mail steht, die ich seit gestern bekomme.
" Container paperless-db-1 in Container Manager wurde unerwartet beendet. Wählen Sie auf der SeiteContainer paperless-db-1 aus, klicken Sie auf Details und öffnen Sie die Registerkarte Protokoll für weitere Informationen.
Von NAS-Fred"
Sehe ich folgendes Bild.
Also ich habe einen neuen Benutzer angelegt, jetzt läuft das Ganze wieder. 
Im Terminal ist das jetzt die letzte Zeile " Thomas@NAS-Fred:/volume1/docker/paperless-ngx/config$ " Muss ich da noch etwas eingeben oder kann ich es einfach schließen?
Dieses Thema wurde automatisch 2 Tage nach der letzten Antwort geschlossen. Es sind keine neuen Antworten mehr erlaubt.