I just experienced a problem with 4.3, it appears that the xymond was hung and was not processing updates. I am currently running 4.3 in parallel with our production 4.2 Hobbit and noticed that some of the statuses weren't synched up between the two versions (I'm using xymonproxy to feed both instances the same data). I tried to run "xymon xxx 'xymondboard'" and it timed out trying to communicate with xymond. I then stopped Xymon, checked to make sure all the process were down, and noticed that xymond and xymonlaunch were still running. I killed them, then started Xymon and everything cleared up, the out of date statuses disappeared and everything looks to be in synch between my production and development instances. Has anybody else seen anything like this? If so, is there a fix for it. I would like to move Xymon to production, but this makes me a little nervous. I'm running both instances on RHEL4. Also, when I killed the hung processes I neglected to generate a core, if this happens again I'll be sure to create them.
Thanks, Larry Barber