|
From: | Martin Pala |
Subject: | Re: [monit] [Announce] monit 5.0 beta6 |
Date: | Sat, 27 Dec 2008 15:48:53 +0100 |
On Dec 27, 2008, at 12:52 AM, Nicola Tiling wrote:
it looks like filesystem problem ... i've tested mmonit-2.0_beta6 on FreeBSD-6.4-p1 - works fine: --8<-- address@hidden ~/cvs/mmonit/mmonit-2.0_beta6]# uname -a FreeBSD freebsd6-x64.localdomain 6.4-RELEASE-p1 FreeBSD 6.4-RELEASE-p1 #0: Sun Dec 21 05:44:45 UTC 2008 address@hidden:/usr/obj/usr/src/sys/GENERIC amd64 address@hidden ~/cvs/mmonit/mmonit-2.0_beta6]# ./bin/mmonit -id Start parsing the server xml file Starting Database reaper thread Log file '/root/cvs/mmonit/mmonit-2.0_beta6/logs/error.log' opened Log file '/root/cvs/mmonit/mmonit-2.0_beta6/logs/localhost_access.log' opened Log file '/root/cvs/mmonit/mmonit-2.0_beta6/logs/mmonit.log' opened End parsing the server xml file Setting Host 'localhost' as default Host Start parsing the standard deployment descriptor '/root/cvs/mmonit/mmonit-2.0_beta6/conf/web.xml' End parsing the deployment descriptor '/root/cvs/mmonit/mmonit-2.0_beta6/conf/web.xml' Engine started Host 'localhost' started Context '' for Host 'localhost' started Alert Manager transmit thread started Loader for Context '' started Start parsing the deployment descriptor '/root/cvs/mmonit/mmonit-2.0_beta6/docroot/WEB-INF/web.xml' End parsing the deployment descriptor '/root/cvs/mmonit/mmonit-2.0_beta6/docroot/WEB-INF/web.xml' SessionManager for Context '' started Context '/collector' for Host 'localhost' started Loader for Context '/collector' started Start parsing the deployment descriptor '/root/cvs/mmonit/mmonit-2.0_beta6/docroot/collector/WEB-INF/web.xml' End parsing the deployment descriptor '/root/cvs/mmonit/mmonit-2.0_beta6/docroot/collector/WEB-INF/web.xml' Service started Starting IPv4 Connector with scheme 'http' at *:8080 with 10 processor threads mmonit started Starting Reactor using kqueue (max concurrent connections = 3449) Alert Manager transmit thread started --8<-- I think it could be good to try fsck for the filesystem. We can also trace system calls using truss: 1.) if the proc filesystem is not mounted, mount it: mount -t procfs proc /proc 2.) truss mmonit start: truss -o mmonit_truss.out -f ./bin/mmonit -id Thanks, Martin |
[Prev in Thread] | Current Thread | [Next in Thread] |