<div dir="ltr">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.<br>
<br>2013-12-10 08:24:13 Setting up network listener on <a href="http://0.0.0.0:1984">0.0.0.0:1984</a><br><div class="gmail_extra"><br></div><div class="gmail_extra">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:</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Comment/remove: Order allow, deny </div><div class="gmail_extra"> Allow from all</div><div class="gmail_extra">Add: Require all granted</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 3:45 PM, Jeremy Laidman <span dir="ltr"><<a href="mailto:jlaidman@rebel-it.com.au" target="_blank">jlaidman@rebel-it.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im">On 10 December 2013 09:39, Doug Strick <span dir="ltr"><<a href="mailto:douglas.strick@gmail.com" target="_blank">douglas.strick@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>xymonlaunch.log</div><div><div><font face="courier new, monospace"></font></div></div></blockquote><div> </div></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><font face="courier new, monospace">2013-12-09 14:35:05 Cannot open directory /usr/local/xymon/server/etc/tasks.d</font><font face="courier new, monospace"></font></div></div></blockquote><div><br></div><div>Might want to create this directory, if only to silence this warning message. But this shouldn't stop Xymon from working.<br>
<br></div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">xymongen.log<div><div><font face="courier new, monospace">2013-12-09 14:35:10 xymond status-board not available, code 0</font></div>
<div><font face="courier new, monospace">2013-12-09 14:35:10 Failed to load current Xymon status, aborting page-update</font></div></div></blockquote><div><br></div></div><div>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:<br>
<br></div><div>$ /usr/local/xymon/server/bin/xymoncmd<br></div><div>$ echo $XYMSERVERS<br><br></div><div>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.<br>
</div><div class="im"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">xymonclient.log<div><div><font face="courier new, monospace">df: '/run/user/1005/gvfs': Permission denied</font></div>
<div><font face="courier new, monospace">df: '/run/user/1005/gvfs': Permission denied</font></div></div></blockquote><div><br></div></div><div>Not sure what's going on here, but probably not going to break anything major.<br>
<br></div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><font face="courier new, monospace">/usr/local/xymon/client/local/README: line 1: This: command not found</font></div>
<div><font face="courier new, monospace">install: target 'run' is not a directory</font></div><div><font face="courier new, monospace">/usr/local/xymon/client/local/README: line 3: all: command not found</font></div>
<div><font face="courier new, monospace">/usr/local/xymon/client/local/README: line 4: output: command not found</font></div></div></blockquote><div><br></div></div><div>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.<br>
<br></div><div>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.<span class="HOEnZb"><font color="#888888"><br>
<br></font></span></div><span class="HOEnZb"><font color="#888888"><div></div><div>J<br><br></div></font></span></div></div></div>
</blockquote></div><br></div></div>