[dev.icinga.com #882] trends.cgi segfaults #405
Comments
Updated by ricardo on 2010-10-13 21:25:15 +00:00 can you please provide the url you are requesting? Did you compile from source? |
Updated by mfriedrich on 2010-10-14 13:59:50 +00:00
selinux enabled? |
Updated by mfriedrich on 2010-11-05 17:31:06 +00:00
any feedback on this? w/o given url params it's rather hard to detect. even run them in gdb, like testing the cgis is described here: https://dev.icinga.org/projects/icinga-development/wiki/Icinga\_Core\_Tests#Classic-UI-CGIs |
Updated by ricardo on 2011-03-08 11:27:23 +00:00 any updates? will close otherwise. |
Updated by ricardo on 2011-03-08 11:29:26 +00:00
no feedback, no fix. |
Updated by mfriedrich on 2014-12-08 09:50:32 +00:00
|
Updated by mhanisch on 2015-12-04 09:50:53 +00:00 Hey Folks!! :) In our icinga environment (icinga 1.12.2) we ran into the same issue, that our trends.cgi throw many many segfaults when it was triggered by an external script. trends.cgi[6962]: segfault at 8 ip 00000000004042e9 sp 00007ffd7926fbe0 error 4 in trends.cgi[400000+49000 about 20-30 times per day. The solution! was, that we've triggered host- and servicenames, which doesn't exist anymore (we changed our name convention). So the trends.cgi segfaults, if you want to process a non existing host. That's maybe not the best behaviour, a clear exception would be cool :D Best regards from Berlin! Marcus |
Updated by ricardo on 2015-12-04 10:22:09 +00:00
Hi, so you call the trends.cgi from command line? Can you send me the QUERY_STRING you calling it with. This way there is a good chance to debug it. Thank you |
Updated by ricardo on 2016-06-23 22:32:50 +00:00
It's been over five years. Let's get this out. |
Updated by ricardo on 2016-07-18 21:06:09 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/882
Created by marcel on 2010-10-12 09:32:46 +00:00
Assignee: ricardo
Status: Resolved (closed on 2016-07-18 21:06:09 +00:00)
Target Version: 1.14
Last Update: 2016-07-18 21:06:09 +00:00 (in Redmine)
cat /var/log/messages | grep trends.cgi
Oct 11 19:24:59 HOSTNAME kernel: trends.cgi[5556]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff7d21ef70 error 4
Oct 11 19:25:09 HOSTNAME kernel: trends.cgi[5816]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fffe94d8e00 error 4
Oct 11 19:25:19 HOSTNAME kernel: trends.cgi[6112]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff92d5f920 error 4
Oct 11 19:25:29 HOSTNAME kernel: trends.cgi[6331]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff00f69140 error 4
Oct 11 19:25:39 HOSTNAME kernel: trends.cgi[6772]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff11830640 error 4
Oct 11 19:25:50 HOSTNAME kernel: trends.cgi[7191]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff3e19ee10 error 4
Oct 11 19:26:00 HOSTNAME kernel: trends.cgi[7379]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff713f0690 error 4
Oct 11 19:26:10 HOSTNAME kernel: trends.cgi[7576]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff246522e0 error 4
Oct 11 19:26:20 HOSTNAME kernel: trends.cgi[7906]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff38c0d9c0 error 4
Oct 11 19:26:30 HOSTNAME kernel: trends.cgi[8129]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fffb49aa190 error 4
Oct 11 19:26:40 HOSTNAME kernel: trends.cgi[8484]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff22b263b0 error 4
Oct 11 19:26:50 HOSTNAME kernel: trends.cgi[8903]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fffc2f32e80 error 4
Oct 11 19:27:01 HOSTNAME kernel: trends.cgi[9112]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff18d9a400 error 4
Oct 11 19:27:11 HOSTNAME kernel: trends.cgi[9355]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fffe156d190 error 4
Oct 11 19:27:21 HOSTNAME kernel: trends.cgi[9676]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff870a9420 error 4
Oct 11 19:27:31 HOSTNAME kernel: trends.cgi[9909]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff861bb9b0 error 4
Oct 11 19:27:41 HOSTNAME kernel: trends.cgi[10252]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fffd08069f0 error 4
Oct 11 19:27:51 HOSTNAME kernel: trends.cgi[10655]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff00d3a320 error 4
Oct 11 19:28:01 HOSTNAME kernel: trends.cgi[10843]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fffd81d0900 error 4
Oct 11 19:28:12 HOSTNAME kernel: trends.cgi[11042]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff169bc210 error 4
Oct 11 19:28:22 HOSTNAME kernel: trends.cgi[11365]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff9d8e3710 error 4
Oct 11 19:28:32 HOSTNAME kernel: trends.cgi[11587]: segfault at 0000000000000008 rip 0000000000406dbf rsp 00007fff009b55f0 error 4
updatedb && locate trends.cgi
/root/dl/icinga/icinga-1.2.0/cgi/trends.cgi
/usr/local/icinga/sbin/trends.cgi
ls -al /usr/local/icinga/sbin/trends.cgi
-rwxrwxr-x 1 zabbix zabbix 251960 Oct 6 12:32 /usr/local/icinga/sbin/trends.cgi
Linux HOSTNAME 2.6.18-194.11.4.el5 #1 SMP Tue Sep 21 05:04:09 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
CentOS 5.5
Icinga 1.2
No idea how to debug this.
Changesets
2016-02-02 21:55:21 +00:00 by ricardo dfc478a
The text was updated successfully, but these errors were encountered: