/var/log/xymon/history.log or xymonlaunch.log might have something or, depending on your system, /var/log/messages or audit/... Basically, anywhere that's liable to have segfault information. ($XYMONTMP might also contain a core dump file that could be useful.)

If xymond_history crashed, it was auto-restarted by xymonlaunch pretty quickly, which is why it's still running now. To clear the purple alert (it was a one-time message), simply drop the status manually (xymon localhost "drop <hostname> xymond_history")

HTH,

-jc

On Friday after over 800 days of operation our xymon server is reporting purple status for xymond_history. It says program crashed fatal sig caught. Yet the process is running and nothing shows in the log as a problem. Any ideas where I should start looking?

Mark Jones

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon