Some issues after Update to 2.2.5

[virtualweb]

Hi,

after the update i figured out some issues:

1) in "Management - Server - Services - Monitoring" some items are listed twice (web:80).

2) how does suPHP work within ISPConfig? do we have to install suPHP separately, are there any settings in ISPConfig? Haven't found something about this.

in case of the cms "joomla" all files are owned by webx_office : webx. those files must be writable by www-data. when changing the permissions to www-data, the user can't edit the files via ftp anymore. when the user installs new components in joomla the files are owned by www-data.

Are there any Manuels or Tipps about suPHP for usage with ISPConfig?

Regards,
Alfons

[till]

Originally Posted by virtualweb

1) in "Management - Server - Services - Monitoring" some items are listed twice (web:80).

Well check that.

2) how does suPHP work within ISPConfig? do we have to install suPHP separately, are there any settings in ISPConfig? Haven't found something about this.

in case of the cms "joomla" all files are owned by webx_office : webx. those files must be writable by www-data. when changing the permissions to www-data, the user can't edit the files via ftp anymore. when the user installs new components in joomla the files are owned by www-data.

Are there any Manuels or Tipps about suPHP for usage with ISPConfig?

There are no manuals yet.

1) You will have to install suphp on your server, for exampla as described here:

http://www.howtoforge.com/apache2_suphp_php4_php5

2) Enable SuPHP by changing the line:

$go_info["server"]["apache2_php"] = 'filter,addtype,engine'; // one string of one or more comma seperated options: 'filter' = set PHP filters, 'addtype' = Set PHP addtype, 'both' = Set Filter + Addtype, 'engine' = Use "php_admin_flag engine on/off", suphp = SuPHP wrapper enabled

to:

$go_info["server"]["apache2_php"] = 'suphp'; // one string of one or more comma seperated options: 'filter' = set PHP filters, 'addtype' = Set PHP addtype, 'both' = Set Filter + Addtype, 'engine' = Use "php_admin_flag engine on/off", suphp = SuPHP wrapper enabled

in the file /home/admispconfig/ispconfig/lib/config.inc.php

[virtualweb]

Thank your for the quick reply.

I followed the documentation you suggested, but am not sure, if it is the correct way:

after installing suPHP and restarting the webserver says:

Starting web server: Apache2Syntax error on line 46 of /etc/apache2/vhosts/Vhosts_ispconfig.conf:
Invalid command 'php_admin_value', perhaps mis-spelled or defined by a module not included in the server configuration

All commands which contains "php" are marked as an error, i found following reason for it:

suphp doesn't support the php_flag, php_value, php_admin_value, and 
php_admin_flag directives.  Primarily because mod_php is no longer 
loaded after suphp is installed.  Use suPHP_ConfigPath in each vHost 
and setup individual php.ini files.

As far as i know those directives are generated and used by ISPConfig, so do i really have to setup individual php.ini's for each vhost?

[till]

Originally Posted by virtualweb

As far as i know those directives are generated and used by ISPConfig, so do i really have to setup individual php.ini's for each vhost?

No.

Have you changed the line in config.inc.php?

After you switched your server to suphp, edit one of your websites (change e.g. quota or something else) and hit save so you Vhost_ispconfig.conf gets rewritten with the SuPHP setup.

[virtualweb]

OK that works, as you described it.

Thanks very much!

[Ben]

But don't forget that suPHP needs more ressources on your server in cases of heavy access than mod_php