Fw: [SLE] "How do I install PHP via yast2?" saith the newbie.
Sorry, one correction: I meant: "I have NOW gotten apache running"
"How do I install PHP via yast2?" saith the newbie.
HI all.
I have just installed SuSE on an older computer.
I have not gotten apache running (installed it via Yast2 control center).
Sorry, one correction: I meant: "I have NOW gotten apache running"
If I install the PHP module via YAST 2 control center then apache won't run. How do I install PHP via Yast2?
Thanks in advance. Regards from Denmark.
Dan
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thu, 15 May 2003 11:10:03 +0200
"Dan Eskildsen"
Sorry, one correction: I meant: "I have NOW gotten apache running"
"How do I install PHP via yast2?" saith the newbie.
HI all.
I have just installed SuSE on an older computer.
I have not gotten apache running (installed it via Yast2 control center).
Well, all I can advise you to do is go to /etc/sysconfig/apache and make sure ENABLE_SUSCONFIG_APACHE=yes HTTPD_SEC_MOD_PHP=yes then restart apache with "rcapache restart". You should see apache messages that it is restarting and it should list which modules are loading, PhP should be listed. Also you might want to look at /etc/http/httpd/suse_loadmodule.conf it should have a line for loading php4 like: LoadModule php4_module /usr/lib/apache/libphp4.so As far as doing it throught yast2, these settings are all in the various menus. -- use Perl; #powerful programmable prestidigitation
I still can't get my Apache to run with php. ;-( httpd -t at the command line returns: "Syntax OK"
Well, all I can advise you to do is go to /etc/sysconfig/apache and make sure ENABLE_SUSCONFIG_APACHE=yes HTTPD_SEC_MOD_PHP=yes
My /etc/sysconfig/apache file is BELOW, please scroll down. It includes HTTPD_SEC_MOD_PHP=yes but I can't find "ENABLE_SUSCONFIG_APACHE=yes" anywhere. Before I add that line please check it, is it SUSCONFIG or did you mean SYSCONFIG ??
Also you might want to look at /etc/http/httpd/suse_loadmodule.conf it should have a line for loading php4 like: LoadModule php4_module /usr/lib/apache/libphp4.so
/etc/httpd/suse_loadmodule.conf contains the following line: LoadModule php4_module /usr/lib/apache/libphp4.so LoadModule userdir_module /usr/lib/apache/mod_userdir.so *******FILE: /etc/sysconfig/apache ************* # # Set this to yes on the central documentation server # or to configure apache for local use of susehelp. # Then the online-help-system indices are automatically adjusted # and access to the help-files is allowed as specified in DOC_ALLOW. # To run as a client for the central documentation server who's name # is specified in DOC_HOST, just set DOC_SERVER to no. # DOC_SERVER="no" # # /etc/sysconfig/apache: # # # performance class: chose one from "slim", "mid", "thick", "enterprise" # for the number of clients to serve. # SuSEconfig will set MinSpareServers, MaxSpareServers, StartServers, and # MaxClients accordingly (see /sbin/conf.d/SuSEconfig.apache) for the numbers). # HTTPD_PERFORMANCE=slim # # timeout during server startup (seconds) # after this time, the start script decides wether the httpd process started without error. # # Increase it, if you use mod_ssl and your certificate is passphrase protected! # HTTPD_START_TIMEOUT=2 # #security relevant webserver generic configuration items # # # enable status module (yes|no) # HTTPD_SEC_ACCESS_SERVERINFO=no # # Which information is to be revealed about the server (yes|no|email)? # This correlates to the ServerSignature directive. # HTTPD_SEC_SAY_FULLNAME=yes # # email address of the server administrator (ServerAdmin directive) # This address is added to the server's responses if HTTPD_SEC_SAY_FULLNAME is # set to "email". # # If empty ("") it defaults to root@$FQHOSTNAME. FQHOSTNAME is set in # /etc/sysconfig/network/config. # # Note that ServerAdmin directives inside VirtualHost statements are not # changed, including the one for the SSL virtual host. # HTTPD_SEC_SERVERADMIN="" # # do you want to allow access to UserDirs (like /home/*/public_html)? (yes|no) # if yes, this is defined in /etc/httpd/suse_public_html.conf # HTTPD_SEC_PUBLIC_HTML=yes # # end of security relevant part. # # Here you can name files, separated by spaces, that should be Include'd from # httpd.conf. # # This allows you to add e.g. VirtualHost statements without touching # /etc/httpd/httpd.conf itself, which means that SuSEconfig will continue doing its # job (since it would not touch httpd.conf any longer as soon it detects changes # made by the admin via the md5sum mechanism) # HTTPD_CONF_INCLUDE_FILES="" # # enable the PHP module (yes|no) # HTTPD_SEC_MOD_PHP=yes *******END OF FILE************* Any other ideas?
More info about my apache/php problem. I can't get apache to start
with PHP.
Here is a snip from my /var/log/httpd/error.log
[snip]
<!--StartFragment-->[Tue May 20 18:55:34 2003] [notice] Apache/1.3.23
(Unix) configured -- resuming normal operations
[Tue May 20 18:55:34 2003] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Tue May 20 18:55:34 2003] [notice] Accept mutex: sysvsem (Default:
sysvsem)
[Tue May 20 21:41:18 2003] [notice] caught SIGTERM, shutting down
PHP Fatal error: Unable to start session mm module in Unknown on line
0
PHP Fatal error: Unable to start session mm module in Unknown on line
0
PHP Fatal error: Unable to start session mm module in Unknown on line
0
PHP Fatal error: Unable to start session mm module in Unknown on line
0
PHP Fatal error: Unable to start session mm module in Unknown on line
0
PHP Fatal error: Unable to start session mm module in Unknown on line
0
PHP Fatal error: Unable to start session mm module in Unknown on line
0
PHP Fatal error: Unable to start session mm module in Unknown on line
0
[/snip]
----- Original Message -----
From: "Dan Eskildsen"
I still can't get my Apache to run with php. ;-( httpd -t at the command line returns: "Syntax OK"
Well, all I can advise you to do is go to /etc/sysconfig/apache and make sure ENABLE_SUSCONFIG_APACHE=yes HTTPD_SEC_MOD_PHP=yes
My /etc/sysconfig/apache file is BELOW, please scroll down. It includes HTTPD_SEC_MOD_PHP=yes but I can't find "ENABLE_SUSCONFIG_APACHE=yes" anywhere. Before I add that line please check it, is it SUSCONFIG or did you mean SYSCONFIG ??
Also you might want to look at
it should have a line for loading php4 like: LoadModule php4_module /usr/lib/apache/libphp4.so
/etc/httpd/suse_loadmodule.conf contains the following line: LoadModule php4_module /usr/lib/apache/libphp4.so LoadModule userdir_module /usr/lib/apache/mod_userdir.so
*******FILE: /etc/sysconfig/apache ************* # # Set this to yes on the central documentation server # or to configure apache for local use of susehelp. # Then the online-help-system indices are automatically adjusted # and access to the help-files is allowed as specified in DOC_ALLOW. # To run as a client for the central documentation server who's name # is specified in DOC_HOST, just set DOC_SERVER to no. # DOC_SERVER="no" # # /etc/sysconfig/apache: #
# # performance class: chose one from "slim", "mid", "thick", "enterprise" # for the number of clients to serve. # SuSEconfig will set MinSpareServers, MaxSpareServers, StartServers, and # MaxClients accordingly (see /sbin/conf.d/SuSEconfig.apache) for
/etc/http/httpd/suse_loadmodule.conf the
numbers). # HTTPD_PERFORMANCE=slim
# # timeout during server startup (seconds) # after this time, the start script decides wether the httpd process started without error. # # Increase it, if you use mod_ssl and your certificate is passphrase protected! # HTTPD_START_TIMEOUT=2
# #security relevant webserver generic configuration items #
# # enable status module (yes|no) # HTTPD_SEC_ACCESS_SERVERINFO=no
# # Which information is to be revealed about the server (yes|no|email)? # This correlates to the ServerSignature directive. # HTTPD_SEC_SAY_FULLNAME=yes
# # email address of the server administrator (ServerAdmin directive) # This address is added to the server's responses if HTTPD_SEC_SAY_FULLNAME is # set to "email". # # If empty ("") it defaults to root@$FQHOSTNAME. FQHOSTNAME is set in # /etc/sysconfig/network/config. # # Note that ServerAdmin directives inside VirtualHost statements are not # changed, including the one for the SSL virtual host. # HTTPD_SEC_SERVERADMIN=""
# # do you want to allow access to UserDirs (like /home/*/public_html)? (yes|no) # if yes, this is defined in /etc/httpd/suse_public_html.conf # HTTPD_SEC_PUBLIC_HTML=yes
# # end of security relevant part.
# # Here you can name files, separated by spaces, that should be Include'd from # httpd.conf. # # This allows you to add e.g. VirtualHost statements without touching # /etc/httpd/httpd.conf itself, which means that SuSEconfig will continue doing its # job (since it would not touch httpd.conf any longer as soon it detects changes # made by the admin via the md5sum mechanism) # HTTPD_CONF_INCLUDE_FILES="" # # enable the PHP module (yes|no) # HTTPD_SEC_MOD_PHP=yes
*******END OF FILE*************
Any other ideas?
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Tuesday 20 May 2003 10:57, Dan Eskildsen wrote:
More info about my apache/php problem. I can't get apache to start with PHP.
Here is a snip from my /var/log/httpd/error.log [snip]
<!--StartFragment-->[Tue May 20 18:55:34 2003] [notice] Apache/1.3.23 (Unix) configured -- resuming normal operations [Tue May 20 18:55:34 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue May 20 18:55:34 2003] [notice] Accept mutex: sysvsem (Default: sysvsem) [Tue May 20 21:41:18 2003] [notice] caught SIGTERM, shutting down PHP Fatal error: Unable to start session mm module in Unknown on line 0 PHP Fatal error: Unable to start session mm module in Unknown on line
Dan - This is caused because the mod_php is calling for a larger shared memory segment than you have available. If you are running 8.2, you can fix this by setting SHMMAX to 33554432, this is done through YaST->System->Sysconfig Editor->System->Kernel->SHMFS-SIZE If you are running 8.1, you'll have to use Powertweak; access Powertwek through YaST->System->Powertweak Configuration->kernel/shmall (set it to 33554432 as well) YaST->System->Powertweak Configuration->KERNEL-SHMALL (I set this to 30, you can tweak it until it works for you) then activate the Powertwek service in the runlevel editor YaST->System->Runlevel Editor and make sure the Powertweak service is enabled. This could be fixed is SuSE would release an updated PHP which didn't request such a large initial shared memory segment (this is what the "mm" error is, I found it searching the mod_php website). Mark Almeida
On Tuesday 20 May 2003 10:57, Dan Eskildsen wrote:
More info about my apache/php problem. I can't get apache to start with PHP.
Here is a snip from my /var/log/httpd/error.log [snip]
<!--StartFragment-->[Tue May 20 18:55:34 2003] [notice] Apache/1.3.23 (Unix) configured -- resuming normal operations [Tue May 20 18:55:34 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue May 20 18:55:34 2003] [notice] Accept mutex: sysvsem (Default: sysvsem) [Tue May 20 21:41:18 2003] [notice] caught SIGTERM, shutting down PHP Fatal error: Unable to start session mm module in Unknown on
0 PHP Fatal error: Unable to start session mm module in Unknown on
Thanks heaps!
I'll look into it.
I am running SuSE 8.0
----- Original Message -----
From: "The Wizard"
Dan - This is caused because the mod_php is calling for a larger
segment than you have available. If you are running 8.2, you can fix
shared memory this by
setting SHMMAX to 33554432, this is done through
YaST->System->Sysconfig Editor->System->Kernel->SHMFS-SIZE
If you are running 8.1, you'll have to use Powertweak; access Powertwek through
YaST->System->Powertweak Configuration->kernel/shmall (set it to 33554432 as well) YaST->System->Powertweak Configuration->KERNEL-SHMALL (I set this to 30, you can tweak it until it works for you)
then activate the Powertwek service in the runlevel editor
YaST->System->Runlevel Editor
and make sure the Powertweak service is enabled.
This could be fixed is SuSE would release an updated PHP which didn't request such a large initial shared memory segment (this is what the "mm" error is, I found it searching the mod_php website).
Mark Almeida
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Dan Eskildsen -
The Wizard -
zentara