suPHP no longer working after custombuild update

H

Henrik

Verified User
Joined
Mar 14, 2008
Messages
121
Hello,


This night I did an update of the entire server to run CentOS 5.3

Rebooted and all came up fine.

Then, Custombuild had a message that freetype was outdated. so I did a ./build update and then ./build update_versions to see the update go through. I then did ./build php n as suggestion by the build-script.

After doing this, su-php does no longer work.

I look in the logs, and in the error logs this shows:
[error] [client xxx.xxx.xxx.xxx] ParsingException in Configuration.cpp:163: Unknown option "full_php_process_display" in section [global]
[error] [client xxx.xxx.xxx.xxx] Premature end of script headers: index.php

I have tried to do a ./build all d and ./build all y and also ./build rewrite_confs - however none is fixing whatever happened.

/var/log/suphp.log has no content.


My options.conf looks like this:
Code: 
PHP settings. default_php possible values - 4 or 5

default_php=5

php4_cli=no

php4_cgi=no

php5_cli=no

php5_cgi=yes

zend=no



#Possible values - 4.1, 5.0 or 5.1

mysql=5.0

mysql_inst=no

mysql_backup=yes



#Possible values - 1.3, 2.0 or 2.2

apache_ver=2.2



#Web applications

phpmyadmin=yes

atmail=no

squirrelmail=yes

roundcube=yes

uebimiau=no



#Mail options

exim=yes

mail-header-patch=yes

dovecot=yes



#FTP options

proftpd=yes



#Jailed shell (beta)

jail=yes



#CustomBuild options

autover=no

bold=no

clean=yes



#Cron settings

cron=yes

[email protected]

notifications=yes

updates=no



#CustomBuild 1.2 settings

php6_cli=no

php6_cgi=no

php_ini=no

#Possible values - recommended or dist

php_ini_type=recommended

cleanapache=no

fileserver=1

eximconf=no

custombuild=1.1

awstats=yes

webalizer=no

clean_old_webapps=yes

webapps_updates=no

clean_old_tarballs=yes

da_autoupdate=no

Code: 
-----/etc/httpd/conf/extra/httpd-suphp.conf-----

<IfModule mod_suphp.c>
<FilesMatch "\.(inc|php|php3|php4|php5|php6|phtml|phps)$">
AddHandler x-httpd-php5 .inc .php .php3 .php4 .php5 .phtml
</FilesMatch>
<Location />
suPHP_Engine on
suPHP_ConfigPath /usr/local/etc/php5/cgi/
suPHP_AddHandler x-httpd-php5
</Location>
</IfModule>

Code: 
-----/usr/local/suphp/etc/suphp.conf-----
[global]
;Path to logfile
logfile=/var/log/suphp.log

;Loglevel
loglevel=warn

;User Apache is running as
webserver_user=apache

;Path all scripts have to be in
docroot=/

; Security options
allow_file_group_writeable=false
allow_file_others_writeable=false
allow_directory_group_writeable=false
allow_directory_others_writeable=false

; Normally suPHP only displays the PHP binary in process lists (ps aux).
; Setting this option to 'true' will cause suPHP to display both the
; PHP binary and the script filename.
full_php_process_display=true

;Check wheter script is within DOCUMENT_ROOT
check_vhost_docroot=false

;Send minor error messages to browser
errors_to_browser=false

;PATH environment variable
env_path=/bin:/usr/bin

;Umask to set, specify in octal notation
umask=0022

;Minimum UID
min_uid=100

;Minimum GID
min_gid=100

[handlers]
;Handler for php-scripts
x-httpd-php5="php:/usr/local/php5/bin/php-cgi"

;Handler for CGI-scripts
x-suphp-cgi="execute:!self"

Code: 
Parts of /etc/httpd/conf/httpd.conf

ServerRoot "/etc/httpd"
Listen 80

#LoadModule dummy_module /usr/lib/apache/mod_dummy.so
Include /etc/httpd/conf/extra/httpd-phpmodules.conf

User apache
Group apache

ServerAdmin admin@localhost
DocumentRoot "/var/www/html"

*****
<Directory "/var/www/html">
    Options Indexes FollowSymLinks
    AllowOverride All
    Order allow,deny
    Allow from all
   <IfModule mod_suphp.c>
        suPHP_Engine On
        suPHP_UserGroup webapps webapps
   </IfModule>
</Directory>

<IfModule dir_module>
    DirectoryIndex index.html index.htm index.shtml index.php index.php5 index.php4 index.php3 index.phtml index.cgi
</IfModule>

*****

# All suPHP directives
Include conf/extra/httpd-suphp.conf

# All the other includes needed by the custombuild script
Include conf/extra/httpd-includes.conf

Any advice? As it is now, every php-page is not loading on this particular server and it is not a good thing as you might imagine. I have contacted John and the DirectAdmin support as well, but I thought I'd send away a notice here as well to hear if anyone have some advice.


Thank you in advance.
 
And I am a bit tired here it seems, I didn't go for the obvious and edit /etc/httpd/conf/extra/httpd-suphp.conf and take out "full_php_process_display".

Doing so, it is parsing php-pages again. What is really odd is that it worked just fine AFTER updating suPHP the last time and then restarting apache (that I use) :eek:

Anyways, error solved :)
 
I believe "full_php_process_display" is possibly a newer suphp.conf option, so you also could try:

./build suphp
./build all d

to get the newer suphp version.

John
 
I have done the above as I was in the process of finding and fixing the error, however it did not fix the issue. Before doing so, ./build versions already reported that it was running the latest version of suPHP.

Removing the config setting did the trick though, and I am still scratching my head over this.
 
Hello,

Thanks, I'm not too sure either. I've removed the option from the default suphp.conf files for now.

John
 
You must log in or register to reply here.
Back
Top