search

truecharts / public

Community Helm Chart Repository
https://truecharts.org
GNU Affero General Public License v3.0
1.14k stars 617 forks source link

paperless-ng stuck in deploying state #7072

Closed satellite-no closed 1 year ago

satellite-no commented 1 year ago

App Name

paperless-ng

SCALE Version

22.12.0

App Version

1.12.2_7.0.28

Application Events

2023-02-06 16:08:46
Startup probe failed: dial tcp 172.16.0.49:8000: connect: connection refused
2023-02-06 16:08:33
Container image "tccr.io/truecharts/paperless-ng:1.12.2@sha256:0981b557e5ac3fcf286025c169161f613936f7dbba52582f90abcf5a107114de" already present on machine
2023-02-06 16:08:33
Created container paperless-ng
2023-02-06 16:08:33
Started container paperless-ng
2023-02-06 16:08:32
Add eth0 [172.16.0.49/16] from ix-net
2023-02-06 16:08:32
Container image "tccr.io/truecharts/ubuntu:jammy-20221101@sha256:4b9475e08c5180d4e7417dc6a18a26dcce7691e4311e5353dbb952645c5ff43f" already present on machine
2023-02-06 16:08:32
Created container db-wait
2023-02-06 16:08:32
Started container db-wait
2023-02-06 16:08:29
Scaled up replica set paperless-ng-7dd6b8b8d8 to 1
2023-02-06 16:08:29
Created pod: paperless-ng-7dd6b8b8d8-d8mvz
2023-02-06 16:08:29
Successfully assigned ix-paperless-ng/paperless-ng-7dd6b8b8d8-d8mvz to ix-truenas
2023-02-06 16:08:07
Job completed
2023-02-06 16:08:07
Scaled down replica set paperless-ng-7db546fc46 to 0 from 1
2023-02-06 16:08:07
Deleted pod: paperless-ng-7db546fc46-d97fn
2023-02-06 16:07:56
Started container paperless-ng-manifests
2023-02-06 16:07:55
Created container paperless-ng-manifests
2023-02-06 16:07:54
Add eth0 [172.16.0.48/16] from ix-net
2023-02-06 16:07:54
Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:6d6e0e50f28b961ed1c1c6a9c140553238641591fbdc9ac7c1a348636f78c552" already present on machine
2023-02-06 16:07:51
Created pod: paperless-ng-manifests-ncpjl
2023-02-06 16:07:51
Successfully assigned ix-paperless-ng/paperless-ng-manifests-ncpjl to ix-truenas
2023-02-06 15:57:47
Startup probe failed: dial tcp 172.16.0.47:8000: connect: connection refused
2023-02-06 15:57:35
Created container paperless-ng
2023-02-06 15:57:35
Started container paperless-ng
2023-02-06 15:57:33
Container image "tccr.io/truecharts/paperless-ng:1.12.2@sha256:0981b557e5ac3fcf286025c169161f613936f7dbba52582f90abcf5a107114de" already present on machine
2023-02-06 15:57:29
Created container db-wait
2023-02-06 15:57:29
Started container db-wait
2023-02-06 15:57:28
Add eth0 [172.16.0.47/16] from ix-net
2023-02-06 15:57:28
Container image "tccr.io/truecharts/ubuntu:jammy-20221101@sha256:4b9475e08c5180d4e7417dc6a18a26dcce7691e4311e5353dbb952645c5ff43f" already present on machine
2023-02-06 15:57:25
Scaled up replica set paperless-ng-7db546fc46 to 1
2023-02-06 15:57:25
Created pod: paperless-ng-7db546fc46-d97fn
2023-02-06 15:57:25
Successfully assigned ix-paperless-ng/paperless-ng-7db546fc46-d97fn to ix-truenas
2023-02-06 15:57:11
Job completed
2023-02-06 15:57:11
Scaled down replica set paperless-ng-86987856fc to 0 from 1
2023-02-06 15:57:11
Deleted pod: paperless-ng-86987856fc-r2t2f
2023-02-06 15:56:52
Started container paperless-ng-manifests
2023-02-06 15:56:51
Created container paperless-ng-manifests
2023-02-06 15:56:50
Add eth0 [172.16.0.46/16] from ix-net
2023-02-06 15:56:50
Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:6d6e0e50f28b961ed1c1c6a9c140553238641591fbdc9ac7c1a348636f78c552" already present on machine
2023-02-06 15:56:48
Created pod: paperless-ng-manifests-snnt6
2023-02-06 15:56:48
Successfully assigned ix-paperless-ng/paperless-ng-manifests-snnt6 to ix-truenas
2023-02-04 15:07:52
Startup probe failed: dial tcp 172.16.0.42:8000: connect: connection refused

Application Logs

paperless-ng-7dd6b8b8d8-d8mvz:

2023-02-06 23:13:52.664503+00:00Paperless-ngx docker container starting...
2023-02-06 23:13:52.673846+00:00Mapping UID and GID for paperless:paperless to 568:568

paperless-ng-postgresql-0:
```text
2023-02-04 22:07:16.675351+00:00postgresql 22:07:16.67 
2023-02-04 22:07:16.677008+00:00postgresql 22:07:16.67 Welcome to the Bitnami postgresql container
2023-02-04 22:07:16.678782+00:00postgresql 22:07:16.67 Subscribe to project updates by watching https://github.com/bitnami/containers
2023-02-04 22:07:16.680637+00:00postgresql 22:07:16.68 Submit issues and feature requests at https://github.com/bitnami/containers/issues
2023-02-04 22:07:16.682667+00:00postgresql 22:07:16.68 
2023-02-04 22:07:16.701445+00:00postgresql 22:07:16.70 INFO  ==> ** Starting PostgreSQL setup **
2023-02-04 22:07:16.732627+00:00postgresql 22:07:16.73 INFO  ==> Validating settings in POSTGRESQL_* env vars..
2023-02-04 22:07:16.740255+00:00postgresql 22:07:16.73 INFO  ==> Loading custom pre-init scripts...
2023-02-04 22:07:16.746665+00:00postgresql 22:07:16.74 INFO  ==> Initializing PostgreSQL database...
2023-02-04 22:07:16.766972+00:00postgresql 22:07:16.76 INFO  ==> pg_hba.conf file not detected. Generating it...
2023-02-04 22:07:16.769363+00:00postgresql 22:07:16.76 INFO  ==> Generating local authentication configuration
2023-02-04 22:07:19.658969+00:00postgresql 22:07:19.65 INFO  ==> Deploying PostgreSQL with persisted data...
2023-02-04 22:07:19.689720+00:00postgresql 22:07:19.68 INFO  ==> Configuring replication parameters
2023-02-04 22:07:19.732958+00:00postgresql 22:07:19.73 INFO  ==> Configuring fsync
2023-02-04 22:07:19.742341+00:00postgresql 22:07:19.74 INFO  ==> Configuring synchronous_replication
2023-02-04 22:07:19.765955+00:00postgresql 22:07:19.76 INFO  ==> Loading custom scripts...
2023-02-04 22:07:19.771586+00:00postgresql 22:07:19.77 INFO  ==> Enabling remote connections
2023-02-04 22:07:19.789103+00:00postgresql 22:07:19.78 INFO  ==> ** PostgreSQL setup finished! **
2023-02-04 22:07:19.789106+00:002023-02-04T22:07:19.789106022Z
2023-02-04 22:07:19.820930+00:00postgresql 22:07:19.82 INFO  ==> ** Starting PostgreSQL **
2023-02-04 22:07:19.886196+00:002023-02-04 22:07:19.885 GMT [1] LOG:  pgaudit extension initialized
2023-02-04 22:07:19.903859+00:002023-02-04 22:07:19.903 GMT [1] LOG:  starting PostgreSQL 14.6 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-02-04 22:07:19.904473+00:002023-02-04 22:07:19.904 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-02-04 22:07:19.904503+00:002023-02-04 22:07:19.904 GMT [1] LOG:  listening on IPv6 address "::", port 5432
2023-02-04 22:07:19.927234+00:002023-02-04 22:07:19.927 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2023-02-04 22:07:19.941761+00:002023-02-04 22:07:19.941 GMT [85] LOG:  database system was shut down at 2023-02-04 22:05:50 GMT
2023-02-04 22:07:19.970229+00:002023-02-04 22:07:19.969 GMT [1] LOG:  database system is ready to accept connections

paperless-ng-redis-0:

2023-02-04 22:07:20.482654+00:00redis 22:07:20.47 
2023-02-04 22:07:20.482717+00:00redis 22:07:20.48 Welcome to the Bitnami redis container
2023-02-04 22:07:20.482890+00:00redis 22:07:20.48 Subscribe to project updates by watching https://github.com/bitnami/containers
2023-02-04 22:07:20.485014+00:00redis 22:07:20.48 Submit issues and feature requests at https://github.com/bitnami/containers/issues
2023-02-04 22:07:20.486563+00:00redis 22:07:20.48 
2023-02-04 22:07:20.488464+00:00redis 22:07:20.48 INFO  ==> ** Starting Redis setup **
2023-02-04 22:07:20.509605+00:00redis 22:07:20.50 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
2023-02-04 22:07:20.526941+00:00redis 22:07:20.52 INFO  ==> Initializing Redis
2023-02-04 22:07:20.543797+00:00redis 22:07:20.54 INFO  ==> Setting Redis config file
2023-02-04 22:07:21.935274+00:00redis 22:07:21.93 INFO  ==> Configuring replication mode
2023-02-04 22:07:21.967105+00:00redis 22:07:21.96 INFO  ==> ** Redis setup finished! **
2023-02-04 22:07:21.967158+00:002023-02-04T22:07:21.967158065Z
2023-02-04 22:07:21.981668+00:00redis 22:07:21.98 INFO  ==> ** Starting Redis **
2023-02-04 22:07:21.998641+00:001:C 04 Feb 2023 22:07:21.998 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2023-02-04 22:07:21.998694+00:001:C 04 Feb 2023 22:07:21.998 # Redis version=7.0.8, bits=64, commit=00000000, modified=0, pid=1, just started
2023-02-04 22:07:21.998724+00:001:C 04 Feb 2023 22:07:21.998 # Configuration loaded
2023-02-04 22:07:21.999389+00:001:M 04 Feb 2023 22:07:21.999 * monotonic clock: POSIX clock_gettime
2023-02-04 22:07:22.000883+00:001:M 04 Feb 2023 22:07:22.000 * Running mode=standalone, port=6379.
2023-02-04 22:07:22.000916+00:001:M 04 Feb 2023 22:07:22.000 # Server initialized
2023-02-04 22:07:22.001911+00:001:M 04 Feb 2023 22:07:22.001 * Reading RDB base file on AOF loading...
2023-02-04 22:07:22.001994+00:001:M 04 Feb 2023 22:07:22.001 * Loading RDB produced by version 7.0.8
2023-02-04 22:07:22.002019+00:001:M 04 Feb 2023 22:07:22.001 * RDB age 3490 seconds
2023-02-04 22:07:22.002046+00:001:M 04 Feb 2023 22:07:22.001 * RDB memory usage when created 0.82 Mb
2023-02-04 22:07:22.002065+00:001:M 04 Feb 2023 22:07:22.001 * RDB is base AOF
2023-02-04 22:07:22.002078+00:001:M 04 Feb 2023 22:07:22.001 * Done loading RDB, keys loaded: 0, keys expired: 0.
2023-02-04 22:07:22.002104+00:001:M 04 Feb 2023 22:07:22.002 * DB loaded from base file appendonly.aof.1.base.rdb: 0.000 seconds
2023-02-04 22:07:22.002126+00:001:M 04 Feb 2023 22:07:22.002 * DB loaded from append only file: 0.000 seconds
2023-02-04 22:07:22.002142+00:001:M 04 Feb 2023 22:07:22.002 * Opening AOF incr file appendonly.aof.1.incr.aof on server start
2023-02-04 22:07:22.002161+00:001:M 04 Feb 2023 22:07:22.002 * Ready to accept connections

### Application Configuration

All settings default except required blank settings.

```text
PAPERLESS_ADMIN_USER = admin
PAPERLESS_ADMIN_PASSWORD = admin

Describe the bug

When trying to install paperless-ng the deployment just sits at the "Deploying 2/3" for ever.

To Reproduce

Follow procedure to install paperless-ng changing the required username and password.

Expected Behavior

Services startup as expected.

Screenshots

image

image

Additional Context

NA

I've read and agree with the following

PrivatePuffin commented 1 year ago

Actually READ the form when filing an issue. primarily the top section.

closed based on title.

satellite-no commented 1 year ago

Sort of rude saying "Actually READ the form when filing an issue." then closing out an otherwise ok issue just because its title incorrectly. Did not even link to relevant docs or anything.

This is a great project that offers a lot of great features and services but from what i've seen from interactions on issues many of the maintainers are quite rude. I would not expect this of an open project and especially one that is trying so hard for sponsors and monetary contributions.

satellite-no commented 1 year ago

What are you supposed to name it if you dont know the "actual bug".. the point of a bug report is to report an issue as seen from an end user, the community should diagnose the "actual bug" as many end users are not versed in finding these things out.

PrivatePuffin commented 1 year ago

Sort of rude saying "Actually READ the form when filing an issue." then closing out an otherwise ok issue just because its title incorrectly. Did not even link to relevant docs or anything.

In the future it will likely be autoclosed by a bot instead. But I could've been more polite and you could've actually read it. Two wrongs do not make a right, but it also doesn't make a valid bug report.

This is a great project that offers a lot of great features and services but from what i've seen from interactions on issues many of the maintainers are quite rude.

You're correct, I've seen more staff members being done with the usual "user fucks something and files a bugreport"-bugreports.

We should more clearly explain in the issue template, that all reports that are not proven to be code related, should be filed as a ticket with our support staff and not as a bug report.

I'll adapt it right away.

especially one that is trying so hard for sponsors and monetary contributions.

We're not trying very hard in my opinion,, it's only a fraction of my time as project-lead going into that. Nor do we ever hint at it in tickets or something.

There is one thing on the frontpage and it's in the App description, but that's it. That's mostly there because iX Systems doesn't allow a clean "donate" button like unraid does and I myself are not quite happy with those nags either.

Why is it there then? because we want to make clear, that people should not expect Open-Source projects to stay maintained if the bill ain't payed. Having enough donations is simply a make-or-break in the long(er) term, not a current goal we heavily push for.

Our current priority focusses are: our new common chart, certificate system, postgresql backend and Enterprise train. Definately not monetisation.

satellite-no commented 1 year ago

Thank you for the long response if not still passive aggressive. For your reference the below reddit demonstrates how TrueCharts is viewed in the community. I thought it was just me but I've worked with many OSS projects and this is a very negative experience.

modbreak We're okey with feedback, but github is not the place to links to campaign to disgrace projects. Regardless of which project it is.

PrivatePuffin commented 1 year ago

Thank you for the long response if not still passive aggressive. For your reference the below reddit demonstrates how TrueCharts is viewed in the community. I thought it was just me but I've worked with many OSS projects and this is a very negative experience.

There was not a cent of passive aggression intended in that response.

truecharts-admin commented 1 year ago

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists