<div dir="ltr"><div><div>Hello,<br><br></div>I'm having a major issue with xymond crashing shortly after the service starts.<br><br></div><div>I'm using the the latest Terabithia RPM for RHEL 7 (4.3.24-3.el7.terabithia).<br><br></div><div>When
I check the status of the xymon service, it shows it as up but with
only the xymonlaunch parent process and vmstat processes. Upon
restarting the service, I see it start normally (all the normal channel
processes, etc.) and then after a while they all go away, leaving the
following process behind:<br><br> ├─2760 xymon-signal 0.0.0.0
status+1d/group:signal <server hostname>.xymond red (Check time of
report) - xymond program crashed Fatal signal caught!<br><br></div><div>along
with the xymonlaunch process and some vmstat processes. After a while
that process goes away. Sometimes a single xymond_rrd will show up
alongside the xymonlaunch and vmstat processes as well after a little
while.<br><br></div><div>I'm already running xymond in --debug mode.<br><br></div><div>This is what I see in the xymond log around the time of the crash:<br><br>2773 2016-01-30 11:02:32.515505 Status: Host=<host>, test=ntp<br>2773 2016-01-30 11:02:32.515507 -- create_hostlist_t for <host> (<client IP address>)<br>2773 2016-01-30 11:02:32.515513 Status: Host=<host>, test=conn<br>2773 2016-01-30 11:02:32.515520 Status: Host=<host>, test=raid<br>2773 2016-01-30 11:02:32.515529 Status: Host=<host>, test=memory<br>2773 2016-01-30 11:02:32.515534 Status: Host=<host>, test=files<br>2773 2016-01-30 11:02:32.515670 Status: Host=<host>, test=procs<br>2773 2016-01-30 11:02:32.515879 Status: Host=<host>, test=inode<br>2773 2016-01-30 11:02:32.515891 Status: Host=<host>, test=disk<br>2773 2016-01-30 11:02:32.516004 Status: Host=<host>, test=cpu<br>2773 2016-01-30 11:02:32.516605 Loaded 14419 status logs<br>2016-01-30 11:02:32 Setting up network listener on <a href="http://0.0.0.0:1984" target="_blank">0.0.0.0:1984</a><br>2016-01-30 11:02:32.516677 Cannot bind to listen socket (Address already in use)<br>2016-01-30 11:02:59.538906 Whoops ! Failed to send message (Timeout)<br>2016-01-30 11:02:59.539020 -><br>2016-01-30 11:02:59.539023 -> Recipient '<server IP address>', timeout 50<br>2016-01-30
11:02:59.539024 -> 1st line: 'status+1d/group:signal <server
hostname>.xymond red (Check time of report) - xymond program crashed'<br></div><div><br></div><div>It
seems to get finished with loading all the hosts and then it crashes
(the last host before it crashes is the last client I have
alphabetically).<br></div><div><br></div><div>I've tried stopping the
service, killing off any remaining xymon owned processes, and started
the service with the same results. I've also tried restarting the xymon
server machine itself, with the same crash happening when the service
starts the first time.<br><br></div><div>This just started happening out of the blue a couple of hours ago...<br></div><div><br></div><div>Looking
in netstat, there are no active connections using port 1984 on the
local side, just a bunch of clients trying to connect to the server with
1984 in the foreign address.<br></div><div><br></div><div>ANY help would be much appreciated as currently our Xymon server is not working!!<br><br></div>Thanks!!<br><br><div><div class="gmail_signature"><div>--</div><div>Matt Vander Werf</div></div></div>
</div>