I think the key here is the "select". To me, this suggests that the
select() system call (which is used to read data on STDIN from xymonnet) is
trying to get data from a closed socket, or a similar problem. I wonder if
fping, which is run from xymonnet, is sometimes taking so long to run, and
eventually xymonlaunch is killing xymonnet.
By default, xymonlaunch (in tasks.cfg) kills xymonnet after 5 minutes, but
xymonnetagain is killed off after only 1 minute. So if you have a lot of
hosts that are uncontactable, or have long ping times, then this might add
up to a minute.
To confirm this, check out the "xymonnet" dot on your Xymon server, and
look at the "TIME SPENT" table for ping test duration.
J
On 10 January 2013 17:12, Vernon Everett <user-b3f8dacb72c8@xymon.invalid> wrote:
Hi all
Anybody seen something like this?
Execution of '/usr/local/sbin/fping -Ae' failed with error-code 4
/usr/local/sbin/fping: select : Invalid argument
Error I see when xymonnet page goes red.
At the same time, all conn tests go white.
Happens briefly every few hours. No obvious pattern, but at least once a
day, sometimes twice.
This is a new installation of Xymon 4.3.10, on a relatively old Solaris 10
Sparc server.
Regards
Vernon
--
"Accept the challenges so that you can feel the exhilaration of victory"
- General George Patton