Upon review I found the issue. The xymond.log gave me a direction: xymond servername MACHINE='<hostname>' not listed in hosts.cfg, dropping xymond status.
In xymonserver.cfg I updated both XYMONSERVERHOSTNAME and XYMONSERVERWWWNAME but as it turned out I only had to update the XYMONSERVERWWWNAME.
The man page states the XYMONSERVERWWWNNAME is used to construct the url. And indeed that?s what I wanted to do.
According to the man page XYMONSERVERHOSTNAME should contain the FQDN, however, since that wasn?t used before the machine didn?t report on the FQDN but on the hostname. We only have the hostname in hosts.cfg so that would be the name to use in the xymonserver.cfg.
Met vriendelijke groet/With kind regards/Mit freundlichen Gr??en, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven
From: van Sleeuwen, Berry Sent: Thursday, 16 June 2022 14:55 To: xymon at xymon.com Subject: xymond xymongen xymonnet status purple after restart
Hi All,
Today I have restarted the Xymon service to activate an update in xymonserver.cfg. I have updated XYMONSERVERHOSTNAME and XYMONSERVERWWWNAME to reflect the actual FQDN hostname.
I restarted xymon with server/bin/xymon.sh. All monitored servers are still monitored, the trend data for them is appended. But I noticed no client data was reported for the Xymon machine itself, as it turned out the client wasn?t started. So I started the client as well.
All reporting is now correct, except for the status of xymond, xymongen and xymonnet. They remain purple, the trends graphic is not updated for them as well. It looks like these services are not started.
How can I get these services to be started?
Met vriendelijke groet/With kind regards/Mit freundlichen Gr??en, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven ? +31 (0)6 22564276 [cid:image001.png at 01D88198.90305B90] [cid:image002.png at 01D88198.90305B90]
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos? liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.