gosa-si-server-crash-monitor does not seem to work

mbenkmann / limux-gosa

GOsa² is a web based adminstration tool for user accounts, groups, servers, clients, and many other things.

18 stars 5 forks source link

gosa-si-server-crash-monitor does not seem to work #162

Closed mbenkmann closed 9 years ago

mbenkmann commented 9 years ago

From mux2...@gmail.com on November 14, 2013 14:42:29

I sent a "panic" to go-susi but got no backtrace in gosa-si-server-crash.log. On another server go-susi crashed but there was also no crash.log. It seems that crash logging doesn't work anymore. Check this.

Original issue: http://code.google.com/p/go-susi/issues/detail?id=162

mbenkmann commented 9 years ago

From mux2...@gmail.com on November 03, 2014 22:50:53

I tested both SIGKILL and panic and got the expected output in the crash log. I have 2 possible explanations for crashes that do not create a crash log:

The OOM killer strikes and kills the gosa-si-server-crash-monitor process together with the gosa-si-server process
The crash was caused by or related to "disk full" on /var/log.

In any case, there is no reproducible problem => Closing

Status: Invalid