Kriege Papermerge nicht zum laufen

Legolas · 2. Oktober 2022

Hallo zusammen,

Raspberry 4, 4GB RAM, OS Dietpi (aktuell). Ich habe nach Anleitung (https://papermerge.readthedocs.io/en/v2.0.1/setup/docker.html) installiert. Lief alles ohne Fehler. Nun sieht das so aus:

[+] Running 8/8
⠿ Network docker_default Created
⠿ Volume "docker_postgres_data" Created
⠿ Volume "docker_redisdata" Created
⠿ Volume "docker_media_root" Created
⠿ Container postgres_db Started
⠿ Container papermerge_worker Started
⠿ Container redis Started
⠿ Container papermerge_app Started

-- Setup fertig

root@DietPi:~/papermerge-proj/docker# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
95af690c9689 postgres:12.3 "docker-entrypoint.s…" 6 minutes ago Up 6 minutes 5432/tcp postgres_db
bcd2fd35f2d3 redis:6 "docker-entrypoint.s…" 6 minutes ago Up 6 minutes 127.0.0.1:6379->6379/tcp redis

Laut Doku sollte das Webinterface auf Port 8000 erreichbar sein, so steht das auch in der docker-compose.yml, da tut sich aber nix.

Habt Ihr einen Tipp wo ich noch suchen kann?

Danke
SW

madmax2010 · 2. Oktober 2022

mit welchem befehl exakt hast du gestartet?
sehe da nur postgres und redis.
Ich lass das gerade auch mal hoch kommen.. sek

Legolas · 2. Oktober 2022

Da steht doch das angeblich alles gestartet wurde ....

madmax2010 · 2. Oktober 2022

ist da auch die zeile:

0.0.0.0:8000->8000/tcp, :::8000->8000/tcp papermerge_app

al in all sollte das so aussehen:

(base) ➜ docker gitmaster) docker ps
19bcb2ce2fb6 eugenci/papermerge:2.0.0 "/opt/app/startup.sh" 26 seconds ago Up 24 seconds 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp papermerge_app

fd80a3e89437 eugenci/papermerge-worker:v2.0.0 "/opt/app/startup.sh" 26 seconds ago Up 25 seconds papermerge_worker

9518148c9b73 postgres:12.3 "docker-entrypoint.s…" 26 seconds ago Up 25 seconds 5432/tcp postgres_db

cf8f4732879f redis:6 "docker-entrypoint.s…" 26 seconds ago Up 25 seconds 127.0.0.1:6379->6379/tcp redis

die 4 elemente sollten hochkommen.
In den logs sehe ich, dass dem app image tesseract fehlt

zeig gern direkt
curl -I http://127.0.0.1:8000/accounts/login/\?next\=/
und sudo netstat -tulpn

M-X · 2. Oktober 2022

Was sagen denn die Logs ?

Legolas · 2. Oktober 2022

Jetzt habe ich mal den Host neu gestartet.

Die Container werden nicht automatisch gestartet

root@DietPi:~# curl -I http://127.0.0.1:8000/accounts/login/\?next\=/
curl: (7) Failed to connect to 127.0.0.1 port 8000: Verbindungsaufbau abgelehnt

root@DietPi:~# netstat -tulpn
Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 477/pihole-FTL
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 318/dropbear
tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 533/lighttpd
tcp 0 0 127.0.0.1:5335 0.0.0.0:* LISTEN 463/unbound
tcp 0 0 127.0.0.1:8953 0.0.0.0:* LISTEN 463/unbound
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 477/pihole-FTL
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 1708/docker-proxy
tcp6 0 0 :::53 :::* LISTEN 477/pihole-FTL
tcp6 0 0 :::22 :::* LISTEN 318/dropbear
tcp6 0 0 :::81 :::* LISTEN 533/lighttpd
tcp6 0 0 ::1:8953 :::* LISTEN 463/unbound
tcp6 0 0 ::1:4711 :::* LISTEN 477/pihole-FTL
udp 0 0 0.0.0.0:53 0.0.0.0:* 477/pihole-FTL
udp 0 0 0.0.0.0:67 0.0.0.0:* 477/pihole-FTL
udp 0 0 127.0.0.1:5335 0.0.0.0:* 463/unbound
udp6 0 0 :::53 :::* 477/pihole-FTL

madmax2010 · 2. Oktober 2022

ok, immerhin blockiert dir niemand port 8000

mehr wollte ich da nicht sehen.

dein zeig doch mal wie von @M-X vorgeschlagen die logs beim starten (docker-compose up (ohne -d))

pack die logs gern auf pastebin.. Sonst wird das hier im thread vielleicht ein paar zeichen zu lang.

Legolas · 2. Oktober 2022

root@DietPi:/papermerge-proj/docker# docker-compose up
[+] Running 4/0
⠿ Container papermerge_worker Created 0.0s
⠿ Container redis Created 0.0s
⠿ Container postgres_db Created 0.0s
⠿ Container papermerge_app Created 0.0s
Attaching to papermerge_app, papermerge_worker, postgres_db, redis
papermerge_worker | exec /opt/app/startup.sh: exec format error
redis | 1:C 02 Oct 2022 13:45:24.081 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis | 1:C 02 Oct 2022 13:45:24.082 # Redis version=6.2.7, bits=64, commit=00000000, modified=0, pid=1, just started
redis | 1:C 02 Oct 2022 13:45:24.082 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis | 1:M 02 Oct 2022 13:45:24.092 * monotonic clock: POSIX clock_gettime
redis | 1:M 02 Oct 2022 13:45:24.098 # A key '__redis__compare_helper' was added to Lua globals which is not on the globals allow list nor listed on the deny list.
redis | 1:M 02 Oct 2022 13:45:24.100 * Running mode=standalone, port=6379.
redis | 1:M 02 Oct 2022 13:45:24.101 # Server initialized
postgres_db |
postgres_db | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_db |
redis | 1:M 02 Oct 2022 13:45:24.116 * Loading RDB produced by version 6.2.7
redis | 1:M 02 Oct 2022 13:45:24.116 * RDB age 190 seconds
redis | 1:M 02 Oct 2022 13:45:24.116 * RDB memory usage when created 0.81 Mb
redis | 1:M 02 Oct 2022 13:45:24.116 # Done loading RDB, keys loaded: 0, keys expired: 0.
redis | 1:M 02 Oct 2022 13:45:24.116 * DB loaded from disk: 0.001 seconds
redis | 1:M 02 Oct 2022 13:45:24.116 * Ready to accept connections
papermerge_worker exited with code 1
postgres_db | 2022-10-02 13:45:24.628 UTC [1] LOG: starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
postgres_db | 2022-10-02 13:45:24.631 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_db | 2022-10-02 13:45:24.632 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_db | 2022-10-02 13:45:24.640 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_db | 2022-10-02 13:45:24.766 UTC [26] LOG: database system was shut down at 2022-10-02 13:42:14 UTC
postgres_db | 2022-10-02 13:45:24.806 UTC [1] LOG: database system is ready to accept connections
papermerge_app | exec /opt/app/startup.sh: exec format error
papermerge_app exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
[+] Running 4/4
⠿ Container papermerge_app Stopped 0.0s
⠿ Container papermerge_worker Stopped 0.0s
⠿ Container redis Stopped 0.9s
⠿ Container postgres_db Stopped 0.9s
canceled

Das hat mir zu lange gedauert oder soll ich da warten?

madmax2010 · 2. Oktober 2022

ok, wenn schon nicht auf pastebin, dann pack es doch wenigstens in eine zitat oder code box.
So liest sich das doch grausig...

Sieht soweit ok aus.
als das aktiv war, bevor du es gekillt hast, hast du geschaut, dass die app lief und auf port 8000 lauschte?
dann hast du curl genutzt um zu schauen ob sie errecibar ist?
Falls nein ->

Legolas schrieb:
soll ich da warten

Falls ja: was kam dabei raus?

Legolas · 2. Oktober 2022

Nach 30 Min sieht das so aus ...

root@DietPi:/papermerge-proj/docker# docker-compose up
[+] Running 4/0
⠿ Container redis Running 0.0s
⠿ Container papermerge_worker Created 0.0s
⠿ Container postgres_db Running 0.0s
⠿ Container papermerge_app Created 0.0s
Attaching to papermerge_app, papermerge_worker, postgres_db, redis
papermerge_worker | exec /opt/app/startup.sh: exec format error
papermerge_app | exec /opt/app/startup.sh: exec format error
papermerge_worker exited with code 1
papermerge_app exited with code 1

madmax2010 · 2. Oktober 2022

Legolas schrieb:
papermerge_app | exec /opt/app/startup.sh: exec format error

schaut ein wenig aus, alsb ob du deine umgebung kaputt gespielt hast. Oder du hast hasrt inkompatible hardware.
Versuchst du ein arm image auf x86 zu starten? Oder anders herum?
Welche shell nutzt du? ( ps -p $$)
welche docker und docker-compose version?

und sei doch bitte so gut und setz logs und code immer etwas ab. So wie du das machst ist es richtig scheiße zu lesen.

Code:

root@DietPi:/papermerge-proj/docker# docker-compose up
[+] Running 4/0
⠿ Container redis              Running                                                                                                                                                                      0.0s
⠿ Container papermerge_worker  Created                                                                                                                                                                      0.0s
⠿ Container postgres_db        Running                                                                                                                                                                      0.0s
⠿ Container papermerge_app     Created                                                                                                                                                                      0.0s
Attaching to papermerge_app, papermerge_worker, postgres_db, redis
papermerge_worker  | exec /opt/app/startup.sh: exec format error
papermerge_app     | exec /opt/app/startup.sh: exec format error
papermerge_worker exited with code 1
papermerge_app exited with code 1

root@DietPi:/papermerge-proj/docker# docker-compose up
[+] Running 4/0
⠿ Container papermerge_worker Created 0.0s
⠿ Container redis Created 0.0s
⠿ Container postgres_db Created 0.0s
⠿ Container papermerge_app Created 0.0s
Attaching to papermerge_app, papermerge_worker, postgres_db, redis
papermerge_worker | exec /opt/app/startup.sh: exec format error
redis | 1:C 02 Oct 2022 13:45:24.081 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis | 1:C 02 Oct 2022 13:45:24.082 # Redis version=6.2.7, bits=64, commit=00000000, modified=0, pid=1, just started
redis | 1:C 02 Oct 2022 13:45:24.082 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis | 1:M 02 Oct 2022 13:45:24.092 * monotonic clock: POSIX clock_gettime
redis | 1:M 02 Oct 2022 13:45:24.098 # A key '__redis__compare_helper' was added to Lua globals which is not on the globals allow list nor listed on the deny list.
redis | 1:M 02 Oct 2022 13:45:24.100 * Running mode=standalone, port=6379.
redis | 1:M 02 Oct 2022 13:45:24.101 # Server initialized
postgres_db |
postgres_db | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_db |
redis | 1:M 02 Oct 2022 13:45:24.116 * Loading RDB produced by version 6.2.7
redis | 1:M 02 Oct 2022 13:45:24.116 * RDB age 190 seconds
redis | 1:M 02 Oct 2022 13:45:24.116 * RDB memory usage when created 0.81 Mb
redis | 1:M 02 Oct 2022 13:45:24.116 # Done loading RDB, keys loaded: 0, keys expired: 0.
redis | 1:M 02 Oct 2022 13:45:24.116 * DB loaded from disk: 0.001 seconds
redis | 1:M 02 Oct 2022 13:45:24.116 * Ready to accept connections
papermerge_worker exited with code 1
postgres_db | 2022-10-02 13:45:24.628 UTC [1] LOG: starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
postgres_db | 2022-10-02 13:45:24.631 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_db | 2022-10-02 13:45:24.632 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_db | 2022-10-02 13:45:24.640 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_db | 2022-10-02 13:45:24.766 UTC [26] LOG: database system was shut down at 2022-10-02 13:42:14 UTC
postgres_db | 2022-10-02 13:45:24.806 UTC [1] LOG: database system is ready to accept connections
papermerge_app | exec /opt/app/startup.sh: exec format error
papermerge_app exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
[+] Running 4/4
⠿ Container papermerge_app Stopped 0.0s
⠿ Container papermerge_worker Stopped 0.0s
⠿ Container redis Stopped 0.9s
⠿ Container postgres_db Stopped 0.9s
canceled

Ergänzung (2. Oktober 2022)

das war wohl leider richtig:

madmax2010 schrieb:
schaut ein wenig aus, alsb ob du deine umgebung kaputt gespielt hast. Oder du hast hasrt inkompatible hardware.
Versuchst du ein arm image auf x86 zu starten? Oder anders herum?

Siehe:
https://github.com/ciur/papermerge/issues/295
hinten im thread verweist der maintainer auf die Manuelle installation. Die Images sind nicht ARM geeignet.

Legolas · 3. Oktober 2022

Ok,

dann versuch ich das ml mit anderer Hardware. Danke für die Mühe

SW

madmax2010 · 3. Oktober 2022

Oder die manuell Installation befohlen

Suche

Kriege Papermerge nicht zum laufen

Legolas

Lieutenant

madmax2010

Fleet Admiral

Legolas

Lieutenant

madmax2010

Fleet Admiral

M-X

Vice Admiral

Legolas

Lieutenant

madmax2010

Fleet Admiral

Legolas

Lieutenant

madmax2010

Fleet Admiral

Legolas

Lieutenant

madmax2010

Fleet Admiral

Legolas

Lieutenant

madmax2010

Fleet Admiral

Ähnliche Themen

Passend zum Thema

Internet of Things Telefónica erprobt 5G RedCap im eigenen Mobilfunknetz

Flipper Zero Zusatzmodul macht Hackertool zum vielfältigen Controller

HatDrive Update M.2-SSDs beim Raspberry Pi 5 nachrüsten