[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [monit] monit fails mysteriously on refresh after upgrade from Debia

From: Martin Pala
Subject: Re: [monit] monit fails mysteriously on refresh after upgrade from Debian etch to lenny
Date: Mon, 23 Feb 2009 22:16:42 +0100
User-agent: Thunderbird (X11/20090105)

Libraries look OK.

Debian package should be also fine if it comes from lenny - in fact even monit compiled on etch can work. You can try to remove monit package and reinstall from lenny repository.

Jenny Hopkins wrote:
2009/2/23 Martin Pala <address@hidden>:
Can you provide output of "ldd monit"?


ldd /usr/sbin/monit =>  (0xffffe000) => /lib/ (0x40026000) => /lib/ (0x4003e000) => /lib/ (0x40070000) => /lib/ (0x40083000) => /usr/lib/i686/cmov/ (0x4009b000) => /usr/lib/i686/cmov/ (0x400e1000) => /lib/ (0x40234000)
        /lib/ (0x40000000) => /lib/ (0x40372000) => /usr/lib/ (0x40376000)

Te problem could be caused by monit compiled with old etch's libraries ...
recompile on lenny will most probably fix the problem.

Does the debian package way not eliminate the need for compiling?

Also you can set the coredump:

 ulimit -c unlimited

and then diagnose using gsb:

 gdb monit core

and in gdb's prompt to get backtrace:


I didn't have any luck running this.  I got "No stack" so might have
been doing something wrong.

/etc/monit/core: No such file or directory.
(gdb) bt
No stack.

Thanks, any other hints?  How do the libraries look?


To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]