Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
502 bad gateway after root password reset Question Question
Problem installing wordpress on subdomain (nginx / ubuntu) Question Question

Question

Postgres stopped running, is there a way I can get alerts if this happens?

Posted August 19, 2017 6.1k views
PostgreSQLMonitoringUbuntu 16.04

I recently realized my site was down, and after I checked the logs I noticed I couldn’t connect to postgres. Once I started postgres the site was back up.

Couple of questions:

  • What might cause postgres to stop?
  • What’s a way that I could get an alert if my site goes down?
Add a comment
rysilva
By:
rysilva

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
502 bad gateway after root password reset Question Question
Problem installing wordpress on subdomain (nginx / ubuntu) Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
Aprexer August 19, 2017

Then you would need to check postgres logs to find out why it crashes.

Reply Report
  • rysilva August 20, 2017

    Looks like it ran out of memory.

    2017-08-16 15:37:13 UTC [1614-2] LOG:  received fast shutdown request
2017-08-16 15:37:13 UTC [1614-3] LOG:  aborting any active transactions
2017-08-16 15:37:13 UTC [1640-2] LOG:  autovacuum launcher shutting down
2017-08-16 15:37:13 UTC [1637-1] LOG:  shutting down
2017-08-16 15:37:13 UTC [1637-2] LOG:  database system is shut down
2017-08-16 15:37:15 UTC [31373-1] FATAL:  could not map anonymous shared memory: Cannot allocate memory
2017-08-16 15:37:15 UTC [31373-2] HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 148488192 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
    Reply Report

Related

Looking for something else?

Ask a new question Search for more help