Check your "Ghost Clients" report to see if the hostnames in hosts.cfg
match the hostnames in the status messages.
The xymond status page indicates that you've received no enable or disable
messages - possibly because they've been rejected by xymond, which I would
expect to see in a log somewhere, such as xymond.log.
The enable/disable page is a CGI script. If it's having permissions
problems or some other issue, you might see something show up in the Apache
logs.
As I understand it, the enable/disable CGI binary gets its host list by
loading in the hosts.cfg and any included files. The CGI binary runs as the
Apache user. So the Apache user needs to have read permission on the
hosts.cfg file and any included files and their containing directories. So
check the permissions of any host files and ensure that the Apache user can
read them. If this is the problem, I would expect a log message in the
Apache log file indicating a permissions problem.
J
On Wed, 28 Apr 2021 at 16:29, Mike Hatami <user-c72b84f53a40@xymon.invalid>
wrote:
Hi Jeremy,
Thanks for the reply.
I installed a fresh Xymon on a CentOs as per the following:
- CentOS Stream 8 Server
- Xymon 4.3.30-1.el8.terabithia
- Enable/Disable page only sees the Xymon Server not any other hosts.
I have something about 100 or more hosts and about 50 of them have
client/agent installed and they report
- Another problem is that though clientlog is received and are green
for the hosts only the xymon server has CPU/disk/procs/etc columns not
other hosts
I checked all the httpd and xymon log as far as I could but cannot find
anything. Xymond status page:
*Wed Apr 28 16:21:42 2021 - xymon daemon up: 0 days, 01:24:59*
Statistics for Xymon daemon
Version: 4.3.30-1.el8.terabithia
Up since 28-Apr-2021 14:56:43 (0 days, 01:24:59)
Incoming messages : 122954
- status : 118924
- combodata : 0
- combo : 0
- extcombo : 1668
- page : 0
- summary : 0
- clientsubmit : 0
- clientconfig : 0
- data : 1148
- clientlog : 1
- client : 849
- notes : 0
- enable : 0
- disable : 0
- modify : 0
- ack : 0
- config : 128
- query : 0
- xymondboard : 98
- xymondlog : 22
- hostinfo : 22
- drop : 0
- rename : 0
- dummy : 82
- ping : 0
- notify : 0
- schedule : 12
- download : 0
- Timeouts : 0
- Bogus/Unknown : 0
Incoming messages/sec : 25 (average last 300 seconds)
status channel messages: 118945 (1 readers)
stachg channel messages: 1680 (1 readers)
page channel messages: 713 (1 readers)
data channel messages: 1148 (1 readers)
notes channel messages: 0 (0 readers)
enadis channel messages: 0 (0 readers)
client channel messages: 848 (1 readers)
clichg channel messages: 9 (1 readers)
user channel messages: 0 (0 readers)
backfeed messages : 0
M
*From:* Jeremy Laidman <user-0608abae5e7c@xymon.invalid>
*Sent:* Wednesday, 28 April 2021 4:15 PM
*To:* Mike Hatami <user-c72b84f53a40@xymon.invalid>
*Cc:* xymon at xymon.com
*Subject:* Re: [Xymon] findhost + enadis not working after in-place
upgrade
Alert: This message originated outside of NGS' network. *BE CAUTIOUS* before
clicking any link or attachment!
On Wed, 28 Apr 2021 at 15:42, Mike Hatami via Xymon <xymon at xymon.com>
wrote:
Any answer for this one?
You're not giving us much to go on. Was this an upgrade to the OS or to
Xymon? From what version to what version? What investigation have you
carried out already? Have you checked for errors in the logs or in the
"xymond" status page for the server?
J