The problem turned out to be SELinux not allowing fping to write its output: type=AVC msg=audit(1581054673.192:3358): avc:? denied? { write } for? pid=14767 comm="fping" path="/var/lib/xymon/tmp/ping-stderr.14764.00" dev="dm-9" ino=288964 scontext=system_u:system_r:ping_t:s0 tcontext=system_u:object_r:init_tmp_t:s0 tclass=file permissive=1 The rule was set as dontaudit, and I had to rebuild the policy ignoring dontaudit flags to see the denials. Before I create a local rule using audit2allow, does anyone know if it's a known issue with a fix available (from terabithia or xymon)? Thanks! --Marcin
On 1/19/2020 7:10 PM, Marcin Struzak wrote:I installed xymon-4.3.28-1.fc20.x86_64 from terabithia.org, and all the hosts fail the conn test, e.g.,
Sun Jan 19 18:56:35 2020 conn NOT ok
Service conn on shark is not OK : Host does not respond to ping
Running "/usr/libexec/xymon/xymonnet --ping --no-update --debug <host>" from command line revealed an issue with folders:
<date & timestamp> Cannot create file /usr/share/xymon/tmp/ping-stdout.2138.00 : No such file or directory
<date & timestamp> Cannot create file /usr/share/xymon/tmp/ping-stderr.2138.00 : No such file or directory
<date & timestamp> xymonping child could not create outputfiles in /usr/share/xymon/tmp
<date & timestamp> Cannot open ping output file /usr/share/xymon/tmp/ping-stdout.2138.00
status+30 shark.conn clear <!-- [flags:OrdAstLe] --> Sun Jan 19 18:38:55 2020 conn ok : System failure of the ping test
Service conn on shark is OK
Xymon system error
&green
I created a symbolic link from /usr/share/xymon to /var/lib/xymon/tmp/, and now the command line succeeds:
status+30 shark.conn green <!-- [flags:OrdAstLe] --> Sun Jan 19 19:01:57 2020 conn ok
Service conn on shark is OK (up)
&green 10.10.10.1 is alive (0.07 ms)
but the Current Status (Main view) reports conn red.
Any help you can provide to debug this further will be appreciated!
--Marcin