AW: [suse-security] apache do not start after upd
Hi, we're having almost the same problem: after the last update it's not possible to run both ssl and php4 modules. The first request leads to a segmentation fault as describe in emails before. And I tried with reinstalling all the updated again. For the moment we can work without SSL. So it's not really an issue for use. But maybe for others... Regards, Olly -----Ursprüngliche Nachricht----- Von: Oliver Bleutgen [mailto:meinbugtraq@gmx.net] Gesendet: Dienstag, 9. Juli 2002 11:08 An: admin@i-concept.de; suse-security@suse.com Betreff: Re: [suse-security] apache do not start after upd
Hi list,
I have a strange problem with apache 1.3.19 running on SuSE7.0:
After I have done the last security update from 18 June to apache 1.3.19-115 I am not able to start the webserver with the mod_ssl and/or mod_php (mod_php is for version php3). It is only possible to start the webserver with "httpd -f /etc/httpd/httpd.conf" . If I start the server with "/sbin/init.d/apache start" it seemed to be OK until I do a request to the webserver: Then I got the message in the apache-error-log: "[Mon Jul 8 18:32:50 2002] [notice] child pid 9736 exit signal Segmentation fault (11)" and nothing happens in my browser! The same thing happens if I start the server with "httpd -f /etc/httpd/httpd.conf -D SSL".
If I try to start the server with the option "-D PHP" I got a message "sqlinit: DBROOT must be set !!!" But the DBROOT is set! And the server didn't start.
Anybody there who had the same problem and could help me?
Is it perhaps the php-modul which isn't supported anylonger? I need this machine running php3 not php4 !
Ruediger, have you updated the mod_php etc. packages from 28.April 2001? See http://www.suse.de/de/support/download/updates/70_i386.html If not, do it and try again (with /sbin/init.d/apache start). This will solve the problem with the segfaults, and therefore maybe everything else is no issue anymore. cf. the thread "Apache upgrade from SuSE?" cheer -- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
Hi,
we're having almost the same problem: after the last update it's not possible to run both ssl and php4 modules.
AOL-user: me too :-) I have been forced to install the stuff from scratch, using mod_ssl, mod_php and apache directly from original locations. Change into mod_ssl directory, do a (fix path to new apache sources) ./configure --with-apache=../apache_1.3.26/ --with-ssl=SYSTEM --with-mm=SYST EM change into apache-dir and do a ./configure --prefix=<you new path> --enable-rule=EAPI --enable-module=all --enable-shared=max --<various prefixes for SuSE directorys, i.e. --libexecdir=/usr/lib/apache --sysconfdir=/etc/httpd etc...> --<suexec if desired> then build apache with make, copy the ssl-certs and httpd you are currently using into a temp dir, make a backup of /usr/lib/apache and the /sbin/init.d/apache script and uninstall all SuSE rpms. make install, restore certs, .conf and init script, copy the missing modules from the backup of /usr/lib/apache into the new libexec dir (use a cp -i, no overwrite of new modules), change into mod_php and do a configure with loads of options, make, make install. This is not quick but dirty, but all modules work for me. Take your time to fix path, get the smaller module sources and recompile them if you wish. If the httpd refuses to start, remove all <IfDefine> and <IfModule> statements from httpd.conf and comment the stuff you're not using out (i.e.backhand, dav), starting the server with simply ./httpd Maybe this helps busted 7.0 users to switch to sources :-) Ciao, Dieter --------------------------------------------------------------- Dieter Kirchner Systemadministration BUPNET +49 551 54707 62 D-Goettingen http://www.bupnet.de ---------------------------------------------------------------
Hi Olly, I run the updates from SuSE for the packages and now everything is working fine. I am running mod_php (v.3), mod_ssl, modcontr and mod_perl - no problems with these modules. Take a look on : http://sdb.suse.de/de/sdb/html/jsj_apache_update.html Regards Ruediger Schoenwaelder Oliver wrote:
Hi,
we're having almost the same problem: after the last update it's not possible to run both ssl and php4 modules. The first request leads to a segmentation fault as describe in emails before. And I tried with reinstalling all the updated again. For the moment we can work without SSL. So it's not really an issue for use. But maybe for others...
Regards,
Olly
participants (3)
-
Dieter Kirchner -
ic_admin -
Schoenwaelder Oliver