Jump to content
We're Hiring! Full Stack Developer ×

Paperless-ng


Hoddl

Recommended Posts

Nein, weil theoretisch wird das erst nach dem starten vom Docker gemacht. Sprich bis dahin sollte schon alles laufen.

Alternativ kann man auch im Template 

PAPERLESS_ADMIN_USER

PAPERLESS_ADMIN_PASSWORD

eintragen. Trotzdem würde er nicht zum Redis verbinden.

 

Die Infos sind aktuell etwas spärlich und das macht es schwierig :D

Link to comment

alles so gemacht wie beschrieben auch mit dem superuser...

 

keine verbindung zu redis

 

im docker von paperless finde ich keinen eintrag um redis einzutragen ist das richtig so?

 

hier mal das protokoll:

FehlerWarnungSystemArrayAnmelden


Paperless-ng docker container starting...
Mapping UID and GID for paperless:paperless to 99:100
Creating directory ../data/index
Creating directory ../media/documents
Creating directory ../media/documents/originals
Creating directory ../media/documents/thumbnails
Creating directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Apply database migrations...
Operations to perform:
Apply all migrations: admin, auth, authtoken, contenttypes, django_q, documents, paperless_mail, sessions
Running migrations:
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying admin.0003_logentry_add_action_flag_choices... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying auth.0002_alter_permission_name_max_length... OK
Applying auth.0003_alter_user_email_max_length... OK
Applying auth.0004_alter_user_username_opts... OK
Applying auth.0005_alter_user_last_login_null... OK
Applying auth.0006_require_contenttypes_0002... OK
Applying auth.0007_alter_validators_add_error_messages... OK
Applying auth.0008_alter_user_username_max_length... OK
Applying auth.0009_alter_user_last_name_max_length... OK
Applying auth.0010_alter_group_name_max_length... OK
Applying auth.0011_update_proxy_permissions... OK
Applying auth.0012_alter_user_first_name_max_length... OK
Applying authtoken.0001_initial... OK
Applying authtoken.0002_auto_20160226_1747... OK
Applying authtoken.0003_tokenproxy... OK
Applying django_q.0001_initial... OK
Applying django_q.0002_auto_20150630_1624... OK
Applying django_q.0003_auto_20150708_1326... OK
Applying django_q.0004_auto_20150710_1043... OK
Applying django_q.0005_auto_20150718_1506... OK
Applying django_q.0006_auto_20150805_1817... OK
Applying django_q.0007_ormq... OK
Applying django_q.0008_auto_20160224_1026... OK
Applying django_q.0009_auto_20171009_0915... OK
Applying django_q.0010_auto_20200610_0856... OK
Applying django_q.0011_auto_20200628_1055... OK
Applying django_q.0012_auto_20200702_1608... OK
Applying django_q.0013_task_attempt_count... OK
Applying django_q.0014_schedule_cluster... OK
Applying documents.0001_initial... OK
Applying documents.0002_auto_20151226_1316... OK
Applying documents.0003_sender... OK
Applying documents.0004_auto_20160114_1844... OK
Applying documents.0005_auto_20160123_0313... OK
Applying documents.0006_auto_20160123_0430... OK
Applying documents.0007_auto_20160126_2114... OK
Applying documents.0008_document_file_type... OK
Applying documents.0009_auto_20160214_0040... OK
Applying documents.0010_log... OK
Applying documents.0011_auto_20160303_1929... OK
Applying documents.0012_auto_20160305_0040... OK
Applying documents.0013_auto_20160325_2111... OK
Applying documents.0014_document_checksum... OK
Applying documents.0015_add_insensitive_to_match... OK
Applying documents.0016_auto_20170325_1558... OK
Applying documents.0017_auto_20170512_0507... OK
Applying documents.0018_auto_20170715_1712... OK
Applying documents.0019_add_consumer_user... OK
Applying documents.0020_document_added... OK
Applying documents.0021_document_storage_type... OK
Applying documents.0022_auto_20181007_1420... OK
Applying documents.0023_document_current_filename... OK
Applying documents.1000_update_paperless_all... OK
Applying documents.1001_auto_20201109_1636... OK
Applying documents.1002_auto_20201111_1105... OK
Applying documents.1003_mime_types... OK
Applying documents.1004_sanity_check_schedule... OK
Applying documents.1005_checksums... OK
Applying documents.1006_auto_20201208_2209... OK
Applying documents.1007_savedview_savedviewfilterrule... OK
Applying documents.1008_auto_20201216_1736... OK
Applying documents.1009_auto_20201216_2005... OK
Applying documents.1010_auto_20210101_2159... OK
Applying documents.1011_auto_20210101_2340... OK
Applying documents.1012_fix_archive_files... OK
Applying documents.1013_migrate_tag_colour... OK
Applying documents.1014_auto_20210228_1614... OK
Applying documents.1015_remove_null_characters... OK
Applying documents.1016_auto_20210317_1351... OK
Applying paperless_mail.0001_initial... OK
Applying paperless_mail.0002_auto_20201117_1334... OK
Applying paperless_mail.0003_auto_20201118_1940... OK
Applying paperless_mail.0004_mailrule_order... OK
Applying paperless_mail.0005_help_texts... OK
Applying paperless_mail.0006_auto_20210101_2340... OK
Applying paperless_mail.0007_auto_20210106_0138... OK
Applying paperless_mail.0008_auto_20210516_0940... OK
Applying sessions.0001_initial... OK
Search index out of date. Updating...
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
2022-01-20 23:09:24,033 INFO Set uid to user 0 succeeded
2022-01-20 23:09:24,038 INFO supervisord started with pid 1
2022-01-20 23:09:25,041 INFO spawned: 'consumer' with pid 61
2022-01-20 23:09:25,045 INFO spawned: 'gunicorn' with pid 62
2022-01-20 23:09:25,048 INFO spawned: 'scheduler' with pid 63
[2022-01-20 23:09:25 +0100] [62] [INFO] Starting gunicorn 20.1.0
[2022-01-20 23:09:25 +0100] [62] [INFO] Listening at: http://0.0.0.0:8000 (62)
[2022-01-20 23:09:25 +0100] [62] [INFO] Using worker: paperless.workers.ConfigurableWorker
[2022-01-20 23:09:25 +0100] [62] [INFO] Server is ready. Spawning workers
2022-01-20 23:09:26,715 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-20 23:09:26,715 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-20 23:09:26,716 INFO success: scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[2022-01-20 23:09:26,973] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/src/../consume
23:09:27 [Q] INFO Q Cluster bakerloo-neptune-king-nebraska starting.
23:09:27 [Q] ERROR Can not connect to Redis server.
Process Process-1:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 559, in connect
sock = self._connect()
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 584, in _connect
for res in socket.getaddrinfo(self.host, self.port, self.socket_type,
File "/usr/local/lib/python3.9/socket.py", line 953, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/local/lib/python3.9/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.9/site-packages/django_q/cluster.py", line 168, in __init__
self.start()
File "/usr/local/lib/python3.9/site-packages/django_q/cluster.py", line 171, in start
self.broker.ping()
File "/usr/local/lib/python3.9/site-packages/django_q/brokers/redis_broker.py", line 39, in ping
raise e
File "/usr/local/lib/python3.9/site-packages/django_q/brokers/redis_broker.py", line 36, in ping
return self.connection.ping()
File "/usr/local/lib/python3.9/site-packages/redis/client.py", line 1378, in ping
return self.execute_command('PING')
File "/usr/local/lib/python3.9/site-packages/redis/client.py", line 898, in execute_command
conn = self.connection or pool.get_connection(command_name, **options)
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 1192, in get_connection
connection.connect()
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 563, in connect
raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error -2 connecting to replace-with-ip:6379. Name or service not known.
[2022-01-20 23:11:25 +0100] [62] [CRITICAL] WORKER TIMEOUT (pid:65)
[2022-01-20 23:11:25 +0100] [62] [WARNING] Worker with pid 65 was terminated due to signal 6

 

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...