Hi Eric, which Linux distribution and version it is? Please can you send Monit coredump? If it was not created, then enable coredump and start monit again in debug mode:
1.) ulimit -c unlimited 2.) monit -vI > /tmp/monit.log 2>&1 When monit will crash, please send the /tmp/monit.log file and the coredump (may be stored in the working directory or for example in the /var/crash/core/ directory - depends on your system configuration) Regards, Martin On 04 Apr 2014, at 09:59, Eric Bonfadini <[email protected]> wrote: > > Hi all, > > Few days ago, I deployed Monit (version 5.8) across different server in my > farm. > I'm using precompiled binaries for linux x64 for the first time, previously I > always compiled the source code. > > Since the deploy, I noticed that the Monit daemon works fine for several > hours and then gets killed. > > While troubleshooting in syslog I found these entries: > - kernel: [66852867.858583] monit[13815] general protection ip:7f2ee03e7799 > sp:7fff7267c7e0 error:0 in libc-2.13.so[7f2ee036d000+17d000] > - kernel: [66743149.724234] monit[1337] general protection ip:7f1e8823b7f9 > sp:7fffbbe50540 error:0 in libc-2.11.2.so[7f1e881c5000+158000] > > Anyone else noticed this behaviour? > > Many thanks, > Eric > > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
