elbadepadualima Posted July 1 Share Posted July 1 (edited) Hallo Zusammen, ich habe seit 2 Jahren einen Paperless Docker in Unraid laufen, bisher ohne Probleme. Seit ich auf die aktuelle Version geupdatet habe (ich habe Paperless immer aktuell gehalten), flutet der Container mein docker.img. Am Mapping habe ich nichts verändert und ebenfalls nichts in den Einstellungen von Paperless. Ein Rollback auf Version 2.9.0 hat leider auch keinen Erfolg gebracht. Ich habe den Container nun gestoppt, da das Beschreiben des Image die Auslastung des gesamten Servers auf 100%. Hat jemand eine Vermutung wo die Ursache liegen könnte? Ich wäre Euch sehr dankbar. Ich ergänze noch um Thunderbird, der Docker verhält sich genauso. Auslastung geht hoch und das docker.img wird vollgeschrieben. Mir ist eben noch eingefallen, dass ich vor 2 Tagen auch Appdata Backup installiert habe. Könnte dies auch der Auslöser sein? Edited July 1 by elbadepadualima Quote Link to comment
alturismo Posted July 2 Share Posted July 2 5 hours ago, elbadepadualima said: Seit ich auf die aktuelle Version geupdatet habe was wurde updated, Unraid, Paperless, ... ? 5 hours ago, elbadepadualima said: flutet der Container mein docker.img. mit was ? gerade paperless hat ja normal nichts zu "fluten" was sagen denn die logs der besagten Docker's aus ? abschließend, docker run <<click<< der besagten docker's bitte mal posten zusätzlich vielleicht noch ne diagnostics <<click<< anhängen dann könnte man eher helfen Quote Link to comment
elbadepadualima Posted July 2 Author Share Posted July 2 (edited) 17 hours ago, alturismo said: was wurde updated, Unraid, Paperless, ... ? Zunächst habe ich die Docker-Container updated und später auch Unraid. Das Problen bestand aber auch schon vor dem Unraid-Update, Quote mit was ? gerade paperless hat ja normal nichts zu "fluten" Ich kann es leider nicht sagen, der Docker startet und nach 2-3Minuten geht die Speicherauslastung des Dockers rapide nach oben, 400-600MB pro Minute. Ebenfalls geht die Prozessorauslastung nach oben, zunächst 25% und nach 3-5Minuten nahezu auf 100%. Quote was sagen denn die logs der besagten Docker's aus ? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/backends/sqlite3/base.py", line 328, in execute return super().execute(query, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlite3.IntegrityError: NOT NULL constraint failed: documents_paperlesstask.status The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/paperless/src/documents/signals/handlers.py", line 855, in task_postrun_handler task_instance.save() File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 814, in save self.save_base( File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 877, in save_base updated = self._save_table( ^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 990, in _save_table updated = self._do_update( ^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 1054, in _do_update return filtered._update(values) > 0 ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 1231, in _update return query.get_compiler(self.db).execute_sql(CURSOR) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1984, in execute_sql cursor = super().execute_sql(result_type) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1562, in execute_sql cursor.execute(sql, params) File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: File "/usr/local/lib/python3.11/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/django/db/backends/sqlite3/base.py", line 328, in execute return super().execute(query, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ django.db.utils.IntegrityError: NOT NULL constraint failed: documents_paperlesstask.status [2024-07-02 22:09:25,761: ERROR/MainProcess] Process 'ForkPoolWorker-4' pid:304 exited with 'signal 15 (SIGTERM)' [2024-07-02 22:09:25,927] [ERROR] [celery.worker.request] Task handler raised error: WorkerLostError('Worker exited prematurely: signal 15 (SIGTERM) Job: 3.') Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/billiard/pool.py", line 1264, in mark_as_worker_lost raise WorkerLostError( billiard.einfo.ExceptionWithTraceback: """ Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/celery/worker/worker.py", line 202, in start self.blueprint.start(self) File "/usr/local/lib/python3.11/site-packages/celery/bootsteps.py", line 116, in start step.start(parent) File "/usr/local/lib/python3.11/site-packages/celery/bootsteps.py", line 365, in start return self.obj.start() ^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py", line 340, in start blueprint.start(self) File "/usr/local/lib/python3.11/site-packages/celery/bootsteps.py", line 116, in start step.start(parent) File "/usr/local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py", line 746, in start c.loop(*c.loop_args()) File "/usr/local/lib/python3.11/site-packages/celery/worker/loops.py", line 86, in asynloop state.maybe_shutdown() File "/usr/local/lib/python3.11/site-packages/celery/worker/state.py", line 93, in maybe_shutdown raise WorkerShutdown(should_stop) celery.exceptions.WorkerShutdown: 0 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/billiard/pool.py", line 1264, in mark_as_worker_lost raise WorkerLostError( billiard.exceptions.WorkerLostError: Worker exited prematurely: signal 15 (SIGTERM) Job: 3. """ [2024-07-02 22:09:25,939] [WARNING] [celery.redirected] Restoring 4 unacknowledged message(s) [2024-07-02 22:09:26 +0200] [96] [INFO] Handling signal: term [2024-07-02 22:09:26 +0200] [96] [INFO] Shutting down: Master 2024-07-02 22:09:25,307 INFO waiting for gunicorn, celery to die 2024-07-02 22:09:26,311 INFO stopped: celery (exit status 0) 2024-07-02 22:09:28,284 INFO stopped: gunicorn (exit status 0) Paperless-ngx docker container starting... Creating directory scratch directory /tmp/paperless Adjusting permissions of paperless files. This may take a while. Waiting for Redis... Connected to Redis broker. Apply database migrations... Operations to perform: Apply all migrations: account, admin, auditlog, auth, authtoken, contenttypes, django_celery_results, documents, guardian, paperless, paperless_mail, sessions, socialaccount Running migrations: No migrations to apply. Running Django checks System check identified no issues (0 silenced). Executing /usr/local/bin/paperless_cmd.sh 2024-07-02 22:11:06,333 INFO Set uid to user 0 succeeded 2024-07-02 22:11:06,533 INFO supervisord started with pid 1 2024-07-02 22:11:07,540 INFO spawned: 'gunicorn' with pid 82 2024-07-02 22:11:07,555 INFO spawned: 'celery' with pid 83 2024-07-02 22:11:07,563 INFO spawned: 'celery-beat' with pid 84 2024-07-02 22:11:07,573 INFO spawned: 'consumer' with pid 85 2024-07-02 22:11:07,594 INFO spawned: 'celery-flower' with pid 86 Checking if we should start flower... 2024-07-02 22:11:07,649 INFO success: celery-flower entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) Not starting flower 2024-07-02 22:11:07,649 INFO exited: celery-flower (exit status 0; expected) 2024-07-02 22:11:08,650 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-02 22:11:08,656 INFO success: celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-02 22:11:08,659 INFO success: celery-beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-02 22:11:08,659 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) celery beat v5.4.0 (opalescent) is starting. [2024-07-02 22:11:12,455] [WARNING] [paperless.management.consumer] Not consuming file /usr/src/paperless/consume/.smbdeleteAAAd0a34.4: Unknown file extension. [2024-07-02 22:11:12,457] [INFO] [paperless.management.consumer] Adding /usr/src/paperless/consume/ALU-WX-instruction_wx_2_de 0007.pdf to the task queue. [2024-07-02 22:11:12,777] [INFO] [paperless.management.consumer] Adding /usr/src/paperless/consume/2024-03-26 scan__010879.pdf to the task queue. [2024-07-02 22:11:12,806] [INFO] [paperless.management.consumer] Adding /usr/src/paperless/consume/KeContact_KCP20_30_ih_de.pdf to the task queue. __ - ... __ - _ LocalTime -> 2024-07-02 22:11:12 Configuration -> . broker -> redis://192.168.1.58:6379// . loader -> celery.loaders.app.AppLoader . scheduler -> celery.beat.PersistentScheduler . db -> /usr/src/paperless/data/celerybeat-schedule.db . logfile -> [stderr]@%INFO . maxinterval -> 5.00 minutes (300s) [2024-07-02 22:11:12,893] [INFO] [celery.beat] beat: Starting... [2024-07-02 22:11:13,021] [INFO] [paperless.management.consumer] Adding /usr/src/paperless/consume/d165f3b5-54c4-4029-bfdb-974ccd734c38.pdf to the task queue. [2024-07-02 22:11:13,056] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/consume [2024-07-02 22:11:13,069] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts) [2024-07-02 22:11:13 +0200] [82] [INFO] Starting gunicorn 22.0.0 [2024-07-02 22:11:13 +0200] [82] [INFO] Listening at: http://[::]:8000 (82) [2024-07-02 22:11:13 +0200] [82] [INFO] Using worker: paperless.workers.ConfigurableWorker [2024-07-02 22:11:13 +0200] [82] [INFO] Server is ready. Spawning workers -------------- celery@0bc36505ce97 v5.4.0 (opalescent) --- ***** ----- -- ******* ---- Linux-6.1.79-Unraid-x86_64-with-glibc2.36 2024-07-02 22:11:15 - *** --- * --- - ** ---------- [config] - ** ---------- .> app: paperless:0x149194d12b10 - ** ---------- .> transport: redis://192.168.1.58:6379// - ** ---------- .> results: - *** --- * --- .> concurrency: 1 (prefork) -- ******* ---- .> task events: ON --- ***** ----- -------------- [queues] .> celery exchange=celery(direct) key=celery [tasks] . documents.bulk_edit.delete . documents.tasks.bulk_update_documents . documents.tasks.consume_file . documents.tasks.empty_trash . documents.tasks.index_optimize . documents.tasks.sanity_check . documents.tasks.train_classifier . documents.tasks.update_document_archive_file . paperless_mail.mail.apply_mail_action . paperless_mail.mail.error_callback . paperless_mail.tasks.process_mail_accounts [2024-07-02 22:11:15,714] [INFO] [celery.worker.consumer.connection] Connected to redis://192.168.1.58:6379// [2024-07-02 22:11:15,857] [INFO] [celery.apps.worker] celery@0bc36505ce97 ready. [2024-07-02 22:11:15,861] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[05e968a0-7956-4294-b2ae-c80085e0647d] received [2024-07-02 22:11:15,866] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[3f93e29f-51cd-4e9f-bf3f-0108866c28f9] received [2024-07-02 22:11:15,870] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[28bd1885-d7f6-42e9-8b23-876f9749bd2d] received [2024-07-02 22:11:15,875] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[fa499c22-06d0-452a-bd69-c1febaa5e48a] received [2024-07-02 22:11:15,878] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[e809e3c3-d4b7-4896-a35b-53b51e51f4aa] received [2024-07-02 22:11:42,453] [INFO] [paperless.tasks] BarcodePlugin completed with no message [2024-07-02 22:11:42,508] [INFO] [paperless.tasks] WorkflowTriggerPlugin completed with: [2024-07-02 22:11:42,902] [ERROR] [paperless.consumer] Not consuming 2024-03-26 scan__010879.pdf: It is a duplicate of scan__010879 (#1621) [2024-07-02 22:11:42,902] [ERROR] [paperless.tasks] ConsumeTaskPlugin failed: 2024-03-26 scan__010879.pdf: Not consuming 2024-03-26 scan__010879.pdf: It is a duplicate of scan__010879 (#1621) Traceback (most recent call last): File "/usr/src/paperless/src/documents/tasks.py", line 151, in consume_file msg = plugin.run() ^^^^^^^^^^^^ File "/usr/src/paperless/src/documents/consumer.py", line 502, in run self.pre_check_duplicate() File "/usr/src/paperless/src/documents/consumer.py", line 326, in pre_check_duplicate self._fail( File "/usr/src/paperless/src/documents/consumer.py", line 302, in _fail raise ConsumerError(f"{self.filename}: {log_message or message}") from exception documents.consumer.ConsumerError: 2024-03-26 scan__010879.pdf: Not consuming 2024-03-26 scan__010879.pdf: It is a duplicate of scan__010879 (#1621) [2024-07-02 22:11:42,944] [ERROR] [celery.app.trace] Task documents.tasks.consume_file[05e968a0-7956-4294-b2ae-c80085e0647d] raised unexpected: ConsumerError('2024-03-26 scan__010879.pdf: Not consuming 2024-03-26 scan__010879.pdf: It is a duplicate of scan__010879 (#1621)') Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/celery/app/trace.py", line 453, in trace_task R = retval = fun(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/celery/app/trace.py", line 736, in __protected_call__ return self.run(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/asgiref/sync.py", line 327, in main_wrap raise exc_info[1] File "/usr/src/paperless/src/documents/tasks.py", line 151, in consume_file msg = plugin.run() ^^^^^^^^^^^^ File "/usr/src/paperless/src/documents/consumer.py", line 502, in run self.pre_check_duplicate() File "/usr/src/paperless/src/documents/consumer.py", line 326, in pre_check_duplicate self._fail( File "/usr/src/paperless/src/documents/consumer.py", line 302, in _fail raise ConsumerError(f"{self.filename}: {log_message or message}") from exception documents.consumer.ConsumerError: 2024-03-26 scan__010879.pdf: Not consuming 2024-03-26 scan__010879.pdf: It is a duplicate of scan__010879 (#1621) [2024-07-02 22:11:43,220] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[15ef7e4b-148f-4cbb-bae5-f7b6cb1dad7e] received [2024-07-02 22:13:13,314] [INFO] [paperless.tasks] BarcodePlugin completed with no message [2024-07-02 22:13:13,488] [INFO] [paperless.tasks] WorkflowTriggerPlugin completed with: [2024-07-02 22:13:14,146] [ERROR] [paperless.consumer] Not consuming ALU-WX-instruction_wx_2_de 0007.pdf: It is a duplicate of ALU-WX-instruction_wx_2_de (#1594) [2024-07-02 22:13:14,148] [ERROR] [paperless.tasks] ConsumeTaskPlugin failed: ALU-WX-instruction_wx_2_de 0007.pdf: Not consuming ALU-WX-instruction_wx_2_de 0007.pdf: It is a duplicate of ALU-WX-instruction_wx_2_de (#1594) Traceback (most recent call last): File "/usr/src/paperless/src/documents/tasks.py", line 151, in consume_file msg = plugin.run() ^^^^^^^^^^^^ File "/usr/src/paperless/src/documents/consumer.py", line 502, in run self.pre_check_duplicate() File "/usr/src/paperless/src/documents/consumer.py", line 326, in pre_check_duplicate self._fail( File "/usr/src/paperless/src/documents/consumer.py", line 302, in _fail raise ConsumerError(f"{self.filename}: {log_message or message}") from exception documents.consumer.ConsumerError: ALU-WX-instruction_wx_2_de 0007.pdf: Not consuming ALU-WX-instruction_wx_2_de 0007.pdf: It is a duplicate of ALU-WX-instruction_wx_2_de (#1594) [2024-07-02 22:13:14,195] [ERROR] [celery.app.trace] Task documents.tasks.consume_file[3f93e29f-51cd-4e9f-bf3f-0108866c28f9] raised unexpected: ConsumerError('ALU-WX-instruction_wx_2_de 0007.pdf: Not consuming ALU-WX-instruction_wx_2_de 0007.pdf: It is a duplicate of ALU-WX-instruction_wx_2_de (#1594)') Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/celery/app/trace.py", line 453, in trace_task R = retval = fun(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/celery/app/trace.py", line 736, in __protected_call__ return self.run(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/asgiref/sync.py", line 327, in main_wrap raise exc_info[1] File "/usr/src/paperless/src/documents/tasks.py", line 151, in consume_file msg = plugin.run() ^^^^^^^^^^^^ File "/usr/src/paperless/src/documents/consumer.py", line 502, in run self.pre_check_duplicate() File "/usr/src/paperless/src/documents/consumer.py", line 326, in pre_check_duplicate self._fail( File "/usr/src/paperless/src/documents/consumer.py", line 302, in _fail raise ConsumerError(f"{self.filename}: {log_message or message}") from exception Quote abschließend, docker run <<click<< der besagten docker's bitte mal posten docker run -d --name='paperless-ngx' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="heimdall2" -e HOST_CONTAINERNAME="paperless-ngx" -e 'PAPERLESS_REDIS'='redis://192.168.1.58:6379' -e 'PAPERLESS_OCR_LANGUAGE'='deu+eng' -e 'PAPERLESS_OCR_LANGUAGES'='' -e 'PAPERLESS_FILENAME_FORMAT'='{created}_{document_type}_{title}_{correspondent}_{tag_list}' -e 'PAPERLESS_TIME_ZONE'='Europe/Berlin' -e 'PAPERLESS_CONSUMER_ENABLE_BARCODES'='true' -e 'PAPERLESS_CONSUMER_ASN_BARCODE_PREFIX'='ASN' -e 'PAPERLESS_CONSUMER_ENABLE_ASN_BARCODE'='true' -e 'PAPERLESS_CONSUMER_BARCODE_UPSCALE'='2.0' -e 'PAPERLESS_FILENAME_FORMAT_REMOVE_NONE'='true' -e 'PAPERLESS_CONSUMER_BARCODE_DPI'='600' -e 'PAPERLESS_IGNORE_DATES'='' -e 'PAPERLESS_CONSUMER_POLLING'='0' -e 'PAPERLESS_SECRET_KEY'='e11fl1oa-*ytql8p)(06fbj4ukrlo+n7k&q5+$1md7i+mge=ee' -e 'USERMAP_UID'='99' -e 'USERMAP_GID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/selfhosters/unRAID-CA-templates/master/templates/img/paperless.png' -p '8000:8000/tcp' -v '/mnt/user/appdata/paperless-ngx/data':'/usr/src/paperless/data':'rw' -v '/mnt/user/paperless/ablage/':'/usr/src/paperless/media':'rw' -v '/mnt/user/paperless/scan/':'/usr/src/paperless/consume':'rw' 'ghcr.io/paperless-ngx/paperless-ngx' 156066cceef689c72045fabaa4f2fc4f7cc399d206b3bab37b66539c44e40cf3 Der Befehl wurde erfolgreich ausgeführt! Quote zusätzlich vielleicht noch ne diagnostics <<click<< anhängen heimdall2-diagnostics-20240702-2220.zip Edited July 2 by elbadepadualima Quote Link to comment
alturismo Posted July 3 Share Posted July 3 On 7/1/2024 at 11:03 PM, elbadepadualima said: Seit ich auf die aktuelle Version geupdatet habe (ich habe Paperless immer aktuell gehalten), flutet der Container mein docker.img. laut logs hattest du bereits RAM Auslastungsprobleme im April, das ist ein Anzeichen das der RAM am Anschlag ist und es anfängt Prozesse zabzustürzen Apr 15 19:17:28 heimdall2 nginx: 2024/04/15 19:17:28 [alert] 12049#12049: worker process 19490 exited on signal 6 Apr 15 19:17:30 heimdall2 nginx: 2024/04/15 19:17:30 [alert] 12049#12049: worker process 9079 exited on signal 6 Apr 15 19:17:32 heimdall2 nginx: 2024/04/15 19:17:32 [alert] 12049#12049: worker process 9164 exited on signal 6 Apr 15 19:17:32 heimdall2 nginx: 2024/04/15 19:17:32 [alert] 12049#12049: worker process 9187 exited on signal 6 Apr 15 19:17:34 heimdall2 nginx: 2024/04/15 19:17:34 [alert] 12049#12049: worker process 9188 exited on signal 6 ... .. . ~ 3000 x ... kommt häufiger vor, ebenso gestern Abend ... Jul 2 22:20:23 heimdall2 nginx: 2024/07/02 22:20:23 [alert] 11822#11822: worker process 15650 exited on signal 6 Jul 2 22:20:24 heimdall2 nginx: 2024/07/02 22:20:24 [alert] 11822#11822: worker process 9792 exited on signal 6 Jul 2 22:20:25 heimdall2 nginx: 2024/07/02 22:20:25 [alert] 11822#11822: worker process 9800 exited on signal 6 ... .. . 6 hours ago, elbadepadualima said: der Docker startet und nach 2-3Minuten geht die Speicherauslastung des Dockers rapide nach oben, 400-600MB pro Minute. daher, ich frag nochmal nach, reden wir über RAM (Arbeitsspeicher) oder Docker Image (SSD/nvme/HDD) ? wobei ich hierzu sagen würde, frrga im github von paperless nach (passend zu deinem genutzten docker) mit der Fehlermeldung, die wissen sicherlich eher was da schief läuft .... Anmerkungen nebenbei noch erwähnt, disk1 error war auch mal da, scheint aber nichts mehr zu kommen hierzu ... Jun 10 02:41:31 heimdall2 kernel: md: disk1 read error, sector=5665449456 Jun 10 02:41:31 heimdall2 kernel: md: disk1 read error, sector=5665449464 Jun 10 02:41:31 heimdall2 kernel: md: disk1 read error, sector=5665449472 ... .. . ich hoffe du installiert das nicht alles ... und wenn doch, warum ? /boot/config/plugins/NerdPack/packages/6.10/: total 125852 -rw------- 1 root root 24320 Aug 31 2022 anacron-2.3-x86_64-3_slonly.txz -rw------- 1 root root 263144 Aug 31 2022 apr-1.6.5-x86_64-1.txz -rw------- 1 root root 137860 Aug 31 2022 apr-util-1.6.1-x86_64-7.txz -rw------- 1 root root 355880 Aug 31 2022 arp-scan-1.9.6-x86_64-1cf.txz -rw------- 1 root root 127956 Aug 31 2022 atop-2.2-x86_64-2.txz -rw------- 1 root root 218476 Aug 31 2022 avfs-1.0.5-x86_64-1_slonly.txz -rw------- 1 root root 44160 Aug 31 2022 axel-2.4-x86_64-2_slonly.txz -rw------- 1 root root 166984 Aug 31 2022 bash-completion-2.8-noarch-1.txz -rw------- 1 root root 43044 Aug 31 2022 bashtop-0.8.17-x86_64-1cf.txz -rw------- 1 root root 116064 Aug 31 2022 bc-1.07.1-x86_64-2.txz -rw------- 1 root root 1088224 Aug 31 2022 bluez-5.50-x86_64-2.txz -rw------- 1 root root 4169268 Aug 31 2022 borgbackup-1.1.15-x86_64-1.txz -rw------- 1 root root 41644 Aug 31 2022 bwm-ng-0.6-x86_64-1_SBo.txz -rw------- 1 root root 63740 Aug 31 2022 byobu-2.82-x86_64-3_slonly.txz -rw------- 1 root root 919944 Aug 31 2022 ccat-1.1.0-x86_64-1.txz -rw------- 1 root root 883000 Aug 31 2022 cdrtools-3.01-x86_64-3.txz -rw------- 1 root root 22968 Aug 31 2022 cksfv-1.3.14-x86_64-1_slack.txz -rw------- 1 root root 19604 Aug 31 2022 colordiff-1.0.18-noarch-1_slonly.txz -rw------- 1 root root 31068 Aug 31 2022 convmv-1.15-x86_64-2_slonly.txz -rw------- 1 root root 3621776 Aug 31 2022 ctop-0.7.3-x86_64-1.txz -rw------- 1 root root 99740 Aug 31 2022 ddrescue-1.23-x86_64-2.txz -rw------- 1 root root 3543304 Aug 31 2022 dry-0.9.4-x86_64-1.txz -rw------- 1 root root 83792 Aug 31 2022 dstat-0.7.3-noarch-1.txz -rw------- 1 root root 715608 Aug 31 2022 elfutils-0.176-x86_64-1.txz -rw------- 1 root root 3303624 Aug 31 2022 exiftool-11.93-x86_64-1cf.txz -rw------- 1 root root 300172 Aug 31 2022 expect-5.45.4-x86_64-2.txz -rw------- 1 root root 16504 Aug 31 2022 fasd-1.0.1-x86_64-1.txz -rw------- 1 root root 657360 Aug 31 2022 fd-6.2.0-x86_64-1_slonly.txz -rw------- 1 root root 17484 Aug 31 2022 fdupes-1.51-x86_64-3_slack.txz -rw------- 1 root root 101880 Aug 31 2022 figlet-2.2.5-x86_64-2_slonly.txz -rw------- 1 root root 463692 Aug 31 2022 fio-3.23-x86_64-1_SBo.txz -rw------- 1 root root 2517236 Aug 31 2022 fish-3.1.0-x86_64-1_slonly.txz -rw------- 1 root root 28176 Aug 31 2022 fping-4.2-x86_64-1cf.txz -rw------- 1 root root 161868 Aug 31 2022 fswatch-1.9.3-x86_64-1.txz -rw------- 1 root root 26000 Aug 31 2022 fuseiso-20070708-x86_64-2.txz -rw------- 1 root root 901728 Aug 31 2022 fzf-0.20.0-x86_64-3_slonly.txz -rw------- 1 root root 25892 Aug 31 2022 gcp-0.1.3-x86_64-3_slonly.txz -rw------- 1 root root 2211012 Aug 31 2022 git-lfs-2.4.2-x86_64-1_slonly.txz -rw------- 1 root root 1013972 Aug 31 2022 httrack-3.49.2-x86_64-1.txz -rw------- 1 root root 22048 Aug 31 2022 idle3-tools-0.9.1-x86_64-1.txz -rw------- 1 root root 40296 Aug 31 2022 iftop-1.0.4-x86_64-2.txz -rw------- 1 root root 50268 Aug 31 2022 iotop-0.6-x86_64-1_fs.tgz -rw------- 1 root root 86108 Aug 31 2022 iperf3-3.9-x86_64-1cf.txz -rw------- 1 root root 1028544 Aug 31 2022 ipmitool-1.8.18-x86_64-1.txz -rw------- 1 root root 651960 Aug 31 2022 irssi-1.2.1-x86_64-1.txz -rw------- 1 root root 45560 Aug 31 2022 jdupes-1.19.1-x86_64-1_SBo.txz -rw------- 1 root root 48832 Aug 31 2022 jhead-3.00-x86_64-1_slack.txz -rw------- 1 root root 496868 Aug 31 2022 joe-4.6-x86_64-2.txz -rw------- 1 root root 1147168 Aug 31 2022 kbd-1.15.3-x86_64-2.txz -rw------- 1 root root 36596 Aug 31 2022 keychain-2.8.5-x86_64-1cf.txz -rw------- 1 root root 687760 Aug 31 2022 ksh93-2018.10.18-x86_64-1.txz -rw------- 1 root root 903664 Aug 31 2022 lftp-4.9.1-x86_64-1.txz -rw------- 1 root root 2359380 Aug 31 2022 libmediainfo-19.09-x86_64-1_SBo.txz -rw------- 1 root root 366184 Aug 31 2022 libzen-0.4.37-x86_64-1_SBo.txz -rw------- 1 root root 353420 Aug 31 2022 llfuse-1.3.8-x86_64-1_SBo.txz -rw------- 1 root root 212244 Aug 31 2022 lrzip-0.631-x86_64-1.txz -rw------- 1 root root 1739904 Aug 31 2022 lynx-2.8.9.1-x86_64-1.txz -rw------- 1 root root 339460 Aug 31 2022 mcelog-161-x86_64-1.txz -rw------- 1 root root 132400 Aug 31 2022 md5deep-4.4-x86_64-2.txz -rw------- 1 root root 68712 Aug 31 2022 mediainfo-19.09-x86_64-1_SBo.txz -rw------- 1 root root 18116 Aug 31 2022 mktorrent-1.1-x86_64-1.txz -rw------- 1 root root 50648 Aug 31 2022 moreutils-0.63-x86_64-1_slonly.txz -rw------- 1 root root 210120 Aug 31 2022 mosh-1.3.2-x86_64-9cf.txz -rw------- 1 root root 66640 Aug 31 2022 mtr-0.92-x86_64-2.txz -rw------- 1 root root 133948 Aug 31 2022 multitail-6.4.2-x86_64-1.txz -rw------- 1 root root 53592 Aug 31 2022 nc-1.10-x86_64-1.txz -rw------- 1 root root 43864 Aug 31 2022 ncdu-1.15.1-x86_64-1cf.txz -rw------- 1 root root 208648 Aug 31 2022 ncurses-terminfo-6.1.20191130-x86_64-1.txz -rw------- 1 root root 81136 Aug 31 2022 neofetch-20200708-noarch-1.txz -rw------- 1 root root 212404 Aug 31 2022 neon-0.30.2-x86_64-1.txz -rw------- 1 root root 203428 Aug 31 2022 netcat-openbsd-1.105-x86_64-2.tgz -rw------- 1 root root 45612 Aug 31 2022 nethogs-0.8.5-x86_64-5cf.txz -rw------- 1 root root 59996 Aug 31 2022 nload-0.7.4-x86_64-1_slack.txz -rw------- 1 root root 142952 Aug 31 2022 nmon-16m-x86_64-1_SBo.txz -rw------- 1 root root 319212 Aug 31 2022 nvme-cli-1.11-x86_64-1_slonly.txz -rw------- 1 root root 1285484 Aug 31 2022 p7zip-16.02-x86_64-1sl.txz -rw------- 1 root root 26199 Aug 31 2022 packages-desc -rw------- 1 root root 138182 Aug 31 2022 packages.json -rw------- 1 root root 113088 Aug 31 2022 par2cmdline-0.8.0-x86_64-1_slonly.txz -rw------- 1 root root 1132288 Aug 31 2022 parallel-20160822-x86_64-1_slonly.txz -rw------- 1 root root 16127512 Aug 31 2022 perl-5.32.0-x86_64-1.txz -rw------- 1 root root 63420 Aug 31 2022 pigz-2.4-x86_64-1_slonly.txz -rw------- 1 root root 204328 Aug 31 2022 powertop-2.13-x86_64-1.txz -rw------- 1 root root 23828 Aug 31 2022 progress-0.14-x86_64-1_slonly.txz -rw------- 1 root root 2360956 Aug 31 2022 protobuf-3.7.1-x86_64-1cf.txz -rw------- 1 root root 496304 Aug 31 2022 psutil-5.7.3-x86_64-3cf.txz -rw------- 1 root root 1761948 Aug 31 2022 python-pip-21.2.3-x86_64-1.txz -rw------- 1 root root 673896 Aug 31 2022 python-setuptools-57.4.0-x86_64-1.txz -rw------- 1 root root 13018740 Aug 31 2022 python2-2.7.18-x86_64-4.txz -rw------- 1 root root 18419532 Aug 31 2022 python3-3.9.6-x86_64-1.txz -rw------- 1 root root 310284 Aug 31 2022 ranger-1.9.2-x86_64-1cf.txz -rw------- 1 root root 290256 Aug 31 2022 rar-5.8.1-x86_64-1_SBo.txz -rw------- 1 root root 168232 Aug 31 2022 rar2fs-1.29.0-x86_64-1_SBo.txz -rw------- 1 root root 295052 Aug 31 2022 readline-7.0-x86_64-1.txz -rw------- 1 root root 21136 Aug 31 2022 reptyr-0.6.2-x86_64-3.txz -rw------- 1 root root 857692 Aug 31 2022 ripgrep-0.7.1-x86_64-3_slonly.txz -rw------- 1 root root 88652 Aug 31 2022 rmlint-2.4.6-x86_64-1.txz -rw------- 1 root root 112868 Aug 31 2022 rsnapshot-1.4.2-x86_64-1.txz -rw------- 1 root root 556816 Aug 31 2022 screen-4.8.0-x86_64-4.txz -rw------- 1 root root 63612 Aug 31 2022 serf-1.3.9-x86_64-3.txz -rw------- 1 root root 875576 Aug 31 2022 sg3utils-1.45-x86_64-1.txz -rw------- 1 root root 28504 Aug 31 2022 slocate-3.1-x86_64-4.txz -rw------- 1 root root 263908 Aug 31 2022 socat-1.7.3.2-x86_64-3cf.txz -rw------- 1 root root 41480 Aug 31 2022 sshfs-fuse-2.8-x86_64-1sl.txz -rw------- 1 root root 347984 Aug 31 2022 strace-4.26-x86_64-1.txz -rw------- 1 root root 673064 Aug 31 2022 strongswan-5.3.4-x86_64-3.txz -rw------- 1 root root 170428 Aug 31 2022 stunnel-5.50-x86_64-1.txz -rw------- 1 root root 4887620 Aug 31 2022 subversion-1.13.0-x86_64-1.txz -rw------- 1 root root 337596 Aug 31 2022 sysstat-12.1.6-x86_64-1.txz -rw------- 1 root root 2921648 Aug 31 2022 tcl-8.6.10-x86_64-1.txz -rw------- 1 root root 3767708 Aug 31 2022 tcllib-1.20-x86_64-1_slonly.txz -rw------- 1 root root 370908 Aug 31 2022 tcpdump-4.9.2-x86_64-3.txz -rw------- 1 root root 434188 Aug 31 2022 testdisk-7.0-x86_64-2.txz -rw------- 1 root root 111320 Aug 31 2022 tinc-1.0.34-x86_64-1.txz -rw------- 1 root root 366896 Aug 31 2022 tmux-3.2-x86_64-1.txz -rw------- 1 root root 36244 Aug 31 2022 unionfs-fuse-0.26-x86_64-1dj.txz -rw------- 1 root root 347692 Aug 31 2022 unrar-5.8.5-x86_64-1_SBo.txz -rw------- 1 root root 57944 Aug 31 2022 utf8proc-2.4.0-x86_64-1.txz -rw------- 1 root root 597208 Aug 31 2022 vifm-0.10.1-x86_64-2cf.txz -rw------- 1 root root 7062672 Aug 31 2022 vim-8.1.0727-x86_64-1.txz -rw------- 1 root root 1593076 Aug 31 2022 virtualenv-13.1.2-x86_64-1_slack.txz -rw------- 1 root root 93656 Aug 31 2022 vnstat-2.1-x86_64-1.txz -rw------- 1 root root 69612 Aug 31 2022 wd5741-1.0.0-x86_64-1.txz -rw------- 1 root root 122084 Aug 31 2022 xinetd-2.3.15-x86_64-3.txz -rw------- 1 root root 170036 Aug 31 2022 zpaq-7.15-x86_64-1_slonly.txz -rw------- 1 root root 3053312 Aug 31 2022 zsh-5.8-x86_64-1.txz warum du das aktiviert hast wird auch seine Gründe haben ... BOOT_IMAGE=/bzimage pcie_acs_override=downstream,multifunction initrd=/bzroot bei der Systemauslastung, deine Frigate VM braucht Dampf ... ja ... aber es ist nichts so auffälliges da was das verursacht, zumindest nicht augenscheinlich für mich ... deiner RAM Bestückung mit 32 + 8 ist auch "ungewöhnlich", aber ok mehr macht bei den logs aktuell keinen Spaß zu schauen, aber wie erwähnt, wenn du es isolieren kannst auf paperless dann würde ich dort mal nachhaken. Quote Link to comment
elbadepadualima Posted July 3 Author Share Posted July 3 Quote laut logs hattest du bereits RAM Auslastungsprobleme im April, das ist ein Anzeichen das der RAM am Anschlag ist und es anfängt Prozesse zabzustürzen Kann ich nicht bestätigen, auch wenn es das log sagt. Die Auslastung vom Arbeitsspeicher liegt im Schnitt so bei 20%. Quote kommt häufiger vor, ebenso gestern Abend ... Damit muss ich mich beschäftigen, aber spürbare Probleme habe ich mit nginx nicht. Quote daher, ich frag nochmal nach, reden wir über RAM (Arbeitsspeicher) oder Docker Image (SSD/nvme/HDD) ? Wie geschrieben, das Docker Image wird voll geschrieben, die Auslastung des Arbeitsspeichers liegt weiterhin bei den bereits genannten 20%. Quote wobei ich hierzu sagen würde, frrga im github von paperless nach (passend zu deinem genutzten docker) mit der Fehlermeldung, die wissen sicherlich eher was da schief läuft .... Dies werde ich versuche, da ein ähnliches Problem aber auch bei Thunderbird auftritt habe vermute ich eine andere Ursache. Quote ich hoffe du installiert das nicht alles ... und wenn doch, warum ? Nein, nur powertop...das sind Überbleibsel von Nerdpack. Das habe ich heute gleich behoben. Quote Link to comment
Solution elbadepadualima Posted July 3 Author Solution Share Posted July 3 Ich habe gerade noch etwas gesucht und ich bin nicht der einzige mit dem Problem. Ich teste gerade das Mappen des /tmp bereichs auf einen Bereich außerhalb des Containers. Bis jetzt funktioniert dies recht gut. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.