You helped me figure out the problem. When I configured xymon initially I wasn't sure which IP on this test box to use so I decided to set it to 0.0.0.0 thinking it would bind to all addresses. Apparently that's not the case. Once I changed the IP for XYMONSERVERIP in /usr/local/xymon/server/etc/xymonserver.cfg. As soon as I made that change I'm able to get the xymon the xymon status page to come up. What's interesting is the xymonlaunch.log file still shows it's listening on 0.0.0.0 even though I modified the xymonserver.cfg.
2013-12-10 08:24:13 Setting up network listener on 0.0.0.0:1984
Also, I went back to verify the original apache issue by putting the out of box xymon-apache.conf in /etc/httpd/conf.d which still throws the 403 errors. Have to modify the Directory blocks like below:
Comment/remove: Order allow, deny Allow from all Add: Require all granted
On Mon, Dec 9, 2013 at 3:45 PM, Jeremy Laidman <jlaidman at rebel-it.com.au>wrote:
On 10 December 2013 09:39, Doug Strick <douglas.strick at gmail.com> wrote:
xymonlaunch.log
2013-12-09 14:35:05 Cannot open directory /usr/local/xymon/server/etc/tasks.d
Might want to create this directory, if only to silence this warning message. But this shouldn't stop Xymon from working.
xymongen.log 2013-12-09 14:35:10 xymond status-board not available, code 0 2013-12-09 14:35:10 Failed to load current Xymon status, aborting page-update
This is a warning sign. It indicates that the xymongen process that creates the web pages is unable to connect to the xymond daemon to find the status. This connection takes place over TCP port 1984. Can do do the following:
$ /usr/local/xymon/server/bin/xymoncmd $ echo $XYMSERVERS
This should show you how you have configured the Xymon server IP address in xymonserver.cfg. If it's not right, then different parts of Xymon won't be able to talk to the main xymond daemon.
xymonclient.log
df: '/run/user/1005/gvfs': Permission denied df: '/run/user/1005/gvfs': Permission denied
Not sure what's going on here, but probably not going to break anything major.
/usr/local/xymon/client/local/README: line 1: This: command not found
install: target 'run' is not a directory /usr/local/xymon/client/local/README: line 3: all: command not found /usr/local/xymon/client/local/README: line 4: output: command not found
Yeah, this is a problem. It's only an issue on the client side, so should not stop you seeing web pages. But it needs to be fixed up if you want to be able to monitor your Xymon server.
This appears to come from an attempt at executing a readme file. Have a look at the [xymonclient] section of /usr/local/xymon/server/etc/tasks.cfg, and confirm that the "CMD" parameter is /usr/local/xymon/client/bin/xymonclient.sh. If not, adjust this value. If it is, then check the xymonclient.sh script contents to see what the heck it's doing. Perhaps run it manually (under xymoncmd) and see if you get the same output.
J
You helped me figure out the problem. When I configured xymon initially I wasn't sure which IP on this test box to use so I decided to set it to 0.0.0.0 thinking it would bind to all addresses. Apparently that's not the case. Once I changed the IP for XYMONSERVERIP in /usr/local/xymon/server/etc/xymonserver.cfg. As soon as I made that change I'm able to get the xymon the xymon status page to come up. What's interesting is the xymonlaunch.log file still shows it's listening on 0.0.0.0 even though I modified the xymonserver.cfg.
2013-12-10 08:24:13 Setting up network listener on 0.0.0.0:1984
Also, I went back to verify the original apache issue by putting the out of box xymon-apache.conf in /etc/httpd/conf.d which still throws the 403 errors. Have to modify the Directory blocks like below:
Comment/remove: Order allow, deny Allow from all Add: Require all granted
On Mon, Dec 9, 2013 at 3:45 PM, Jeremy Laidman <jlaidman at rebel-it.com.au>wrote:
On 10 December 2013 09:39, Doug Strick <douglas.strick at gmail.com> wrote:
xymonlaunch.log
2013-12-09 14:35:05 Cannot open directory /usr/local/xymon/server/etc/tasks.d
Might want to create this directory, if only to silence this warning message. But this shouldn't stop Xymon from working.
xymongen.log 2013-12-09 14:35:10 xymond status-board not available, code 0 2013-12-09 14:35:10 Failed to load current Xymon status, aborting page-update
This is a warning sign. It indicates that the xymongen process that creates the web pages is unable to connect to the xymond daemon to find the status. This connection takes place over TCP port 1984. Can do do the following:
$ /usr/local/xymon/server/bin/xymoncmd $ echo $XYMSERVERS
This should show you how you have configured the Xymon server IP address in xymonserver.cfg. If it's not right, then different parts of Xymon won't be able to talk to the main xymond daemon.
xymonclient.log
df: '/run/user/1005/gvfs': Permission denied df: '/run/user/1005/gvfs': Permission denied
Not sure what's going on here, but probably not going to break anything major.
/usr/local/xymon/client/local/README: line 1: This: command not found
install: target 'run' is not a directory /usr/local/xymon/client/local/README: line 3: all: command not found /usr/local/xymon/client/local/README: line 4: output: command not found
Yeah, this is a problem. It's only an issue on the client side, so should not stop you seeing web pages. But it needs to be fixed up if you want to be able to monitor your Xymon server.
This appears to come from an attempt at executing a readme file. Have a look at the [xymonclient] section of /usr/local/xymon/server/etc/tasks.cfg, and confirm that the "CMD" parameter is /usr/local/xymon/client/bin/xymonclient.sh. If not, adjust this value. If it is, then check the xymonclient.sh script contents to see what the heck it's doing. Perhaps run it manually (under xymoncmd) and see if you get the same output.
Looks like I stand corrected. :-)
On 11 December 2013 03:34, Doug Strick <douglas.strick at gmail.com> wrote:
You helped me figure out the problem. When I configured xymon initially I wasn't sure which IP on this test box to use so I decided to set it to 0.0.0.0 thinking it would bind to all addresses. Apparently that's not the case. Once I changed the IP for XYMONSERVERIP in /usr/local/xymon/server/etc/xymonserver.cfg. As soon as I made that change I'm able to get the xymon the xymon status page to come up. What's interesting is the xymonlaunch.log file still shows it's listening on 0.0.0.0 even though I modified the xymonserver.cfg.
The XYMONSERVERIP is not the bind IP address, but the inter-communications IP address. That is, what the modules within Xymon use to talk to the xymond daemon. In most cases you can use 127.0.0.1 for this, which is probably the default.
Cheers Jeremy
participants (3)
-
douglas.strick＠gmail.com
-
jlaidman＠rebel-it.com.au
-
mburger＠bubbanfriends.org