search

CyberDem0n / bg_mon

Background worker for monitoring PostgreSQL
MIT License
66 stars 11 forks source link

Segmentation fault issue #19

Closed mfuhrmann closed 2 years ago

mfuhrmann commented 5 years ago

We have found that PostgreSQL has killed itself after a segmentation fault issued against the bg_mon extension: 

2018-11-09 07:54:18 UTC [22072]: [9499-1] user=,db= LOG:  worker process: bg_mon (PID 20867) was terminated by signal 11: Segmentation fault
2018-11-09 07:54:18 UTC [22072]: [9500-1] user=,db= DETAIL:  Failed process was running: WITH locked_processes AS (SELECT this.pid  [ ... ]
2018-11-09 07:54:18 UTC [22072]: [9501-1] user=,db= LOG:  terminating any other active server processes
2018-11-09 07:54:18 UTC [20875]: [1-1] user=postgres,db=[unknown] WARNING:  terminating connection because of crash of another server process
2018-11-09 07:54:18 UTC [20875]: [2-1] user=postgres,db=[unknown] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2018-11-09 07:54:18 UTC [20875]: [3-1] user=postgres,db=[unknown] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2018-11-09 07:54:19 UTC [3580]: [1-1] user=postgres,db=postgres FATAL:  the database system is in recovery mode

Since we've disabled it, we never run into that issue again. We are using PostgreSQL v10.5 on Ubuntu 16.04 LTS.

Not sure why this happened or if this information is helpful. Let me know if I can provide other information.

CyberDem0n commented 5 years ago

Unfortunately without the core dump it is hard to tell what is wrong :(