Xymon Mailing List Archive search

Setting up xymon

list Michael Brown
Sun, 9 Feb 2014 09:25:28 -0500
Message-Id: <user-dfd00149ef0a@xymon.invalid>

Sorry this is taken me a while to get back. I have not been feeling well
with the dramatic temperature changes here of late.

The issues I had Jeremy assisted in solving and we did the following:

-Edited apache2.conf to change LogLevel "info" to "warn". This showed that
apache was not looking in /var/lib/xymon/www/ but at /var/www/html/xymon.
The /etc/apache2/conf.d/xymon was not being parsed.

-A conf file was found in /etc/apache2/conf-available/xymon.conf which was
a link to /etc/apache2/conf.d/xymon. A new symlink was created in
/etc/apache/conf-enabled that pointed to
/etc/apache2/conf-available/xymon.conf.

-Apache was restarted

-The permissions for the xymon pages were stating Permission denied so the
authen

-At this point, the error log started showing me the right errors.  But all
of the xymon pages were giving permission denied type errors. The "Order
allow, deny" and "Allow from all" were removed and only implemented one
line of "Require all granted"

-apache was restarted and errors were shown about the group file.

-The mod_authz_groupfile module was enabled by creating a symlink in
/etc/apache2/mods-enabled to the
/etc/apache2/mods-available/authz_groupfile.load.

-apache was restarted

Restarted apache, all good now.  I've made backup copies of the files I
changed.  Here are the files I modified or created:

After this all seemed to be working.

---
Thank you,

Michael A. Brown
user-eb30166000d4@xymon.invalid
(XXX) XXX-XXXX
M.S. Forensic Studies: Computer Forensics
B.S. Information Technology: Network Specialist

"The only thing necessary for the triumph of evil is for good men to do
nothing" -Edmund Burke


On Tue, Feb 4, 2014 at 9:29 PM, Jeremy Laidman <user-71895fb2e44c@xymon.invalid>wrote:
On 5 February 2014 12:27, Michael Brown <user-eb30166000d4@xymon.invalid> wrote:
I reinstalled everything. And this is what i found. Does the
/usr/lib/xymon error causing what I am seeing.
Probably not.  I'd say that's just a side-effect of you installing the
package over itself.  If you had uninstalled the package first, then
installed it again, you probably wouldn't have seen that message.

J