Paperless-ngx Paperless-ngx – DMS via Docker auf dem NAS

alexhell · 01. Dez 2023

Hast du mal per CLI nachgeguckt, ob die Datenbank auch richtig angelegt wurde?
Und wenn du wirklich ein Update machen willst, dann müsstest du deine docker-compose.yml anpassen.

myssv · 01. Dez 2023

Sorry, als alter Maus-Schubser, zwar mit DOS aber ohne Linux-Kenntnisse, bin ich da raus. Keine Ahnung wie ...

alexhell · 01. Dez 2023

Code:

docker exec -it db psql 
\l #zeigt alle Datenbanken an, da müsstest du paperless sehen
\du+ #das zeigt alle vorhanden User an.
\c paperless # wechselt zur DB mit dem namen paperless
select * from auth_user; # Fragt die User bei Paperless ab. Da mit könntest du gucken, ob überhaupt Daten in der DB drin sind.

Vielleicht hilft dir das weiter. Wäre aber nicht verkehrt, wenn man sich minimal damit auskennt, was man da betreibt.

myssv · 01. Dez 2023

Das sind die letztenj Zeilen vom import:

ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
SET
SET
SET
SET
SET
set_config
------------

(1 row)

SET
SET
SET
SET
DROP DATABASE
CREATE DATABASE
ALTER DATABASE
You are now connected to database "postgres" as user "paperless".
SET
SET
SET
SET
SET
set_config
------------

(1 row)

SET
SET
SET
SET
COMMENT

Also gibt es den User paperless

Bei Deinem Befehl bekomme ich folgende Meldung

paperless@paperless:~$ docker exec -it db psql
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist
paperless@paperless:~$

alexhell · 01. Dez 2023

myssv schrieb:
Bei Deinem Befehl bekomme ich folgende Meldung

Dann Ergänze es mit -U paperless

You are now connected to database "postgres" as user "paperless".

Database postgres, aber nicht paperless. Oder kam das irgendwo vorher?

myssv · 01. Dez 2023

So ging es jetzt:

paperless@paperless:~$ docker exec -it db psql -U paperless
psql (16.1 (Debian 16.1-1.pgdg120+1))
Type "help" for help.

paperless=# \l
List of databases
Name | Owner | Encoding | Locale Provider | Collate | Ctype | ICU Locale | ICU Rules | Access privileges
-----------+-----------+----------+-----------------+------------+------------+------------+-----------+-------------------------
paperless | paperless | UTF8 | libc | en_US.utf8 | en_US.utf8 | | |
postgres | paperless | UTF8 | libc | en_US.utf8 | en_US.utf8 | | |
template0 | paperless | UTF8 | libc | en_US.utf8 | en_US.utf8 | | | =c/paperless +
| | | | | | | | paperless=CTc/paperless
template1 | paperless | UTF8 | libc | en_US.utf8 | en_US.utf8 | | | paperless=CTc/paperless+
| | | | | | | | =c/paperless
(4 rows)

paperless=# \du+
List of roles
Role name | Attributes | Description
-----------+------------------------------------------------------------+-------------
paperless | Superuser, Create role, Create DB, Replication, Bypass RLS |

paperless=# \c paperless
You are now connected to database "paperless" as user "paperless".
paperless=# select * from auth_user
paperless-#

alexhell · 01. Dez 2023

Beim letzten Befehl hast du das ; am Ende vergessen.

myssv · 01. Dez 2023

ups ...

alexhell · 01. Dez 2023

Also ist die DB richtig da....
Mal probiert die Container neu zumachen? Oder mal in die DB Logs geguckt?

myssv · 01. Dez 2023

paperless@paperless:~$ docker compose down
[+] Running 6/6
✔ Container webserver Removed 0.0s
✔ Container broker Removed 0.4s
✔ Container tika Removed 0.4s
✔ Container gotenberg Removed 10.3s
✔ Container db Removed 0.5s
✔ Network paperless_default Removed 0.3s
paperless@paperless:~$ docker compose pull
[+] Pulling 5/5
✔ broker Pulled 1.2s
✔ webserver Pulled 0.5s
✔ gotenberg Pulled 1.1s
✔ db Pulled 1.4s
✔ tika Pulled 0.5s
paperless@paperless:~$ docker compose up -d
[+] Running 6/6
✔ Network paperless_default Created 0.1s
✔ Container tika Started 0.2s
✔ Container gotenberg Started 0.1s
✔ Container db Started 0.1s
✔ Container broker Started 0.1s
✔ Container webserver Started 0.0s
paperless@paperless:~$

Im DB Log steht was:

PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-12-01 12:47:30.759 UTC [1] LOG: starting PostgreSQL 16.1 (Debian 16.1-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-12-01 12:47:30.759 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-12-01 12:47:30.759 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-12-01 12:47:30.766 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-12-01 12:47:30.779 UTC [28] LOG: database system was shut down at 2023-12-01 12:47:02 UTC
2023-12-01 12:47:30.788 UTC [1] LOG: database system is ready to accept connections
2023-12-01 12:47:40.935 UTC [33] FATAL: password authentication failed for user "paperless"
2023-12-01 12:47:40.935 UTC [33] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
2023-12-01 12:47:42.445 UTC [35] FATAL: password authentication failed for user "paperless"
2023-12-01 12:47:42.445 UTC [35] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
2023-12-01 12:47:43.854 UTC [37] FATAL: password authentication failed for user "paperless"
2023-12-01 12:47:43.854 UTC [37] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
2023-12-01 12:47:45.498 UTC [39] FATAL: password authentication failed for user "paperless"
2023-12-01 12:47:45.498 UTC [39] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
2023-12-01 12:47:47.527 UTC [41] FATAL: password authentication failed for user "paperless"
2023-12-01 12:47:47.527 UTC [41] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
2023-12-01 12:47:50.317 UTC [43] FATAL: password authentication failed for user "paperless"
2023-12-01 12:47:50.317 UTC [43] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
2023-12-01 12:47:54.696 UTC [46] FATAL: password authentication failed for user "paperless"
2023-12-01 12:47:54.696 UTC [46] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
2023-12-01 12:48:02.252 UTC [48] FATAL: password authentication failed for user "paperless"
2023-12-01 12:48:02.252 UTC [48] DETAIL: User "paperless" does not have a valid SCRAM secret.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"

alexhell · 01. Dez 2023

Dann guck mal hier: https://www.crunchydata.com/blog/how-to-upgrade-postgresql-passwords-to-scram

myssv · 01. Dez 2023

2023-12-01 12:58:10.611 UTC [1] LOG: database system is ready to accept connections

Es läuft, DANKE !!

alexhell · 01. Dez 2023

Sehr gut... Hast du denn jetzt ein Update gemacht? Weil in deiner letzten docker-compose.yml noch die 13er Version drin stand.

myssv · 01. Dez 2023

Falls noch jemand das gleiche Problem hat, hier die nötigen Schritte:

docker exec -it db psql -U paperless
\password
# 2x das Passwort eingeben
\q

myssv · 01. Dez 2023

Ja, das ist jetzt die aktuelle docker-compose.yml

version: "3.4"
services:
broker:
image: docker.io/library/redis:7
container_name: broker
restart: unless-stopped
volumes:
- /data/paperless/redis/_data:/data

db:
image: docker.io/library/postgres:16
container_name: db
restart: unless-stopped
volumes:
- /data/paperless/postgresql/_data:/var/lib/postgresql/data
environment:
POSTGRES_DB: paperless
POSTGRES_USER: paperless
POSTGRES_PASSWORD: paperless

webserver:
image: ghcr.io/paperless-ngx/paperless-ngx:latest
container_name: webserver
restart: unless-stopped
depends_on:
- db
- broker
- gotenberg
- tika
ports:
- 8001:8000
healthcheck:
test: ["CMD", "curl", "-fs", "-S", "--max-time", "2", "http://localhost:8000"]
interval: 30s
timeout: 10s
retries: 5
volumes:
- /data/paperless/consume:/usr/src/paperless/consume
- /data/paperless/data:/usr/src/paperless/data
- /data/paperless/media:/usr/src/paperless/media
- /data/paperless/export:/usr/src/paperless/export
environment:
PAPERLESS_ADMIN_USER: paperless
PAPERLESS_ADMIN_PASSWORD: paperless
PAPERLESS_REDIS: redis://broker:6379
PAPERLESS_DBHOST: db
PAPERLESS_TIKA_ENABLED: true
PAPERLESS_TIKA_GOTENBERG_ENDPOINT: http://gotenberg:3000
PAPERLESS_TIKA_ENDPOINT: http://tika:9998
PAPERLESS_OCR_LANGUAGE: deu
PAPERLESS_TIME_ZONE: Europe/Berlin
USERMAP_UID: 1001
USERMAP_GID: 1001

gotenberg:
image: docker.io/gotenberg/gotenberg:latest
container_name: gotenberg
restart: unless-stopped

alexhell · 01. Dez 2023

Gut, dann läuft ja alles wie gewollt

myssv · 01. Dez 2023

ja, nochmals vielen Dank für Deine Ruhe und Hilfe!!

alexhell · 01. Dez 2023

Sehr gerne. Dauert ab und zu ein bisschen, aber mit Geduld bekommt man die Probleme schon identifiziert

Tuxnet · 01. Dez 2023

Ich benötige mal bitte euer Schwamwissen.

Ich habe Paperless-NGX auf meiner Synology am laufen ( im Host Modus ). Erstellt damals über docker
Als Datenbank nutze ich meine Synology MariaDB ( Da wird alles gespeichert ) sowie das Redis Packet aus dem synocommunity.

Wie bekomme ich die Office Erweiterung (gotenberg & tinka) nachinstalliert ?
Ich bin am verzweifeln.

Und wo kann ich in Portainer in paperless-ngx folgendes Nachtragen ?

healthcheck:
test: ["CMD", "curl", "-fs", "-S", "--max-time", "2", "http://localhost:8000"]
interval: 30s
timeout: 10s
retries: 5

Dog6574 · 01. Dez 2023

Hallo. Ich habe auch auf 2.0.1 ein Update gemacht und würde mich nun an die Progress Datenbank wagen. Es wird jede Nacht ein Dump gezogen, der mittlerweile 8,4 MB groß ist. Ich habe ca. 1.000 Dokumente in meinem System. Gibt es eine Anleitung dafür?

Der Dump wird erstellt:

cd /volume1/docker/paperlessngx/export
find -mtime +30 -delete
/usr/local/bin/docker exec Paperless-NGX-DB pg_dump -U paperless -c paperless > /volume1/docker/paperlessngx/backup/backup.sql

Der Import sieht dann so aus??

sudo docker stop postgres
cd /volume1/docker/postgresql/
mv data/ data.old/
mkdir data
sudo docker start postgres
gunzip < /volume1/docker/postgresql/backups/backup.sql | sudo docker exec -i postgres psql -U postgres

Meine Compose sieht ja so aus:

version: "3.6"
services:
broker:
image: redis
container_name: Paperless-NGX-REDIS
restart: always
volumes:
- /volume1/docker/paperlessngx/redis:/data

db:
image: postgres:15.4
container_name: Paperless-NGX-DB
restart: always
volumes:
- /volume1/docker/paperlessngx/db:/var/lib/postgresql/data
environment:
POSTGRES_DB: paperless
POSTGRES_USER: paperless
POSTGRES_PASSWORD: paperless

webserver:
image: ghcr.io/paperless-ngx/paperless-ngx:latest
container_name: Paperless-NGX
restart: always
depends_on:
- db
- broker
ports:
- 8777:8000
volumes:
- /volume1/docker/paperlessngx/data:/usr/src/paperless/data
- /volume1/docker/paperlessngx/media:/usr/src/paperless/media
- /volume1/docker/paperlessngx/export:/usr/src/paperless/export
- /volume1/docker/paperlessngx/consume:/usr/src/paperless/consume
environment:
PAPERLESS_REDIS: redis://broker:6379
PAPERLESS_DBHOST: db
PAPERLESS_CONSUMER_ENABLE_BARCODES: true
USERMAP_UID: 1026
USERMAP_GID: 101
PAPERLESS_TIME_ZONE: Europe/Berlin
PAPERLESS_ADMIN_USER: XXX
PAPERLESS_ADMIN_PASSWORD: XXX-XX-XXXXX
PAPERLESS_OCR_LANGUAGE: deu+eng
PAPERLESS_CONSUMER_INOTIFY_DELAY: 5
PAPERLESS_URL: https://xxx

Ist das so richtig?

Gruß,