Actions
Bug #24326
open
pg_ctlcluster 13 down on install on Debian 11
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
When I install rudder-server on Debian 11 I see some weird logs:
Success. You can now start the database server using:
pg_ctlcluster 13 main start
Ver Cluster Port Status Owner Data directory Log file
13 main 5432 down postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log
root@server:~# cat /var/log/postgresql/postgresql-13-main.log 2024-03-05 10:18:42.281 UTC [6635] LOG: starting PostgreSQL 13.14 (Debian 13.14-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 2024-03-05 10:18:42.281 UTC [6635] LOG: listening on IPv6 address "::1", port 5432 2024-03-05 10:18:42.281 UTC [6635] LOG: listening on IPv4 address "127.0.0.1", port 5432 2024-03-05 10:18:42.282 UTC [6635] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2024-03-05 10:18:42.284 UTC [6636] LOG: database system was shut down at 2024-03-05 10:18:41 UTC 2024-03-05 10:18:42.286 UTC [6635] LOG: database system is ready to accept connections 2024-03-05 10:19:07.711 UTC [6635] LOG: received SIGHUP, reloading configuration files 2024-03-05 10:20:01.447 UTC [13270] rudder@rudder LOG: could not receive data from client: Connection reset by peer 2024-03-05 10:20:01.447 UTC [13269] rudder@rudder LOG: could not receive data from client: Connection reset by peer 2024-03-05 10:20:01.447 UTC [13267] rudder@rudder LOG: could not receive data from client: Connection reset by peer 2024-03-05 10:20:01.451 UTC [13266] rudder@rudder LOG: could not receive data from client: Connection reset by peer 2024-03-05 10:20:01.452 UTC [13265] rudder@rudder LOG: could not receive data from client: Connection reset by peer
Files
Updated by
Actions