Error 500 while trying to switch PHP from modPHP to CGI

Pillola · July 1, 2016, 8:20am

Hi,
as titled i’m trying to switch php to CGI.
I’ve made sure that module CGI is on in webmin configuration and on in virtual server but when i switch from Apache mod_php to CGI_wrapper in website option i recive an Error 500.
I’ve tested it in a new virtual server with only an index.html on.

What i have to do?

Thanks in advance.

Eric · July 1, 2016, 2:59pm

Howdy,

When receiving that 500 error, what shows up in $HOME/logs/error_log? There should be a more descriptive error in that log file.

-Eric

Pillola · July 1, 2016, 3:43pm

Sorry, here’s the log.
[Fri Jul 01 17:38:25.002520 2016] [cgi:error] [pid 5062] [client 79.1.199.10:50137] AH01215: suexec policy violation: see suexec log for more details [Fri Jul 01 17:38:25.002569 2016] [cgi:error] [pid 5062] [client 79.1.199.10:50137] End of script output before headers: php5.cgi [Fri Jul 01 17:38:25.963975 2016] [cgi:error] [pid 5061] [client 79.1.199.10:62704] AH01215: suexec policy violation: see suexec log for more details, referer: http://domain.net/ [Fri Jul 01 17:38:25.964080 2016] [cgi:error] [pid 5061] [client 79.1.199.10:62704] End of script output before headers: php5.cgi, referer: http:/domain.net/ [Fri Jul 01 17:38:48.663053 2016] [cgi:error] [pid 5058] [client 66.249.65.67:58016] AH01215: suexec policy violation: see suexec log for more details [Fri Jul 01 17:38:48.663141 2016] [cgi:error] [pid 5058] [client 66.249.65.67:58016] End of script output before headers: php5.cgi

Thanks,Lorenzo

Eric · July 2, 2016, 2:30pm

Howdy,

I suspect you’re seeing some sort of permissions issue… the suexec logs would have more information.

You’d want to take a peek at that log, in either /var/log/apache2 or /var/log/httpd, it should contain more information about the problem you’re experiencing.

-Eric

Pillola · July 4, 2016, 7:36am

Apache2 log
[Fri Jul 01 17:38:18.180168 2016] [mpm_prefork:notice] [pid 27515] AH00171: Graceful restart requested, doing restart AH00112: Warning: DocumentRoot [/var/www/html] does not exist [Fri Jul 01 17:38:18.208829 2016] [mpm_prefork:notice] [pid 27515] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.17 OpenSSL/1.0.1f configured – resuming normal operations [Fri Jul 01 17:38:18.208841 2016] [core:notice] [pid 27515] AH00094: Command line: ‘/usr/sbin/apache2’

this is apache2.conf

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

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 1000

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

container, error messages relating to that virtual host will be

logged here. If you do define an error logfile for a

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.

Options FollowSymLinks AllowOverride None Require all denied

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

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

#<Directory /srv/>

Options Indexes FollowSymLinks

AllowOverride None

Require all granted

#

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

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