How to prevent i-MSCP installer to disable Apache2 fastcgi module?

**Pimbo** · Dec 26th 2016

Debian 8 64bit

During the Upgrade from 1.3.11 to 1.3.13 an error occured (have a look at the picture).

The status apache output is:

Code

Drop-In: /lib/systemd/system/apache2.service.d└─forking.confActive: failed (Result: exit-code) since Mo 2016-12-26 15:36:17 CET; 6min agoProcess: 27916 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)Dez 26 15:36:17 server1 apache2[27916]: Starting web server: apache2 failed!Dez 26 15:36:17 server1 apache2[27916]: The apache2 configtest failed. ... (warning).Dez 26 15:36:17 server1 apache2[27916]: Output of config test was:Dez 26 15:36:17 server1 apache2[27916]: AH00526: Syntax error on line 222 of /etc/apache2/apache2.conf:Dez 26 15:36:17 server1 apache2[27916]: Invalid command 'FastCGIExternalServer', perhaps misspelled or defined by a module not included in the server configurationDez 26 15:36:17 server1 apache2[27916]: Action 'configtest' failed.Dez 26 15:36:17 server1 apache2[27916]: The Apache error log may have more information.Dez 26 15:36:17 server1 systemd[1]: apache2.service: control process exited, code=exited status=1Dez 26 15:36:17 server1 systemd[1]: Failed to start LSB: Apache2 web server.Dez 26 15:36:17 server1 systemd[1]: Unit apache2.service entered failed state.

The Problem is this line for my seafile configuration in line 222

Code

FastCGIExternalServer /var/www/virtual/cloud.xxx.de/htdocs/seahub.fcgi -host 127.0.0.1:8000

What exactly do I have to do now?

**Pimbo** · Dec 26th 2016

Obviously the module fastcgi was deactivated during the upgrade process. Is this normal?

After manual activation of the mod apache runs normal, but the imscp controlpanel is not working anymore.

Deleting The FASTCGIExternal command, running the upgrade, activatung mod fastcgi, insertig the FASTCGIExternal commadn, restart apache works fine. What do I have to do that the mod fastcgi is not deactivated during the IMSCP Upgrade?

**Nuxwin** · Dec 26th 2016

@'Pimbo'

i-MSCP under Debian Jessie with the apache_php_fpm server implementation do not make usage of the fastcgi module. We make use of the proxy_fcgi module instead. Hence, the fastcgi module is automatically disabled by the installer. However, You can create an i-MSCP listener that will re-enables the module. For instance:

Create the /etc/imscp/listeners.d/10_apache_module_fastcgi.pl file with the following content:

Perl

package Listener::Apache2::Module::FastCGI;
use strict;
use warnings;
use iMSCP::EventManager;
use Servers::httpd;
iMSCP::EventManager->getInstance()->register('afterHttpdBuildFastCgiConfFiles', sub {
Servers::httpd->factory()->enableModules('fastcgi');
});
1;
__END__

Display More

Interesting code part that can help you to understand the issue and also the way I solve it:

How to prevent i-MSCP installer to disable Apache2 fastcgi module?

Share

Daily visitors