CGI files are downloading, not executing

[abrist]

It looks like you have issues with your httpd.conf configuration. Those will need to be resolved before this command or apache itself will work as expected.
Can you post a copy of:

Code: Select all

/etc/apache2/apache2.conf

[mcamcintyrem]

Here is the apache2.conf file.

Code: Select all

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#
ServerName <servername>  # censored
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# 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 ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

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


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

[mcamcintyrem]

I'm about to give up on this. I don't understand what could be wrong. This is a fresh install of Ubuntu Server 14.04. I installed Apache, MySQL and PHP during the initial server install. I then install the XFCE4 environment to make managing the server easier. Then I downloaded Nagios Core and the plugins from the Nagios website. I followed all of the instructions. I don't understand what could've gone wrong. I'm about to erase, start over and use a different product.

[mcamcintyrem]

Here's another intersting fact. I also installed Webmin on this server. Webmin uses CGI files and they are working properly. So the problem seems to be with the Nagios install, not Apache.

[abrist]

Well, I did some research on this error at line 74:

Mutex file:${APACHE_LOCK_DIR} default

Looks like Ubuntu had the brilliant idea to use env vars by defualt, but only populate them when apache is run as service. So essentially, any command that would run apache from the cli (like apache2 -M | grep cgi), not through the init system, is now broken.
Is apache in the nagios group:

Code: Select all

grep nag /etc/group

You may have been better off installing nagios3 from aptitude and then upgrading to core 4 from source. This would guarantee that all the necessary dependencies and apache configs are correctly created/configured.

[mcamcintyrem]

OK, I started over. I reinstalled the Ubuntu server again. This time I installed Nagios 3 using Synaptic as you suggested. Nagios is running and I can see the localhost and use the menu. I am also following the instructions on this online article:

http://nagios.sourceforge.net/docs/3_0/ ... ndows.html

I have been able to install the NSCclient++ agent on a Windows server. However, I'm stuck on the part where I need to configure the Nagios server for windows clients. It says to edit the windows.cfg file that's supposed to be located in /usr/local/nagios/etc/objects/ folder, but I can't find that location; it doesn't exist. Also, when I conduct a find command for the windows.cfg, it only locates the sample file that is in the documentation folders. All of the paths indicated in this online article are completely different than the ones on my server. I'm stuck.

[lmiltchev]

Paths will be different, whether or not you install nagios from source or repo. This is perfectly normal.

You can use the "sample" file to create the "windows.cfg" config. After creating new configs or modifying old ones, you will need to verify your configs for errors:

Code: Select all

/etc/sbin/nagios3 -v /etc/nagios3/nagios.cfg

If there are no errors, restart nagios3 so that changes can take effect:

Code: Select all

service nagios3 restart

[jeffa0]

Hi all, users solution wasn't actually a fix to the original problem, I've had this issue for 3 days but knew there must have been an easier way to fix this.

Turns out the whizkids at ubuntu don't enable cgi by default in 14.04 (maybe even previously).

This link should fix the issue if anyone else is having the problem.
http://askubuntu.com/questions/54251/ho ... g-the-text

Fixed it for me.

[sreinhardt]

thanks for the tip, hopefully that helps the OP!

[roachmmflhyr]

I was having the same issue. It can be resolved with adding nagios group to www-data user.

Code: Select all

sudo usermod -a -G nagios www-data
sudo service apache2 restart