Keep getting 403 Forbidden on /xymon 🔗 link

ScriptAlias /xymon-cgi/ "/usr/local/xymon/cgi-bin/"
<Directory "/usr/local/xymon/cgi-bin">
    AllowOverride None
    Options ExecCGI Includes
    Order allow,deny
    Allow from all
</Directory>

On Thu, December 5, 2013 4:49 pm, Doug Strick wrote:

I just installed xymon on a Fedora 18 local desktop for a POC.  No matter
what I try I can't access the web console.  This apache instance works
fine
on everything else so I'm not sure what I'm missing.  I've ensured the
file
system has global read and execute permissions for all users to view the
content and I've even added apache user to the xymon group.  The apache
error logs show:

AH01630: client denied by server configuration:
/usr/local/xymon/server/www/

Below is my httpd.conf.  I eliminated all other config issues by
commenting
out the Include conf.d/*.conf line and copied the contents of
xymon-apache.conf into httpd.conf directly with no success.  Any other
suggestions?

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/>; for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>;
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are
unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32),
the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share
the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO
you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are
used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
Include conf.modules.d/*.conf

#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User apache
Group apache

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. user-36795ae9911d@xymon.invalid
#
ServerAdmin root at localhost

#
# ServerName gives the name and port that the server uses to identify
itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address
here.
#
#ServerName www.example.com:80

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
    AllowOverride none
    Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"

#
# Relax access to content within /var/www.
#
<Directory "/var/www">
    AllowOverride None
    # Allow open access:
    Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/var/www/html">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI
MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess
files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
    Require all denied
</Files>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile
Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    #CustomLog "logs/access_log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    CustomLog "logs/access_log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to
the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

</IfModule>

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig /etc/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the
server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the
client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
</IfModule>

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default.  To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

#
# The mod_mime_magic module allows the server to use various hints from
the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on

# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
#IncludeOptional conf.d/*.conf
Include conf.d/*.conf

# This file is for Apache 1.3.x and Apache 2.0.x
#
# Add this to your Apache configuration, it makes
# the Xymon webpages and cgi-scripts available in the
# "/xymon" and "/xymon-cgi" URLs.


# NB: The "Alias" line below must NOT be used if you have
#     the Xymon webfiles as the root URL. In that case,
#     you should instead set this:
#
#          DocumentRoot /usr/local/xymon/server/www

Alias /xymon/  "/usr/local/xymon/server/www/"
<Directory "/usr/local/xymon/server/www">
    Options Indexes FollowSymLinks Includes MultiViews
    Order allow,deny
    Allow from all
</Directory>

ScriptAlias /xymon-cgi/ "/usr/local/xymon/cgi-bin/"
<Directory "/usr/local/xymon/cgi-bin">
    AllowOverride None
    Options ExecCGI Includes
    Order allow,deny
    Allow from all
</Directory>

ScriptAlias /xymon-seccgi/ "/usr/local/xymon/cgi-secure/"
<Directory "/usr/local/xymon/cgi-secure">
    AllowOverride None
    Options ExecCGI Includes
    Order allow,deny
    Allow from all

    # Password file where users with access to these scripts are kept.
    # Create it with "htpasswd -c /usr/local/xymon/server/etc/xymonpasswd
USERNAME"
    # Add more users / change passwords with "htpasswd
/usr/local/xymon/server/etc/xymonpasswd USERNAME"
    #
    # You can also use a group file to restrict admin access to members of
a
    # group, instead of anyone who is logged in. In that case you must
setup
    # the "xymongroups" file, and change the "Require" settings to require
    # a specific group membership. See the Apache docs for more details.

    AuthUserFile /usr/local/xymon/server/etc/xymonpasswd
    AuthGroupFile /usr/local/xymon/server/etc/xymongroups
    AuthType Basic
    AuthName "Xymon Administration"

    # "valid-user" restricts access to anyone who is logged in.
    Require valid-user

    # "group admins" restricts access to users who have logged in, AND
    # are members of the "admins" group in xymongroups.
    # Require group admins

</Directory>

# Rewrite-rules for migrating from the URL's used in Hobbit
RewriteEngine On

RewriteRule ^/xymon/bb.html /xymon/xymon.html [R=permanent,L]
RewriteRule ^/xymon/bb2.html /xymon/nongreen.html [R=permanent,L]
RewriteRule ^/xymon/bbnk.html /xymon/critical.html [R=permanent,L]

RewriteRule ^/xymon-cgi/bb-hist.sh /xymon-cgi/history.sh [R=permanent,L]
RewriteRule ^/xymon-cgi/bb-eventlog.sh /xymon-cgi/eventlog.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/bb-rep.sh /xymon-cgi/report.sh [R=permanent,L]
RewriteRule ^/xymon-cgi/bb-replog.sh /xymon-cgi/reportlog.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/bb-snapshot.sh /xymon-cgi/snapshot.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/bb-findhost.sh /xymon-cgi/findhost.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/bb-csvinfo.sh /xymon-cgi/csvinfo.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbitcolumn.sh /xymon-cgi/columndoc.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/bb-datepage.sh /xymon-cgi/datepage.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbitgraph.sh /xymon-cgi/showgraph.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/bb-hostsvc.sh /xymon-cgi/svcstatus.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/bb-histlog.sh /xymon-cgi/historylog.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-confreport.sh /xymon-cgi/confreport.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-confreport-critical.sh
/xymon-cgi/confreport-critical.sh [R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-nkview.sh /xymon-cgi/criticalview.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-certreport.sh /xymon-cgi/certreport.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-nongreen.sh /xymon-cgi/nongreen.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-hostgraphs.sh /xymon-cgi/hostgraphs.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-ghosts.sh /xymon-cgi/ghostlist.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-notifylog.sh /xymon-cgi/notifications.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-hostlist.sh /xymon-cgi/hostlist.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-perfdata.sh /xymon-cgi/perfdata.sh
[R=permanent,L]
RewriteRule ^/xymon-cgi/hobbit-topchanges.sh /xymon-cgi/topchanges.sh
[R=permanent,L]

RewriteRule ^/xymon-seccgi/bb-ack.sh /xymon-seccgi/acknowledge.sh
[R=permanent,L]
RewriteRule ^/xymon-seccgi/hobbit-enadis.sh /xymon-seccgi/enadis.sh
[R=permanent,L]
RewriteRule ^/xymon-seccgi/hobbit-nkedit.sh
/xymon-seccgi/criticaleditor.sh
[R=permanent,L]
RewriteRule ^/xymon-seccgi/hobbit-ackinfo.sh /xymon-seccgi/ackinfo.sh
[R=permanent,L]
RewriteRule ^/xymon-seccgi/hobbit-useradm.sh /xymon-seccgi/useradm.sh
[R=permanent,L]

On 6 December 2013 11:49, Doug Strick <user-1c52a486cbc5@xymon.invalid> wrote:

AH01630: client denied by server configuration:
/usr/local/xymon/server/www/

<Directory />
    AllowOverride none
    Require all denied
</Directory>

<Directory "/usr/local/xymon/server/www">
    Options Indexes FollowSymLinks Includes MultiViews
    Order allow,deny
    Allow from all
</Directory>

On Thu, Dec 5, 2013 at 10:41 PM, Jeremy Laidman <user-71895fb2e44c@xymon.invalid>wrote:

On 6 December 2013 11:49, Doug Strick <user-1c52a486cbc5@xymon.invalid> wrote:

AH01630: client denied by server configuration:
/usr/local/xymon/server/www/

<Directory />
    AllowOverride none
    Require all denied
</Directory>

<Directory "/usr/local/xymon/server/www">
    Options Indexes FollowSymLinks Includes MultiViews
    Order allow,deny
    Allow from all
</Directory>

I notice that the distro-provided config uses "require all ..." whereas
the Xymon config uses "... from all".  From the Apache v2.2 to v2.4 upgrade
doco at

  http://httpd.apache.org/docs/current/upgrading.html#run-time

"In 2.4, such access control is done in the same way as other
authorization checks, using the new module mod_authz_host<http://httpd.apache.org/docs/current/mod/mod_authz_host.html>;.
The old access control idioms should be replaced by the new authentication
mechanisms, although for compatibility with old configurations, the new
module mod_access_compat<http://httpd.apache.org/docs/current/mod/mod_access_compat.html>is provided."

I suspect the "allow from all" is no longer valid, and you need to change
this from "allow from all" "require all granted".  Could be that there's a
warning in the Apache logs at the time you restarted it.

Alternatively, enable the compatibility module as indicated.

It looks like the Xymon installer needs to be updated to detect the use of
the new authorization module and install in a version of config files that
are compatible with Apache v2.4.

Cheers
Jeremy

On Fri, Dec 6, 2013 at 11:43 AM, Doug Strick <user-1c52a486cbc5@xymon.invalid>wrote:

That got me a little further.  Now I just get a directory listing instead
of a 403.  The xymon web console still won't load.  Below is what's in the
access logs when I hit /xymon/.  Also found mod_access_compat is in the
configs and being loaded so not sure why the original config didn't work.
 I've also noticed some of the directories of xymon are empty like
/usr/local/xymon/server/www/html.  Is that normal?

00-base.conf:LoadModule access_compat_module modules/mod_access_compat.so

10.33.98.24 - - [06/Dec/2013:08:37:06 -0800] "GET /xymon/ HTTP/1.1" 200
2336 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/30.0.1599.101 Safari/537.36"
10.33.98.24 - - [06/Dec/2013:08:37:07 -0800] "GET /icons/back.gif
HTTP/1.1" 200 216 "http://buildsystem.xyz.net/xymon/"; "Mozilla/5.0
(Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/30.0.1599.101 Safari/537.36"
10.33.98.24 - - [06/Dec/2013:08:37:07 -0800] "GET /icons/blank.gif
HTTP/1.1" 200 148 "http://buildsystem.xyz.net/xymon/"; "Mozilla/5.0
(Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/30.0.1599.101 Safari/537.36"
10.33.98.24 - - [06/Dec/2013:08:37:07 -0800] "GET /icons/folder.gif
HTTP/1.1" 200 225 "http://buildsystem.xyz.net/xymon/"; "Mozilla/5.0
(Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/30.0.1599.101 Safari/537.36"
10.33.98.24 - - [06/Dec/2013:08:37:07 -0800] "GET /favicon.ico HTTP/1.1"
404 209 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/30.0.1599.101 Safari/537.36"


On Thu, Dec 5, 2013 at 10:41 PM, Jeremy Laidman <user-71895fb2e44c@xymon.invalid>wrote:

On 6 December 2013 11:49, Doug Strick <user-1c52a486cbc5@xymon.invalid> wrote:

AH01630: client denied by server configuration:
/usr/local/xymon/server/www/

<Directory />
    AllowOverride none
     Require all denied
</Directory>

<Directory "/usr/local/xymon/server/www">
    Options Indexes FollowSymLinks Includes MultiViews
    Order allow,deny
    Allow from all
</Directory>

I notice that the distro-provided config uses "require all ..." whereas
the Xymon config uses "... from all".  From the Apache v2.2 to v2.4 upgrade
doco at

  http://httpd.apache.org/docs/current/upgrading.html#run-time

"In 2.4, such access control is done in the same way as other
authorization checks, using the new module mod_authz_host<http://httpd.apache.org/docs/current/mod/mod_authz_host.html>;.
The old access control idioms should be replaced by the new authentication
mechanisms, although for compatibility with old configurations, the new
module mod_access_compat<http://httpd.apache.org/docs/current/mod/mod_access_compat.html>is provided."

I suspect the "allow from all" is no longer valid, and you need to change
this from "allow from all" "require all granted".  Could be that there's a
warning in the Apache logs at the time you restarted it.

Alternatively, enable the compatibility module as indicated.

It looks like the Xymon installer needs to be updated to detect the use
of the new authorization module and install in a version of config files
that are compatible with Apache v2.4.

Cheers
Jeremy

      `'
From: Xymon [xymon-bounces at xymon.com] On Behalf Of Doug Strick [user-1c52a486cbc5@xymon.invalid]
Sent: Friday, December 06, 2013 5:26 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Keep getting 403 Forbidden on /xymon

Since this POC system was a hand me down from a previous employee I went ahead and built a quick VM on my desktop with Fedora 19 and installed everything from scratch.  Still get the 403 with out of box xymon apache configs.  After changing the directory blocks to use "Require all granted" I still get the same behavior of just getting a directory listing.

<user-6e4f7a3bb37f@xymon.invalid>wrote:

Your Apache logs should say why.

--
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
 || \\UTGERS      |---------------------*O*---------------------
 ||_// Biomedical | Ryan Novosielski - Sr. Systems Programmer
 || \\ and Health | user-46c89e614701@xymon.invalid - 973/972.0922 (2x0922)
 ||  \\  Sciences | OIT/EI-Academic Svcs. - ADMC 450, Newark
      `'
From: Xymon [xymon-bounces at xymon.com] On Behalf Of Doug Strick [
user-1c52a486cbc5@xymon.invalid]
Sent: Friday, December 06, 2013 5:26 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Keep getting 403 Forbidden on /xymon

Since this POC system was a hand me down from a previous employee I went
ahead and built a quick VM on my desktop with Fedora 19 and installed
everything from scratch.  Still get the 403 with out of box xymon apache
configs.  After changing the directory blocks to use "Require all granted"
I still get the same behavior of just getting a directory listing.

On Fri, December 6, 2013 10:26 am, Doug Strick wrote:

Right, no errors, but is the console not loading because there's no
content
in some of those directories?  Just trying to figure out if this is still
an apache issue or if we're now down to an app layer issue.  Below is what
I see in the xymongen.log over and over too.

2013-12-06 10:23:05 xymond status-board not available, code 0
2013-12-06 10:23:05 Failed to load current Xymon status, aborting
page-update

Xymon is running as best I can tell.  Below are the pids I see after
starting it.

[user at buildsystem logs]$ ps -ef | grep xymon
xymon     5404     1  0 14:35 ?        00:00:00
/usr/local/xymon/server/bin/xymonlaunch
--config=/usr/local/xymon/server/etc/tasks.cfg
--env=/usr/local/xymon/server/etc/xymonserver.cfg
--log=/usr/local/xymon/logs/xymonlaunch.log
--pidfile=/usr/local/xymon/logs/xymonlaunch.pid
xymon     5405  5404  0 14:35 ?        00:00:00 xymond
--pidfile=/usr/local/xymon/logs/xymond.pid
--restart=/usr/local/xymon/server/tmp/xymond.chk
--checkpoint-file=/usr/local/xymon/server/tmp/xymond.chk
--checkpoint-interval=600 --log=/usr/local/xymon/logs/xymond.log
--admin-senders=127.0.0.1 0.0.0.0 --store-clientlogs=!msgs
xymon     5490  5404  0 14:35 ?        00:00:00 xymond_channel
--channel=stachg --log=/usr/local/xymon/logs/history.log xymond_history
--pidfile=/usr/local/xymon/logs/xymond_history.pid
xymon     5491  5404  0 14:35 ?        00:00:00 xymond_channel
--channel=page --log=/usr/local/xymon/logs/alert.log xymond_alert
--checkpoint-file=/usr/local/xymon/server/tmp/alert.chk
--checkpoint-interval=600
xymon     5492  5404  0 14:35 ?        00:00:00 xymond_channel
--channel=client --log=/usr/local/xymon/logs/clientdata.log xymond_client
xymon     5493  5404  0 14:35 ?        00:00:00 xymond_channel
--channel=status --log=/usr/local/xymon/logs/rrd-status.log xymond_rrd
--rrddir=/usr/local/xymon/data/rrd
xymon     5494  5404  0 14:35 ?        00:00:00 xymond_channel
--channel=data --log=/usr/local/xymon/logs/rrd-data.log xymond_rrd
--rrddir=/usr/local/xymon/data/rrd
xymon     5495  5404  0 14:35 ?        00:00:00 xymond_channel
--channel=clichg --log=/usr/local/xymon/logs/hostdata.log xymond_hostdata
xymon     5500  5404  0 14:35 ?        00:00:00 /bin/sh
/usr/local/xymon/client/bin/xymonclient.sh
xymon     5509  5500  0 14:35 ?        00:00:00 /bin/sh
/usr/local/xymon/client/bin/xymonclient-linux.sh
xymon     5538  5509  0 14:35 ?        00:00:00 sh -c vmstat 300 2
1>/usr/local/xymon/client/tmp/xymon_vmstat.buildsystem.xyz.net.5509 2>&1;
mv /usr/local/xymon/client/tmp/xymon_vmstat.buildsystem.xyz.net.5509
/usr/local/xymon/client/tmp/xymon_vmstat.buildsystem.xyz.net
xymon     5539  5509  0 14:35 ?        00:00:00 sleep 5
xymon     5540  5538  0 14:35 ?        00:00:00 vmstat 300 2


Here's what in the logs:

xymonlaunch.log
2013-12-09 14:35:05 xymonlaunch starting
2013-12-09 14:35:05 Loading tasklist configuration from
/usr/local/xymon/server/etc/tasks.cfg
2013-12-09 14:35:05 Cannot open directory
/usr/local/xymon/server/etc/tasks.d
2013-12-09 14:35:05 Loading hostnames
2013-12-09 14:35:05 Loading saved state
2013-12-09 14:35:05 Setting up network listener on 0.0.0.0:1984
2013-12-09 14:35:05 Setting up signal handlers
2013-12-09 14:35:05 Setting up xymond channels
2013-12-09 14:35:05 Setting up logfiles

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
2013-12-09 14:36:10 xymond status-board not available, code 0
2013-12-09 14:36:10 Failed to load current Xymon status, aborting
page-update
2013-12-09 14:37:10 xymond status-board not available, code 0
2013-12-09 14:37:10 Failed to load current Xymon status, aborting
page-update

xymond.log
2013-12-09 14:35:05 Setup complete

xymonclient.log
df: '/run/user/1005/gvfs': Permission denied
df: '/run/user/1005/gvfs': Permission denied
/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
/usr/local/xymon/client/local/README: line 5: message: command not found
/usr/local/xymon/client/local/README: line 7: This: command not found
/usr/local/xymon/client/local/README: line 7: there: command not found
/usr/local/xymon/client/local/README: line 8: is: command not found
/usr/local/xymon/client/local/README: line 9: scripts.: command not found
/usr/local/xymon/client/local/README: line 11: If: command not found
/usr/local/xymon/client/local/README: line 12: status: command not found
/usr/local/xymon/client/local/README: line 13: instead.: command not found

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

/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

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
<user-71895fb2e44c@xymon.invalid>wrote:

On 10 December 2013 09:39, Doug Strick <user-1c52a486cbc5@xymon.invalid> 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.

On 11 December 2013 03:34, Doug Strick <user-1c52a486cbc5@xymon.invalid> 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.