RE: monit (latest CVS checkout) crashes

[Nowak, Bernhard]

Hi,

here is the backtrace. I hope this helps.

Regards,
Bernhard


************************************
gdb /usr/local/bin/monit /core.3852
GNU gdb Red Hat Linux (6.1post-1.20040607.43rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...(no debugging symbols 
found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".

Core was generated by `/usr/local/bin/monit -c /etc/monitrc'.
Program terminated with signal 6, Aborted.
Reading symbols from /lib/tls/libpthread.so.0...(no debugging symbols 
found)...done.
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libssl.so.4...(no debugging symbols found)...done.
Loaded symbols for /lib/libssl.so.4
Reading symbols from /lib/libcrypto.so.4...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypto.so.4
Reading symbols from /lib/tls/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libgssapi_krb5.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libgssapi_krb5.so.2
Reading symbols from /usr/lib/libkrb5.so.3...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libkrb5.so.3
Reading symbols from /lib/libcom_err.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libcom_err.so.2
Reading symbols from /usr/lib/libk5crypto.so.3...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libk5crypto.so.3
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /lib/libnss_files.so.2
#0  0x0019e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0  0x0019e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x001de955 in raise () from /lib/tls/libc.so.6
#2  0x001e0319 in abort () from /lib/tls/libc.so.6
#3  0x00211f9a in __libc_message () from /lib/tls/libc.so.6
#4  0x00218528 in _int_free () from /lib/tls/libc.so.6
#5  0x00218afa in free () from /lib/tls/libc.so.6
#6  0x080616e2 in signal ()
#7  0x08058ca8 in signal ()
#8  0x08058ef1 in signal ()
#9  0x0805892b in signal ()
#10 0x080501fe in ?? ()
#11 0x00000000 in ?? ()
(gdb)   








-----Original Message-----
From: address@hidden
[mailto:address@hidden
]On Behalf Of Martin Pala
Sent: Tuesday, February 01, 2005 8:51 PM
To: This is the general mailing list for monit
Subject: Re: monit (latest CVS checkout) crashes


It could help, when you have core of crashed process (note that you can
use 'ulimit -c unlimited' command before actual test attempt to unset
possible core size limit). When you have core, you can use following
sequence to trace the stack:

1.) run gdb with monit binary and core as arguments:
   gdb /path/to/monit /path/to/core

2.) show backtrace - on gdb prompt:
(gdb) bt

... now you will see what preceeded the crash ... this output may help
us to fix the problem quickly.

(if you are running solaris, you can just use pstack command on core)

You can also can look on short debug howto in monit FAQ.txt. It
describes how to trace the system calls - these are useful informations
as well (solaris alternative is truss).

Thanks,
Martin


Nowak, Bernhard wrote:
> Hi all,
>
> I just compiled monit from CVS because I wanted to test the new URL and HTTP 
> content monitoring feature.
>
> I use monit to monitor two services (aaa and bbb) and restart them max two 
> times. If that happens I want to switch over to standby system (by stopping 
> heartbeat, monit was started before by heartbeat..I know, the manual tells me 
> to do it the other way around...but I want it that way).
> As long as the "Event ratio dependant action rules" are not yet supported I 
> will do a workaround monitoring the monit service pages for the words "not 
> monitored" (ccc_mont and ddd_monit).
>
>
> Unfortunately monit crashes.
>
> /etc/init.d/monit status gives me a "monit dead but pid file exists".
> Last line of monit.log is: monit HTTP server started"
>
> I also tried to use monit -c /etc/monit.conf -v. This one started monit (with 
> all the debug messages), but also crashed after some seconds.
>
> I attached my config as well.
>
> I'm no developer, just user.
>
> Thanks,
>
> Bernhard
>
> ***************************************************
>
> set daemon  30    
> set logfile /var/log/monit.log
> set mailserver localhost
> set mail-format        
>   { from: address@hidden
>  set alert address@hidden
> set httpd port 2812 and 
>      allow localhost     
>      allow 192.168.9.41
>      allow 192.168.10.171
>
> #------services to 
> watch-----------------------------------------------------------
>   check host aaa with address 127.0.0.1
>      start program = "/etc/init.d/ABC start"
>      stop program  = "/etc/init.d/ABC stop"
>      if failed port 20001 with timeout 60 seconds then restart
>      if 2 restarts within 20 cycles then timeout
>
>
>   check host bbb with address 192.168.10.173
>      start program = "/etc/init.d/DEF start"
>      stop program  = "/etc/init.d/DEF stop"
>      if failed host 192.168.10.173 port 8080 protocol http with timeout 60 
> seconds then restart
>      if 2 restarts within 20 cycles then timeout
>
> #-----use mont http content feature to check for "not monitored"  -------
>
>   check host ccc_monit with address 192.168.10.173
>   if failed url http://192.168.10.173:2812/aaa
>      and content != "not monitored" with timeout 60 seconds
>      then exec "/etc/init.d/heartbeat stop"
>
>
>   check host ddd_monit with address 192.168.10.173
>   if failed url http://192.168.10.173:2812/bbb
>      and content != "not monitored" with timeout 60 seconds
>      then exec "/etc/init.d/heartbeat stop"
>
> ***************************************************************************************************
> The information in this email is confidential and may be legally privileged.  
> Access to this email by anyone other than the intended addressee is 
> unauthorized.  If you are not the intended recipient of this message, any 
> review, disclosure, copying, distribution, retention, or any action taken or 
> omitted to be taken in reliance on it is prohibited and may be unlawful.  If 
> you are not the intended recipient, please reply to or forward a copy of this 
> message to the sender and delete the message, any attachments, and any copies 
> thereof from your system.
> ***************************************************************************************************
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general


--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general

***************************************************************************************************
The information in this email is confidential and may be legally privileged.  
Access to this email by anyone other than the intended addressee is 
unauthorized.  If you are not the intended recipient of this message, any 
review, disclosure, copying, distribution, retention, or any action taken or 
omitted to be taken in reliance on it is prohibited and may be unlawful.  If 
you are not the intended recipient, please reply to or forward a copy of this 
message to the sender and delete the message, any attachments, and any copies 
thereof from your system.
***************************************************************************************************