Piped
Piped copied to clipboard
signal 17 (SIGCHLD) received
Official Instance
- [ ] The bug is reproducible on the official hosted instance, or is API-related.
Describe the bug
i had a broken self host for awhile, i finally decided to just wipe it and start over from scratch. after ensuring all images and related files were gone i did the setup fresh once again and i still have the same problem. After docker-compose startup if you watch the logs everything starts fine but you cant load the site. after some time the following log lines will appear
nginx | 2023/08/24 21:53:06 [notice] 57#57: http file cache: /tmp/pipedapi_cache 0.000M, bsize: 4096
nginx | 2023/08/24 21:53:06 [notice] 1#1: signal 17 (SIGCHLD) received from 57
nginx | 2023/08/24 21:53:06 [notice] 1#1: cache loader process 57 exited with code 0
nginx | 2023/08/24 21:53:06 [notice] 1#1: signal 29 (SIGIO) received
i am not sure what to do about this, i have almost 10GB of free ram so it should not be a memory issue. and this was a full wipe and clean try but its the same issue i was having on the old install that used to work so im not sure what is causing this.
To Reproduce
follow the documentation for docker-compose with nginx reverse proxy docker-compose up -d problem
Expected behavior
site loads up and can be used
Logs/Errors
Attaching to nginx, piped-frontend, piped-backend, postgres, piped-proxy, watchtower
nginx | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
nginx | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
nginx | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
nginx | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
nginx | 10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
nginx | /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
nginx | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
nginx | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
nginx | /docker-entrypoint.sh: Configuration complete; ready for start up
nginx | 2023/08/24 21:52:06 [notice] 1#1: using the "epoll" event method
nginx | 2023/08/24 21:52:06 [notice] 1#1: nginx/1.25.2
nginx | 2023/08/24 21:52:06 [notice] 1#1: built by gcc 12.2.1 20220924 (Alpine 12.2.1_git20220924-r10)
nginx | 2023/08/24 21:52:06 [notice] 1#1: OS: Linux 6.4.0-3-amd64
nginx | 2023/08/24 21:52:06 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
nginx | 2023/08/24 21:52:06 [notice] 1#1: start worker processes
nginx | 2023/08/24 21:52:06 [notice] 1#1: start worker process 30
nginx | 2023/08/24 21:52:06 [notice] 1#1: start worker process 31
nginx | 2023/08/24 21:52:06 [notice] 1#1: start worker process 32
nginx | 2023/08/24 21:52:06 [notice] 1#1: start worker process 33
nginx | 2023/08/24 21:52:06 [notice] 1#1: start worker process 38
nginx | 2023/08/24 21:52:06 [notice] 1#1: start cache manager process 49
nginx | 2023/08/24 21:52:06 [notice] 1#1: start cache loader process 57
postgres | The files belonging to this database system will be owned by user "postgres".
postgres | This user must also own the server process.
postgres |
postgres | The database cluster will be initialized with locale "en_US.utf8".
postgres | The default database encoding has accordingly been set to "UTF8".
postgres | The default text search configuration will be set to "english".
postgres |
postgres | Data page checksums are disabled.
postgres |
postgres | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres | creating subdirectories ... ok
postgres | selecting dynamic shared memory implementation ... posix
postgres | selecting default max_connections ... 100
postgres | selecting default shared_buffers ... 128MB
postgres | selecting default time zone ... Etc/UTC
postgres | creating configuration files ... ok
postgres | running bootstrap script ... ok
postgres | performing post-bootstrap initialization ... ok
postgres | syncing data to disk ... ok
postgres |
postgres |
postgres | Success. You can now start the database server using:
postgres |
postgres | pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres |
postgres | initdb: warning: enabling "trust" authentication for local connections
postgres | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
postgres | waiting for server to start....2023-08-24 21:52:06.182 UTC [50] LOG: starting PostgreSQL 15.4 (Debian 15.4-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
postgres | 2023-08-24 21:52:06.183 UTC [50] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres | 2023-08-24 21:52:06.188 UTC [53] LOG: database system was shut down at 2023-08-24 21:52:05 UTC
postgres | 2023-08-24 21:52:06.200 UTC [50] LOG: database system is ready to accept connections
postgres | done
postgres | server started
postgres | CREATE DATABASE
postgres |
postgres |
postgres | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres |
postgres | waiting for server to shut down...2023-08-24 21:52:06.489 UTC [50] LOG: received fast shutdown request
postgres | .2023-08-24 21:52:06.490 UTC [50] LOG: aborting any active transactions
postgres | 2023-08-24 21:52:06.494 UTC [50] LOG: background worker "logical replication launcher" (PID 56) exited with exit code 1
postgres | 2023-08-24 21:52:06.500 UTC [51] LOG: shutting down
postgres | 2023-08-24 21:52:06.502 UTC [51] LOG: checkpoint starting: shutdown immediate
postgres | 2023-08-24 21:52:06.570 UTC [51] LOG: checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.038 s, sync=0.025 s, total=0.070 s; sync files=301, longest=0.003 s, average=0.001 s; distance=4223 kB, estimate=4223 kB
postgres | 2023-08-24 21:52:06.579 UTC [50] LOG: database system is shut down
postgres | done
postgres | server stopped
postgres |
postgres | PostgreSQL init process complete; ready for start up.
postgres |
postgres | 2023-08-24 21:52:06.646 UTC [1] LOG: starting PostgreSQL 15.4 (Debian 15.4-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
postgres | 2023-08-24 21:52:06.647 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres | 2023-08-24 21:52:06.647 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres | 2023-08-24 21:52:06.650 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres | 2023-08-24 21:52:06.659 UTC [66] LOG: database system was shut down at 2023-08-24 21:52:06 UTC
postgres | 2023-08-24 21:52:06.666 UTC [1] LOG: database system is ready to accept connections
postgres | 2023-08-24 21:52:08.224 UTC [70] ERROR: relation "public.databasechangeloglock" does not exist at character 22
postgres | 2023-08-24 21:52:08.224 UTC [70] STATEMENT: SELECT COUNT(*) FROM public.databasechangeloglock
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: using the "epoll" event method
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: nginx/1.25.2
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: built by gcc 12.2.1 20220924 (Alpine 12.2.1_git20220924-r10)
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: OS: Linux 6.4.0-3-amd64
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: start worker processes
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: start worker process 9
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: start worker process 10
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: start worker process 11
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: start worker process 12
piped-frontend | 2023/08/24 21:52:07 [notice] 1#1: start worker process 13
watchtower | time="2023-08-24T21:52:06Z" level=info msg="Watchtower 1.5.3"
watchtower | time="2023-08-24T21:52:06Z" level=info msg="Using no notifications"
watchtower | time="2023-08-24T21:52:06Z" level=info msg="Only checking containers which name matches "piped-frontend" or "piped-backend" or "piped-proxy" or "varnish" or "nginx" or "postgres" or "watchtower""
watchtower | time="2023-08-24T21:52:06Z" level=info msg="Scheduling first run: 2023-08-25 21:52:06 +0000 UTC"
watchtower | time="2023-08-24T21:52:06Z" level=info msg="Note that the first check will be performed in 23 hours, 59 minutes, 59 seconds"
piped-backend | Aug 24, 2023 9:52:07 PM liquibase.database
piped-backend | INFO: Set default schema name to public
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.changelog
piped-backend | INFO: Creating database history table with name: public.databasechangelog
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.changelog
piped-backend | INFO: Reading from public.databasechangelog
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.lockservice
piped-backend | INFO: Successfully acquired change log lock
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.command
piped-backend | INFO: Using deploymentId: 2913928314
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.changelog
piped-backend | INFO: Reading from public.databasechangelog
piped-backend | Running Changeset: changelog/version/0-init.xml::0-0::kavin
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.changelog
piped-backend | INFO: ChangeSet changelog/version/0-init.xml::0-0::kavin ran successfully in 4ms
piped-backend | Running Changeset: changelog/version/0-init.xml::0-1::kavin
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.executor
piped-backend | WARNING: index "users_id_idx" does not exist, skipping
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.changelog
piped-backend | INFO: SQL in file 0-1-init.sql executed
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.changelog
piped-backend | INFO: SQL in file 0-1-init-pg.sql executed
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.changelog
piped-backend | INFO: ChangeSet changelog/version/0-init.xml::0-1::kavin ran successfully in 191ms
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.util
piped-backend | INFO: UPDATE SUMMARY
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.util
piped-backend | INFO: Run: 2
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.util
piped-backend | INFO: Previously run: 0
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.util
piped-backend | INFO: Filtered out: 0
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.util
piped-backend | INFO: -------------------------------
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.util
piped-backend | INFO: Total change sets: 2
piped-backend |
piped-backend |
piped-backend | UPDATE SUMMARY
piped-backend | Run: 2
piped-backend | Previously run: 0
piped-backend | Filtered out: 0
piped-backend | -------------------------------
piped-backend | Total change sets: 2
piped-backend |
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.util
piped-backend | INFO: Update summary generated
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.command
piped-backend | INFO: Update command completed successfully.
piped-backend | Liquibase: Update has been successful. Rows affected: 2
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.lockservice
piped-backend | INFO: Successfully released change log lock
piped-backend | Aug 24, 2023 9:52:08 PM liquibase.command
piped-backend | INFO: Command execution complete
piped-backend | ThrottlingCache: 0 entries
piped-backend | SLF4J: No SLF4J providers were found.
piped-backend | SLF4J: Defaulting to no-operation (NOP) logger implementation
piped-backend | SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
piped-backend | Aug 24, 2023 9:52:08 PM org.hibernate.Version logVersion
piped-backend | INFO: HHH000412: Hibernate ORM core version [WORKING]
piped-backend | Aug 24, 2023 9:52:08 PM org.hibernate.cfg.Environment
Browser, and OS with Version.
several browsers tried, all on arch linux.
Additional context
No response
Having the exact same problem here too.