Hmm. This seems very strange. Are these hosts visible like normal in
generated status pages, and via query to xymond from the command line?
Based on your exclusions there, I believe the only test you wanted to
have present was the resulting 'sslcert'?
I just tested a descending directory structure and confirmed that
something like "directory /etc/xymon/hosts.d/" should read into
subdirectories properly.
Would you mind providing some xymond debug (-USR2) output during a
hostfile reload or startup? It should list each file as it's reading it in.
-jc
On 9/5/2019 4:56 AM, Rothlisberger, John R. wrote:
I added "--loadhostsfromxymond" to xymond_alert and that made no difference.
These are just directory includes in the hosts.cfg file.
FWIW, these clients can also NOT be found using the find host script from the browser - this is annoying for the time being but what if all of our hosts were with directory includes?
Thanks,
John
-----Original Message-----
From: Japheth Cleaver <user-87556346d4af@xymon.invalid>
Sent: Wednesday, September 4, 2019 2:58 PM
To: Rothlisberger, John R. <user-7adce57665bb@xymon.invalid>; xymon at xymon.com
Subject: [External] Re: Errors after upgrade to 4.3.29
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
Hi,
This warning (used to be just a debug message) was added in a few
versions ago (https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_xymon_code_7888_&d=DwID-g&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=u6KtIBCRNAeN-AbgJjdZe5zZJVFEfq04dnWD-hYNPL_fxJIIFncbL8W6k0NMJtuq&m=RK9M5u1KGPmJEBNLLre2D9-Esck80LjKSd4WB3cXoyk&s=ErUxIseIPx2kqKT4GWGENm-LlkHZcfx71WooCgTu3rI&e= ) to call out
when rules were presented for a host not visible yet. It could be a sign
that xymond is not following the 'include' files and thus not presenting
it to xymond_alert.
Are these regular directory includes or 'netinclude's?
Also, can you try adding the --loadhostsfromxymond option to your
xymond_alert CMD line and see if the warnings go away?
HTH,
-jc