Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

appdata-Ordner (fast) leer

Featured Replies

Liebe Community,

ich bin in der Mitte meiner Unraid-Testphase und frage mich so langsam, ob Unraid nicht viel zu kompliziert für mich ist....

 

Konkret habe ich große Probleme, apps wie Paperless-ngx zum Laufen zu bringen. 

Mittlerweile glaube ich, dass ein Grund dafür ist, dass ich außer NginxProxManager und filebrowser (hatte ich schon wieder deinstalliert) keine Ordner unter appdata habe, obwohl ich paperless-ngx, cloudfare-DDNS und Redis installiert habe. Deswegen muss ich vermutlich jedes Mal den superuser in paperless neu anlegen, wenn ich etwas im Template ändere.

 

Ich habe das diagnostics.zip beigefügt. Vielleicht wisst Ihr ja, welchen Fehler ich gemacht habe und wie ich ihn wieder korrigieren kann? Das wäre super toll! Vielen Dank!

unraid22-diagnostics-20241116-1557.zip

Solved by alturismo

38 minutes ago, Oliver22 said:

Ich habe das diagnostics.zip beigefügt. Vielleicht wisst Ihr ja, welchen Fehler ich gemacht habe und wie ich ihn wieder korrigieren kann? Das wäre super toll! Vielen Dank!

 

zuerst mal entferne das tweks plugin, dein system wirdt haufenweise Fehler aus wegen Stromsparmechanismen ...

 

zu deinen Dockers, zeig mal bitte den docker run <<click<< um zu prüfen wo du was speicherst, ebenso einen screen deiner Main Seite (Übersicht der Platten) und einen screenshot deiner Share settings, angefangen mit system und appdata, dann kann man weiter schauen.

 

das Fehlerbild beschreibt "verlorene" Daten weil du "in den Docker" schreibst anstelle auf appdata (persistent storage", was schon merkwürdig ist

  • Author

Hi Alturismo,

vielen Dank für Deine schnelle Antwort.

Das AutoTweak-plugin habe ich entfernt.

docker run (paperless-ngx):

Screenshot-2024-11-16-173048.png

 

[2024-11-16 17:30:44 +0100] [197] [INFO] Starting gunicorn 23.0.0
[2024-11-16 17:30:44 +0100] [197] [INFO] Listening at: http://[::]:8000 (197)
[2024-11-16 17:30:44 +0100] [197] [INFO] Using worker: paperless.workers.ConfigurableWorker
[2024-11-16 17:30:44 +0100] [197] [INFO] Server is ready. Spawning workers
[2024-11-16 17:30:44,274] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/consume
[2024-11-16 17:30:44,462] [INFO] [celery.beat] beat: Starting...
[2024-11-16 17:30:44,530] [INFO] [celery.worker.consumer.connection] Connected to redis://192.168.178.175:6379//
[2024-11-16 17:30:44,536] [INFO] [celery.apps.worker] celery@ea13495a0633 ready.
  Applying documents.1045_alter_customfieldinstance_value_monetary_squashed_1049_document_deleted_at_document_restored_at... OK
  Applying documents.1050_customfield_extra_data_and_more... OK
  Applying documents.1051_alter_correspondent_owner_alter_document_owner_and_more... OK
  Applying documents.1052_document_transaction_id... OK
  Applying documents.1053_document_page_count... OK
  Applying documents.1054_customfieldinstance_value_monetary_amount_and_more... OK
  Applying documents.1055_alter_storagepath_path... OK
  Applying documents.1056_customfieldinstance_deleted_at_and_more... OK
  Applying guardian.0001_initial... OK
  Applying guardian.0002_generic_permissions_index... OK
  Applying paperless.0001_initial... OK
  Applying paperless.0002_applicationconfiguration_app_logo_and_more... OK
  Applying paperless.0003_alter_applicationconfiguration_max_image_pixels... OK
  Applying paperless_mail.0025_alter_mailaccount_owner_alter_mailrule_owner_and_more... OK
  Applying paperless_mail.0026_mailrule_enabled... OK
  Applying paperless_mail.0027_mailaccount_expiration_mailaccount_account_type_and_more... OK
  Applying paperless_mail.0028_alter_mailaccount_password_and_more... OK
  Applying sessions.0001_initial... OK
  Applying socialaccount.0001_initial... OK
  Applying socialaccount.0002_token_max_lengths... OK
  Applying socialaccount.0003_extra_data_default_dict... OK
  Applying socialaccount.0004_app_provider_id_settings... OK
  Applying socialaccount.0005_socialtoken_nullable_app... OK
  Applying socialaccount.0006_alter_socialaccount_extra_data... OK
Running Django checks
System check identified no issues (0 silenced).
Search index out of date. Updating...
Executing /usr/local/bin/paperless_cmd.sh
2024-11-16 17:30:41,439 INFO Set uid to user 0 succeeded
2024-11-16 17:30:41,440 INFO supervisord started with pid 1
2024-11-16 17:30:42,442 INFO spawned: 'gunicorn' with pid 197
2024-11-16 17:30:42,443 INFO spawned: 'celery' with pid 198
2024-11-16 17:30:42,444 INFO spawned: 'celery-beat' with pid 199
2024-11-16 17:30:42,444 INFO spawned: 'consumer' with pid 200
2024-11-16 17:30:42,445 INFO spawned: 'celery-flower' with pid 201
Checking if we should start flower...
Not starting flower
2024-11-16 17:30:42,448 INFO success: celery-flower entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-11-16 17:30:42,448 INFO exited: celery-flower (exit status 0; expected)
celery beat v5.4.0 (opalescent) is starting.
2024-11-16 17:30:44,266 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-11-16 17:30:44,266 INFO success: celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-11-16 17:30:44,266 INFO success: celery-beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-11-16 17:30:44,266 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
__    -    ... __   -        _
LocalTime -> 2024-11-16 17:30:44
Configuration ->
    . broker -> redis://192.168.178.175: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)
 
 -------------- celery@ea13495a0633 v5.4.0 (opalescent)
--- ***** ----- 
-- ******* ---- Linux-6.1.106-Unraid-x86_64-with-glibc2.36 2024-11-16 17:30:44
- *** --- * --- 
- ** ---------- [config]
- ** ---------- .> app:         paperless:0x14c7a052f6b0
- ** ---------- .> transport:   redis://192.168.178.175: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

 

Screenshot share setting system

Screenshot-2024-11-16-173739.png

 

Screenshot share appdata

Screenshot-2024-11-16-174040.png

 

Screenshot Main:

Screenshot-2024-11-16-174348.png

 

Ich hoffe, das ist alles, was Du brauchst. Bin gespannt, welchen Fehler ich gemacht habe. Vielen Dank!

 

  • Solution
31 minutes ago, Oliver22 said:

docker run (paperless-ngx):

 

wie erwartet, dir fehlt der mount von der config

 

image.png.9d5ebbdfb61c286ade269acaadd9ac72.png

 

sprich, das bleibt innerhalb des Dockers und ist bei jedem Update, Redo Config, ... weg ;)

 

entweder fehlt der im template oder du hast ihn (versehentlich) gelöscht ...

  • Author

Vielen Dank! Das war es!

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.