Re: [monit] monit fails mysteriously on refresh after upgrade from Debian etch to lenny

[Jenny Hopkins]

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

Indeed:

ldd /usr/sbin/monit
        linux-gate.so.1 =>  (0xffffe000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x40026000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x4003e000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x40070000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x40083000)
        libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0x4009b000)
        libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0x400e1000)
        libc.so.6 => /lib/libc.so.6 (0x40234000)
        /lib/ld-linux.so.2 (0x40000000)
        libdl.so.2 => /lib/libdl.so.2 (0x40372000)
        libz.so.1 => /usr/lib/libz.so.1 (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:
>
>  bt
>
>

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?

Jenny