4.3.18 install issues. /home/xymon permissions, missing FollowSymLinks
FYI, I installed xymon-4.3.18 from scratch last week, and ran into a couple of problems. The system I installed on is running RedHat Enterprise Linux v5.11, and I used almost all default answers in the Configure setup (changed location of man pages to /usr/local/share/man from /usr/local/man, if I recall.)
First was that I installed xymon into its own home directory (/home/xymon), and I needed to change directory permissions so the web server (running as login 'apache') could see any of the xymon directory. By default, home directories are set to mode 700 (user only.)
I added group read and execute permissions and added user 'apache' to the 'xymon' group, although I'm not sure if this exposes more than should be exposed. I also added user 'xymon' to the 'apache' group when I created the login.
Secondly, I needed to add "FollowSymLinks" to the cgi options sections in the apache config file for xymon before any of the scripts would work. Once that was in place, and Apache restarted, we seemed to have a working xymon install.
I'm assuming when doing a "./configure --server" I'm also configuring the client (as it's now running on the server.) Can I just grab a tarball of the /home/xymon/client directory and use it for client installations on the same architecture systems, or do I need to run a separate configure and build for "--client"?
-Andrew
On Fri, February 20, 2015 9:26 am, Andrew Rakowski wrote:
Secondly, I needed to add "FollowSymLinks" to the cgi options sections in the apache config file for xymon before any of the scripts would work. Once that was in place, and Apache restarted, we seemed to have a working xymon install.
Odd. FollowSymLinks should already be present in the config files for 4.3.18. Which stanza did you need to add it to?
I'm assuming when doing a "./configure --server" I'm also configuring the client (as it's now running on the server.) Can I just grab a tarball of the /home/xymon/client directory and use it for client installations on the same architecture systems, or do I need to run a separate configure and build for "--client"?
When making a tarball to copy onto other systems, it's better to do a ./configure --client since you'll end up pulling in slightly lighter binaries, however the ones produced by the server config should still work.
Regards, -jc
On Fri, 20 Feb 2015, J.C. Cleaver wrote (in part):
Secondly, I needed to add "FollowSymLinks" to the cgi options sections in the apache config file for xymon before any of the scripts would work. Once that was in place, and Apache restarted, we seemed to have a working xymon install.
Odd. FollowSymLinks should already be present in the config files for 4.3.18. Which stanza did you need to add it to?
My apologies on this false alarm / operator error / PEBKAC incident.
It was MY mistake - I appear to have copied the example xymon-apacheconf.txt file to /etc/httpd/conf.d/xymon-apache.conf file. I noticed it needed editing to use the right path, but thought that was an oversight in the config/make during build/install, and fixed it manually.
If I had actually *read* the install instructions, it says to link the /home/xymon/server/etc/xymon-apache.conf file into the apache conf.d directory, which would have worked fine, and DOES have the proper FollowSymLinks options in place, as well as correct paths for the install.
When making a tarball to copy onto other systems, it's better to do a ./configure --client since you'll end up pulling in slightly lighter binaries, however the ones produced by the server config should still work.
Thanks, I'll do new client builds on other systems for the appropriate OS releases and architectures.
I'm actually tempted to just use your Terabithia.org RPMs for the clients. It's nice to have a package install, as we're all used to doing an "rpm -qa | grep XXX" in the RedHat world to see if package XXX is installed.
-Andrew
ps: I blame Thursdays for the problem - I never could get the hang of Thursdays.
I use and recommend the Terebithia RPMs. Building from source doesn't buy you anything for the client, IMO.
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Senior Technologist || \\ and Health | novosirj at rutgers.edu<mailto:novosirj at rutgers.edu>- 973/972.0922 (2x0922) || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark `'
On Feb 20, 2015, at 16:44, Andrew Rakowski <landrew at pnnl.gov<mailto:landrew at pnnl.gov>> wrote:
On Fri, 20 Feb 2015, J.C. Cleaver wrote (in part):
Secondly, I needed to add "FollowSymLinks" to the cgi options sections in the apache config file for xymon before any of the scripts would work. Once that was in place, and Apache restarted, we seemed to have a working xymon install.
Odd. FollowSymLinks should already be present in the config files for 4.3.18. Which stanza did you need to add it to?
My apologies on this false alarm / operator error / PEBKAC incident.
It was MY mistake - I appear to have copied the example xymon-apacheconf.txt file to /etc/httpd/conf.d/xymon-apache.conf file. I noticed it needed editing to use the right path, but thought that was an oversight in the config/make during build/install, and fixed it manually.
If I had actually *read* the install instructions, it says to link the /home/xymon/server/etc/xymon-apache.conf file into the apache conf.d directory, which would have worked fine, and DOES have the proper FollowSymLinks options in place, as well as correct paths for the install.
When making a tarball to copy onto other systems, it's better to do a ./configure --client since you'll end up pulling in slightly lighter binaries, however the ones produced by the server config should still work.
Thanks, I'll do new client builds on other systems for the appropriate OS releases and architectures.
I'm actually tempted to just use your Terabithia.org<http://Terabithia.org> RPMs for the clients. It's nice to have a package install, as we're all used to doing an "rpm -qa | grep XXX" in the RedHat world to see if package XXX is installed.
-Andrew
ps: I blame Thursdays for the problem - I never could get the hang of Thursdays.
Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon
participants (3)
-
cleaver＠terabithia.org
-
landrew＠pnnl.gov
-
novosirj＠ca.rutgers.edu