Has anyone ran into this issue and had to restart Xymon? This server is a new installation of FreeBSD and Xymon as of yesterday with only a few hosts being monitored.
OS: FreeBSD 9.0 Xymon: 4.3.10
/var/log/xymon/xymonlaunch.log 2012-09-13 08:48:53 Task xymond terminated by signal 6 2012-09-13 08:48:53 Task xymongen terminated by signal 15 2012-09-13 08:48:53 Loading hostnames 2012-09-13 08:48:53 Loading saved state 2012-09-13 08:48:53 Setting up network listener on 0.0.0.0:1984 2012-09-13 08:48:53 Cannot bind to listen socket (Address already in use) 2012-09-13 08:48:53 Task xymond terminated, status 1
/var/log/xymon/xymond.log 2012-09-13 08:49:08 Whoops ! Failed to send message (timeout) 2012-09-13 08:49:08 -> 2012-09-13 08:49:08 -> Recipient '10.110.2.5', timeout 15 2012-09-13 08:49:08 -> 1st line: 'status server1,dc,domain,net.xymond red - Program crashed'
** What I was doing when the crash occurred **
/usr/local/xymon/server/bin/xymon 127.0.0.1 "drop a.someserver.org"
/usr/local/xymon/server/bin/xymon 127.0.0.1 "drop b.someserver.org"
/usr/local/xymon/server/bin/xymon 127.0.0.1 "drop c.someserver.org"
<-- I hit enter because of the long pause/usr/local/xymon/server/bin/xymon 127.0.0.1 "drop d.someserver.org"
2012-09-13 08:49:17 Whoops ! Failed to send message (Connection failed) 2012-09-13 08:49:17 -> Could not connect to Xymon daemon at 127.0.0.1:1984 (Connection refused) 2012-09-13 08:49:17 -> Recipient '127.0.0.1', timeout 15 2012-09-13 08:49:17 -> 1st line: 'drop d.someserver.org'
Note: I'm running Xymon 4.2.3 on FreeBSD 8.0 with 2215 hosts and have never experienced a crash having to restart.
-Clint This e-mail (and any attachment) is strictly confidential and for use only by intended recipient(s). The opinions therein expressed are those of the author. Its contents, therefore, do not represent any commitment between the company and the recipient(s) and no liability or responsibility is accepted by the company for the above mentioned content. If you are not an intended recipient(s), please notify the author promptly and delete this message.