On Wed, Dec 18, 2019 at 01:02:16PM +0000, Julian Gilbey wrote: > [...] > So indeed, this seems to be one of the issues - well identified! I'll > send a separate bug report about the other weirdness.
Dear Christoph, I've no idea about the other trouble I've had on one of the two machines (the same one as with the now-fixed ssl bug), and wonder whether you have any ideas. It now runs pg_upgradecluster without a problem, except that it finishes with: Ver Cluster Port Status Owner Data directory Log file 11 main 5432 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11-main.log Ver Cluster Port Status Owner Data directory Log file 12 main 5433 down postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log Both of the clusters are down, and a 'ps aux | grep postgres' confirms that no instance of postgresql is running. Running 'invoke-rc.d postgresql start' does not help: it still does not bring up the postgresql server. I can bring it up with 'pg_ctlcluster 12 main start' and then take it down with 'invoke-rc.d postgresql stop', but then 'invoke-rc.d postgresql start' doesn't bring it back again. More curiously, 'systemctl status [email protected]' reports: ● [email protected] - PostgreSQL Cluster 12-main Loaded: loaded (/lib/systemd/system/[email protected]; disabled; vendor preset: enabled) Active: inactive (dead) whereas on my other machine where things are working smoothly, after stopping it (with 'invoke-rc.d postgresql stop'), it reports: ● [email protected] - PostgreSQL Cluster 12-main Loaded: loaded (/lib/systemd/system/[email protected]; enabled-runtime; vendor preset: enabled) Active: inactive (dead) since Wed 2019-12-18 13:51:55 GMT; 9s ago Process: 7245 ExecStart=/usr/bin/pg_ctlcluster --skip-systemctl-redirect 12-main start (code=exited, status=0/SUCCESS) Process: 14306 ExecStop=/usr/bin/pg_ctlcluster --skip-systemctl-redirect -m fast 12-main stop (code=exited, status=0/SUCCESS) Main PID: 7481 (code=exited, status=0/SUCCESS) The /lib/systemd/system/[email protected] files are identical on both machines. And 'systemctl enable [email protected]' doesn't do anything, though 'systemctl enable [email protected]' changes the status to enabled. But even with that, 'invoke-rc.d postgresql start' doesn't start it. So something is very fishy here. I reinstalled postgresql-12 on the funny machine (purge and reinstall), and also rebooted both machines (after a kernel upgrade), but that seems to have made no difference :-/ I'm very confused, and grateful for any ideas you may have. Best wishes, Julian
