Greetings,
All of a sudden, I can't access the Nagios web client. It has worked fine for years, but not since I migrated our vSphere 6.5 environment over to a new cluster of hosts and, after rebooting the Nagios VM, it no longer shows up in the Web client.
I logged on the nagios server via ssh, and the nagios service is running, but the apache service is not. I am posting the results below. This is running on CentOS 7.
Any help would be greatly appreciated. Thank you so much.
[root@nagioscore conf.d]# apachectl status
* httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-02-02 10:09:55 EST; 41min ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 2082 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 1229 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 1229 (code=exited, status=1/FAILURE)
Feb 02 10:09:55 nagioscore.iatsenbf.ofc systemd[1]: Starting The Apache HTTP Server...
Feb 02 10:09:55 nagioscore.iatsenbf.ofc httpd[1229]: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Could not open configuration file /etc/httpd/...directory
Feb 02 10:09:55 nagioscore.iatsenbf.ofc systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Feb 02 10:09:55 nagioscore.iatsenbf.ofc kill[2082]: kill: cannot find process ""
Feb 02 10:09:55 nagioscore.iatsenbf.ofc systemd[1]: httpd.service: control process exited, code=exited status=1
Feb 02 10:09:55 nagioscore.iatsenbf.ofc systemd[1]: Failed to start The Apache HTTP Server.
Feb 02 10:09:55 nagioscore.iatsenbf.ofc systemd[1]: Unit httpd.service entered failed state.
Feb 02 10:09:55 nagioscore.iatsenbf.ofc systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@nagioscore conf.d]# apachectl start
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@nagioscore conf.d]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-02-02 10:52:06 EST; 12s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 17276 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 17273 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 17273 (code=exited, status=1/FAILURE)
Feb 02 10:52:06 nagioscore.iatsenbf.ofc systemd[1]: Starting The Apache HTTP Server...
Feb 02 10:52:06 nagioscore.iatsenbf.ofc httpd[17273]: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Could not open configuration file /etc/httpd...directory
Feb 02 10:52:06 nagioscore.iatsenbf.ofc systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Feb 02 10:52:06 nagioscore.iatsenbf.ofc kill[17276]: kill: cannot find process ""
Feb 02 10:52:06 nagioscore.iatsenbf.ofc systemd[1]: httpd.service: control process exited, code=exited status=1
Feb 02 10:52:06 nagioscore.iatsenbf.ofc systemd[1]: Failed to start The Apache HTTP Server.
Feb 02 10:52:06 nagioscore.iatsenbf.ofc systemd[1]: Unit httpd.service entered failed state.
Feb 02 10:52:06 nagioscore.iatsenbf.ofc systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@nagioscore conf.d]#
Can No Longer Access Nagios Web Client
Re: Can No Longer Access Nagios Web Client
I'd like to add that I think this happened from uninstalling OMD, which I thought was done correctly, but now I'm seeing in the results of apachectl configtest that it can't find the config file for zzz_omd.comf (see below).
Can someone please help me clean up the /etc/httpd/conf.d folder so I can start the apache service without omd causing errors?
Thanks so much. Here's some more output:
[root@nagioscore httpd]# apachectl configtest
httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Could not open configuration file /etc/httpd/conf.d/zzz_omd.conf: No such file or directory
[root@nagioscore httpd]# cd /etc/httpd/conf.d
[root@nagioscore conf.d]# ls -l
total 40
-rw-r--r-- 1 root root 2926 Oct 19 16:39 autoindex.conf
-rw-r--r-- 1 root root 1495 Aug 30 2015 cacti.conf
-rw-r--r-- 1 root root 401 Dec 1 13:31 fcgid.conf
-rw-r--r--. 1 root root 1679 Aug 27 2015 nagios.conf
-rw-r--r-- 1 root root 691 Nov 15 11:36 php.conf
-rw-r--r-- 1 root root 922 Oct 1 2015 pnp4nagios.conf
-rw-r--r-- 1 root root 366 Oct 19 16:39 README
-rw-r--r-- 1 root root 158 Oct 1 2015 test_mod_python.conf
-rw-r--r-- 1 root root 1252 Oct 19 12:44 userdir.conf
-rw-r--r-- 1 root root 824 Oct 19 12:44 welcome.conf
lrwxrwxrwx 1 root root 43 Oct 1 2015 zzz_omd.conf -> /omd/versions/default/share/omd/apache.conf
Can someone please help me clean up the /etc/httpd/conf.d folder so I can start the apache service without omd causing errors?
Thanks so much. Here's some more output:
[root@nagioscore httpd]# apachectl configtest
httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Could not open configuration file /etc/httpd/conf.d/zzz_omd.conf: No such file or directory
[root@nagioscore httpd]# cd /etc/httpd/conf.d
[root@nagioscore conf.d]# ls -l
total 40
-rw-r--r-- 1 root root 2926 Oct 19 16:39 autoindex.conf
-rw-r--r-- 1 root root 1495 Aug 30 2015 cacti.conf
-rw-r--r-- 1 root root 401 Dec 1 13:31 fcgid.conf
-rw-r--r--. 1 root root 1679 Aug 27 2015 nagios.conf
-rw-r--r-- 1 root root 691 Nov 15 11:36 php.conf
-rw-r--r-- 1 root root 922 Oct 1 2015 pnp4nagios.conf
-rw-r--r-- 1 root root 366 Oct 19 16:39 README
-rw-r--r-- 1 root root 158 Oct 1 2015 test_mod_python.conf
-rw-r--r-- 1 root root 1252 Oct 19 12:44 userdir.conf
-rw-r--r-- 1 root root 824 Oct 19 12:44 welcome.conf
lrwxrwxrwx 1 root root 43 Oct 1 2015 zzz_omd.conf -> /omd/versions/default/share/omd/apache.conf
-
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: Can No Longer Access Nagios Web Client
Hello, @fodmidoid. I'm not familiar with OMD, and how to properly uninstall it from a Linux system. You might want to refer to their forum instead. But based on the error that you're getting I'd probably start looking at the /etc/httpd/conf/httpd.conf file, and clean it out from any OMD entries.
Here's the httpd.conf from my CentOS 7 system that has Nagios 5.4.12 installed.
Here's the httpd.conf from my CentOS 7 system that has Nagios 5.4.12 installed.
Code: Select all
#
# 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. admin@your-domain.com
#
ServerAdmin root@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
<IfModule mime_magic_module>
#
# 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
</IfModule>
#
# 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
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Can No Longer Access Nagios Web Client
Thanks @npolovenko.
Yeah, I followed instructions from their site to uninstall it, and it seems I did everything correctly. Plus, I checked and I'm not seeing any traces of OMD in the httpd.conf file. However, the symbolic link is still showing up in the /etc/httpd/conf.d directory.
Thanks for your /etc/httpd/conf/httpd.conf output. Here's mine:
Yeah, I followed instructions from their site to uninstall it, and it seems I did everything correctly. Plus, I checked and I'm not seeing any traces of OMD in the httpd.conf file. However, the symbolic link is still showing up in the /etc/httpd/conf.d directory.
Thanks for your /etc/httpd/conf/httpd.conf output. Here's mine:
Code: Select all
#
# 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. admin@your-domain.com
#
ServerAdmin root@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
<IfModule mime_magic_module>
#
# 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
</IfModule>
#
# 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
-
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: Can No Longer Access Nagios Web Client
@fodmidoid, Can you remove the following link from your /etc/httpd/conf.d/ folder?
And here's ls -l of my conf.d folder.
Code: Select all
lrwxrwxrwx 1 root root 43 Oct 1 2015 zzz_omd.conf -> /omd/versions/default/share/omd/apache.conf
Code: Select all
[root@centos7x64 ~]# ls -l /etc/httpd/conf.d/
total 68
-rw-r--r-- 1 root root 2926 Aug 23 10:47 autoindex.conf
-rw-r--r-- 1 root root 1054 Sep 15 09:41 nagios.conf
-rw-r--r-- 1 root root 623 Sep 15 09:41 nagiosmobile.conf
-rw-r--r-- 1 root root 427 Jan 17 13:35 nagiosql.conf
-rw-r--r-- 1 root root 834 Sep 15 09:41 nagiosxi.conf
-rw-r--r-- 1 apache apache 2148 Sep 15 09:40 nagvis.conf
-rwxr-xr-x 1 root root 367 Sep 15 09:41 nrdp.conf
-rw-r--r-- 1 root root 691 Nov 5 2016 php.conf
-rw-r--r-- 1 root root 366 Aug 23 10:48 README
-rw-r--r-- 1 root root 10034 Sep 15 09:39 ssl.conf
-rw-r--r-- 1 root root 9438 Sep 15 09:39 ssl.conf.nagiosxibackup
-rw-r--r-- 1 root root 1252 Aug 23 06:11 userdir.conf
-rw-r--r-- 1 root root 824 Aug 23 06:11 welcome.conf
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Can No Longer Access Nagios Web Client
I was worried about removing the link file, but your advice did the trick! Can't thank you enough.npolovenko wrote:@fodmidoid, Can you remove the following link from your /etc/httpd/conf.d/ folder?Code: Select all
lrwxrwxrwx 1 root root 43 Oct 1 2015 zzz_omd.conf -> /omd/versions/default/share/omd/apache.conf
-
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: Can No Longer Access Nagios Web Client
@fodmidoid, Not a problem! Should we go ahead and lock this thread as resolved?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.