Docker image instalation error on Centos 8

Hi,
I get the following errors in peertube docker image setup. Setup does not complete.
Can you support?
indent preformatted text by 4 spaces
ttaching to peertube_redis_1, peertube_reverse-proxy_1, peertube_postgres_1, peertube_postfix_1, peertube_peertube_1
postgres_1 | The files belonging to this database system will be owned by user « postgres ».
postgres_1 | This user must also own the server process.
postgres_1 |
postgres_1 | The database cluster will be initialized with locale « en_US.utf8 ».
postgres_1 | The default database encoding has accordingly been set to « UTF8 ».
postgres_1 | The default text search configuration will be set to « english ».
postgres_1 |
postgres_1 | Data page checksums are disabled.
postgres_1 |
postgres_1 | fixing permissions on existing directory /var/lib/postgresql/data … ok
postgres_1 | creating subdirectories … ok
postgres_1 | selecting default max_connections … 100
postgres_1 | selecting default shared_buffers … 128MB
postgres_1 | selecting default timezone … UTC
postgres_1 | selecting dynamic shared memory implementation … posix
postgres_1 | creating configuration files … ok
postgres_1 | running bootstrap script … ok
postgres_1 | performing post-bootstrap initialization … sh: locale: not found
postgres_1 | 2020-07-03 09:09:12.098 UTC [30] WARNING: no usable system locales were found
postgres_1 | ok
redis_1 | 1:C 03 Jul 09:09:10.850 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 03 Jul 09:09:10.850 # Redis version=4.0.14, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 03 Jul 09:09:10.850 # 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 | 1:M 03 Jul 09:09:10.859 * Running mode=standalone, port=6379.
redis_1 | 1:M 03 Jul 09:09:10.859 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 03 Jul 09:09:10.859 # Server initialized
redis_1 | 1:M 03 Jul 09:09:10.859 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‹ vm.overcommit_memory = 1 › to /etc/sysctl.conf and then reboot or run the command ‹ sysctl vm.overcommit_memory=1 › for this to take effect.
redis_1 | 1:M 03 Jul 09:09:10.859 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‹ echo never > /sys/kernel/mm/transparent_hugepage/enabled › as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 03 Jul 09:09:10.859 * Ready to accept connections
postgres_1 | syncing data to disk … ok
postgres_1 |
postgres_1 | Success. You can now start the database server using:
postgres_1 |
postgres_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres_1 |
postgres_1 |
postgres_1 | WARNING: enabling « trust » authentication for local connections
postgres_1 | You can change this by editing pg_hba.conf or using the option -A, or
postgres_1 | --auth-local and --auth-host, the next time you run initdb.
postgres_1 | waiting for server to start…2020-07-03 09:09:12.938 UTC [35] LOG: listening on Unix socket « /var/run/postgresql/.s.PGSQL.5432 »
postgres_1 | 2020-07-03 09:09:12.975 UTC [36] LOG: database system was shut down at 2020-07-03 09:09:12 UTC
postgres_1 | 2020-07-03 09:09:12.982 UTC [35] LOG: database system is ready to accept connections
postgres_1 | done
postgres_1 | server started
postgres_1 | CREATE DATABASE
postgres_1 |
postgres_1 |
postgres_1 | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres_1 |
postgres_1 | waiting for server to shut down…2020-07-03 09:09:13.331 UTC [35] LOG: received fast shutdown request
postgres_1 | 2020-07-03 09:09:13.340 UTC [35] LOG: aborting any active transactions
postgres_1 | 2020-07-03 09:09:13.342 UTC [35] LOG: worker process: logical replication launcher (PID 42) exited with exit code 1
postgres_1 | 2020-07-03 09:09:13.342 UTC [37] LOG: shutting down
postgres_1 | 2020-07-03 09:09:13.383 UTC [35] LOG: database system is shut down
postgres_1 | done
postgres_1 | server stopped
postgres_1 |
postgres_1 | PostgreSQL init process complete; ready for start up.
postgres_1 |
postgres_1 | 2020-07-03 09:09:13.447 UTC [1] LOG: listening on IPv4 address « 0.0.0.0 », port 5432
postgres_1 | 2020-07-03 09:09:13.447 UTC [1] LOG: listening on IPv6 address « :: », port 5432
postgres_1 | 2020-07-03 09:09:13.457 UTC [1] LOG: listening on Unix socket « /var/run/postgresql/.s.PGSQL.5432 »
postgres_1 | 2020-07-03 09:09:13.495 UTC [46] LOG: database system was shut down at 2020-07-03 09:09:13 UTC
postgres_1 | 2020-07-03 09:09:13.505 UTC [1] LOG: database system is ready to accept connections
peertube_1 |
peertube_1 | > peertube@2.2.0 start /app
peertube_1 | > node dist/server
peertube_1 |
postfix_1 | Starting Postfix Mail Transport Agent: postfix.
postfix_1 | rsyslogd: [origin software=« rsyslogd » swVersion=« 8.1901.0 » x-pid=« 120 » x-info=« https://www.rsyslog.com »] start
postfix_1 | postfix/master[119]: daemon started – version 3.4.10, configuration /etc/postfix
peertube_1 | [peertubeweb:443] 2020-07-03 09:09:19.740 error: Cannot start application. {
peertube_1 | « err »: {
peertube_1 | « stack »: « SequelizeConnectionRefusedError: connect ECONNREFUSED 172.18.0.5:5432\n at connection.connect.err (/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:170:24)\n at Connection.connectingErrorHandler (/app/node_modules/pg/lib/client.js:194:14)\n at Connection.emit (events.js:198:13)\n at Socket.reportStreamError (/app/node_modules/pg/lib/connection.js:73:10)\n at Socket.emit (events.js:198:13)\n at emitErrorNT (internal/streams/destroy.js:91:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)\n at process._tickCallback (internal/process/next_tick.js:63:19) »,
peertube_1 | « message »: « connect ECONNREFUSED 172.18.0.5:5432 »,
peertube_1 | « name »: « SequelizeConnectionRefusedError »,
peertube_1 | « parent »: {
peertube_1 | « stack »: « Error: connect ECONNREFUSED 172.18.0.5:5432\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14) »,
peertube_1 | « message »: « connect ECONNREFUSED 172.18.0.5:5432 »,
peertube_1 | « errno »: « ECONNREFUSED »,
peertube_1 | « code »: « ECONNREFUSED »,
peertube_1 | « syscall »: « connect »,
peertube_1 | « address »: « 172.18.0.5 »,
peertube_1 | « port »: 5432
peertube_1 | }
peertube_1 | }
peertube_1 | }
peertube_1 | npm ERR! code ELIFECYCLE
peertube_1 | npm ERR! errno 255
peertube_1 | npm ERR! peertube@2.2.0 start: node dist/server
peertube_1 | npm ERR! Exit status 255
peertube_1 | npm ERR!
peertube_1 | npm ERR! Failed at the peertube@2.2.0 start script.
peertube_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
peertube_1 |
peertube_1 | npm ERR! A complete log of this run can be found in:
peertube_1 | npm ERR! /home/peertube/.npm/_logs/2020-07-03T09_09_19_761Z-debug.log
reverse-proxy_1 | time=« 2020-07-03T09:09:21Z » level=error msg=« undefined backend ‹ backend-peertube-peertube › for frontend frontend-Host-peertubeweb-0. Skipping frontend frontend-Host-peertubeweb-0… »
peertube_1 |
peertube_1 | > peertube@2.2.0 start /app
peertube_1 | > node dist/server
peertube_1 |
peertube_1 | [peertubeweb:443] 2020-07-03 09:09:27.236 error: Cannot start application. {
peertube_1 | « err »: {
peertube_1 | « stack »: « SequelizeConnectionRefusedError: connect ECONNREFUSED 172.18.0.5:5432\n at connection.connect.err (/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:170:24)\n at Connection.connectingErrorHandler (/app/node_modules/pg/lib/client.js:194:14)\n at Connection.emit (events.js:198:13)\n at Socket.reportStreamError (/app/node_modules/pg/lib/connection.js:73:10)\n at Socket.emit (events.js:198:13)\n at emitErrorNT (internal/streams/destroy.js:91:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)\n at process._tickCallback (internal/process/next_tick.js:63:19) »,

Hello,

Look at this: https://github.com/Chocobozzz/PeerTube/issues/1369

Hi,

I get the error in the docker image. Is it possible to apply your proposed solution here?
Thanks

In your message, you get connect ECONNREFUSED 172.18.0.5:5432

In the comment in the Peertube’s git I shared the link to, there is a similar issue (except it talked about 127.0.0.1 instead of a public IP)

ldidry commented on 2 Nov 2018

5432 is PostgreSQL port. So PostgreSQL is not started, or login/password for the database are not good (or pg_hba.conf does not allow connections from 127.0.0.1, but I don’t think, it would be weird since it’s the default behavior of a newly installed PostgreSQL).

In the ldidry (@framasky) reply reproduced here above, it’s said that the 5432 port is related the PostgreSQL server. ldidry supposition is that this database server is not running, the database user’s password is invalid.

So, you may check those points. Plus, look if any firewall rule avoids using this port.

this subnet is determined by the docker. usernames and passwords are set in the ./env file. Firewall does not work.

@Chocobozzz, any advises to help Gokhan?

I read a lot of issues concerning the same problem but ever related to localhost usage. It seems here something else is culprit.