Only document I found which references core dumps is:
http://192.168.0.1/xymon/help/known-issues.html
Haven't found any debug options yet for the client issues :(
On Sat, Mar 28, 2009 at 4:41 PM, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid>wrote:
The core files would generally be somewhere in the Xymon home directory
structure. You might also want to look in the hobbit name pages to see how
to enable debug options on the various components.
Ralph Mitchell
On Sat, Mar 28, 2009 at 2:26 PM, J. Bobby Lopez <user-cf5303e672c8@xymon.invalid> wrote:
I was searching for something like that, but haven't found any. Where
would the core files reside?
On Sat, Mar 28, 2009 at 12:38 PM, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid
wrote:
That sounds like the client runs once, sends some info, then quits.
Thirty minutes later the display goes purple because no further reports
were received. Are there any core files??
Ralph Mitchell
On Sat, Mar 28, 2009 at 6:26 AM, J. Bobby Lopez <user-cf5303e672c8@xymon.invalid> wrote:
Having an odd problem that I'm not quite sure how to troubleshoot it.
I'm using Xymon 4.2.3 on Debian (kernel 2.4.27-2-386).
I have one client which was was installed as user 'xymon'
(configure/make/make install).
I run the client with 'runclient.sh start' and I see the services go
great on the web interface. All looks great.
After about 30 minutes however, the client seems to stop sending reports
to the server, and all services go purple.
Here's what I see when looking at the process listing on the client when
things are working correctly:
xymon at JBLDMZWEB01:~/client$ ps -ef | grep hobbit
xymon 25702 1 0 05:23 ? 00:00:00
/home/xymon/client/bin/hobbitlaunch
--config=/home/xymon/client/etc/clientlaunch.cfg
--log=/home/xymon/client/logs/clientlaunch.log
--pidfile=/home/xymon/client/logs/clientlaunch.JBLDMZWEB01.pid
xymon 25724 1 0 05:23 ? 00:00:00 sh -c vmstat 300 2
1>/home/xymon/client/tmp/hobbit_vmstat.JBLDMZWEB01.25707 2>&1; mv
/home/xymon/client/tmp/hobbit_vmstat.JBLDMZWEB01.25707
/home/xymon/client/tmp/hobbit_vmstat.JBLDMZWEB01
And then when the client stops reporting to the server, the process
listing looks like this:
xymon at JBLDMZWEB01:~/client$ ps -ef | grep hobbit
xymon 25702 1 0 05:23 ? 00:00:00
/home/xymon/client/bin/hobbitlaunch
--config=/home/xymon/client/etc/clientlaunch.cfg
--log=/home/xymon/client/logs/clientlaunch.log
--pidfile=/home/xymon/client/logs/clientlaunch.JBLDMZWEB01.pid
So other than the virtual memory stats missing from the process list, it
seems like it should still be sending reports.
I've checked the log files in 'logs/' and 'tmp/' but found nothing
useful.
This is a pretty fresh install of the Xymon server/client, so there
isn't really much that hsould be affecting it.
Should I be running the client as root? Does it provide more logs that
way?
Any thoughts?
--
J. Bobby Lopez
Web: http://jbldata.com/
Twitter: http://www.twitter.com/jbobbylopez
--
J. Bobby Lopez
Web: http://jbldata.com/
Twitter: http://www.twitter.com/jbobbylopez
--
J. Bobby Lopez
Web: http://jbldata.com/
Twitter: http://www.twitter.com/jbobbylopez