deutrino's picture

Something killed postgres. In /var/log/postgresql

2021-05-14 09:44:49.532 UTC [585] LOG:  received fast shutdown request
2021-05-14 09:44:49.533 UTC [585] LOG:  aborting any active transactions
[various specific connections terminated]
2021-05-14 09:44:49.571 UTC [585] LOG:  background worker "logical replication launcher" (PID 614) exited with exit code 1
2021-05-14 09:44:49.574 UTC [609] LOG:  shutting down
2021-05-14 09:44:49.605 UTC [585] LOG:  database system is shut down

This is on two separate hosts, two separate providers in different countries. The events did not happen at the exact same time of day.

 

Forum: 
deutrino's picture

I'm pretty sure a recent unattended update to postgresql somehow eventually caused postgresql to exit and not be restarted. I rebooted both servers and they came back up and appear to be functioning normally now.

Jeremy Davis's picture

It looks like you are right. There was a recent security update to PostgreSQL (11.12-0+deb10u1) See Debian Security Announcement (DSA) 4915-1.

Although it should have restarted PostgreSQL cleanly. It appears that it was stopped (relatively) cleanly (I don't think that the "logical replication launcher" message is a problem). It just wasn't restarted?!

When I'm back at my desk, I'll launch one without installing the sec updates on firstboot and see how it goes.

Thanks for posting.

Add new comment