RE: RC1 installation report
It looks like mod_ssl is preventing apache from stsrting. Thant must be why the init script doestn't shut it down, because it never started. Best luck to you -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Phil Lavigna Sent: Sunday, August 12, 2001 11:18 PM To: [EMAIL PROTECTED] Subject: Re: RC1 installation report Hi, On Sunday 12 August 2001 05:34, Stew Benedict wrote: On Sat, 11 Aug 2001, Phil Lavigna wrote: 1) Apache isn't working properly when mod_ssl is installed. There are no errors in Apache's error_log, and apachectl restart *seems* to work OK (aside from an extra long pause while starting up), but calling up Apache in a web browser returns Connection was refused when attempting to contact 127.0.0.1. I think you and I went over this in private mail when I patched mod_ssl. I never have been able to duplicate your error. I just went through the same set of patches in the pending security updates for 8.0 of apache/php, and I was able to connect to http://localhost as well as https://localhost? I'm experiencing the same problem on a different machine after a brand-new installation; this time it's an iMac. Can anyone on this list see if it's reproduceable on their machine? All I do is select the Web/FTP software group as seen here: http://www.linux-mandrake.com/en/demos/PPC/Test/Install/Reco/pages/reco10.ht ml Then from the desktop, try to access 127.0.0.1 in a web browser: http://www.linux-mandrake.com/en/demos/Demo/Mandrake8.0/QuickLook/pages/feat ures18.php3 If the browser displays an error message such as Could not connect to host, try uninstalling mod_ssl; then see if 127.0.0.1 displays Apache's default page. Thank you in advance for any help. I also don't see the long startup delay. Here is apachectl restart with mod_ssl installed: [root@localhost root]# apachectl restart Shutting down httpd-perl: [ OK ] Starting httpd-perl:[ OK ] Starting httpd: [ OK ] [ OK ] [ OK ] Those last two blank lines are where the delay is happening. And it's missing the step Shutting down httpd. -- Here is apachectl restart with the mod_ssl package removed: [root@localhost root]# apachectl restart Shutting down httpd-perl: [ OK ] Shutting down httpd:[ OK ] Starting httpd-perl:[ OK ] Starting httpd: [ OK ] [root@localhost root]# Bye, Phil
Re: RC1 installation report
Stew, Yep - I'll try this. But it'll have to wait until this afternoon/evening or tomorrow. Got some things on my plate that will keep me away from my computers for most of the day. -Brice Stew Benedict wrote: On Sun, 12 Aug 2001, Brice D Ruth wrote: I get the same behaviour. Might this be because no certificate is installed? I haven't actually checked the configuration ... I know a little about Apache, so I might take a look at this tomorrow or the day after. I do run a web design/production company, so I should know something about this, right? :) -Brice The times I've installed mod_ssl from the command line, a certificate is generated post install. I just tried it agin here using konqueror instead of links and 127.0.0.1 instead of localhost and it still worked for both http and https. This is with the pending security update for apache/php. Can you verify the following in /etc/http/conf/ssl/mod_ssl.conf: # Semaphore: # Configure the path to the mutual explusion semaphore the # SSL engine uses internally for inter-process synchronization. SSLMutex file:logs/ssl_mutex It should not say sem, as that does not seem to work for PPC. I just uninstall all that stuff and went back to the distributed versions and my patch to change the above does not seem to happen. Looking at the spec again, it looks like I need the change in 2 places - 1 for an upgrade, and one for a clean install. Sorry about that. Anyway, changing the above line should work, although I think Phil tried that before and still had issues. Brice can you try that? Stew Benedict
Re: RC1 installation report
On Sun, 12 Aug 2001, Brice D Ruth wrote: I get the same behaviour. Might this be because no certificate is installed? I haven't actually checked the configuration ... I know a little about Apache, so I might take a look at this tomorrow or the day after. I do run a web design/production company, so I should know something about this, right? :) -Brice The times I've installed mod_ssl from the command line, a certificate is generated post install. I just tried it agin here using konqueror instead of links and 127.0.0.1 instead of localhost and it still worked for both http and https. This is with the pending security update for apache/php. Can you verify the following in /etc/http/conf/ssl/mod_ssl.conf: # Semaphore: # Configure the path to the mutual explusion semaphore the # SSL engine uses internally for inter-process synchronization. SSLMutex file:logs/ssl_mutex It should not say sem, as that does not seem to work for PPC. I just uninstall all that stuff and went back to the distributed versions and my patch to change the above does not seem to happen. Looking at the spec again, it looks like I need the change in 2 places - 1 for an upgrade, and one for a clean install. Sorry about that. Anyway, changing the above line should work, although I think Phil tried that before and still had issues. Brice can you try that? Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppcm=99441208917647w=
Re: RC1 installation report
Hi, On Sunday 12 August 2001 05:34, Stew Benedict wrote: On Sat, 11 Aug 2001, Phil Lavigna wrote: 1) Apache isn't working properly when mod_ssl is installed. There are no errors in Apache's error_log, and apachectl restart *seems* to work OK (aside from an extra long pause while starting up), but calling up Apache in a web browser returns Connection was refused when attempting to contact 127.0.0.1. I think you and I went over this in private mail when I patched mod_ssl. I never have been able to duplicate your error. I just went through the same set of patches in the pending security updates for 8.0 of apache/php, and I was able to connect to http://localhost as well as https://localhost? I'm experiencing the same problem on a different machine after a brand-new installation; this time it's an iMac. Can anyone on this list see if it's reproduceable on their machine? All I do is select the Web/FTP software group as seen here: http://www.linux-mandrake.com/en/demos/PPC/Test/Install/Reco/pages/reco10.html Then from the desktop, try to access 127.0.0.1 in a web browser: http://www.linux-mandrake.com/en/demos/Demo/Mandrake8.0/QuickLook/pages/features18.php3 If the browser displays an error message such as Could not connect to host, try uninstalling mod_ssl; then see if 127.0.0.1 displays Apache's default page. Thank you in advance for any help. I also don't see the long startup delay. Here is apachectl restart with mod_ssl installed: [root@localhost root]# apachectl restart Shutting down httpd-perl: [ OK ] Starting httpd-perl:[ OK ] Starting httpd: [ OK ] [ OK ] [ OK ] Those last two blank lines are where the delay is happening. And it's missing the step Shutting down httpd. -- Here is apachectl restart with the mod_ssl package removed: [root@localhost root]# apachectl restart Shutting down httpd-perl: [ OK ] Shutting down httpd:[ OK ] Starting httpd-perl:[ OK ] Starting httpd: [ OK ] [root@localhost root]# Bye, Phil
Re: RC1 installation report
I get the same behaviour. Might this be because no certificate is installed? I haven't actually checked the configuration ... I know a little about Apache, so I might take a look at this tomorrow or the day after. I do run a web design/production company, so I should know something about this, right? :) -Brice Phil Lavigna wrote: Hi, On Sunday 12 August 2001 05:34, Stew Benedict wrote: On Sat, 11 Aug 2001, Phil Lavigna wrote: 1) Apache isn't working properly when mod_ssl is installed. There are no errors in Apache's error_log, and apachectl restart *seems* to work OK (aside from an extra long pause while starting up), but calling up Apache in a web browser returns Connection was refused when attempting to contact 127.0.0.1. I think you and I went over this in private mail when I patched mod_ssl. I never have been able to duplicate your error. I just went through the same set of patches in the pending security updates for 8.0 of apache/php, and I was able to connect to http://localhost as well as https://localhost? I'm experiencing the same problem on a different machine after a brand-new installation; this time it's an iMac. Can anyone on this list see if it's reproduceable on their machine? All I do is select the Web/FTP software group as seen here: http://www.linux-mandrake.com/en/demos/PPC/Test/Install/Reco/pages/reco10.html Then from the desktop, try to access 127.0.0.1 in a web browser: http://www.linux-mandrake.com/en/demos/Demo/Mandrake8.0/QuickLook/pages/features18.php3 If the browser displays an error message such as Could not connect to host, try uninstalling mod_ssl; then see if 127.0.0.1 displays Apache's default page. Thank you in advance for any help. I also don't see the long startup delay. Here is apachectl restart with mod_ssl installed: [root@localhost root]# apachectl restart Shutting down httpd-perl: [ OK ] Starting httpd-perl: [ OK ] Starting httpd:[ OK ] [ OK ] [ OK ] Those last two blank lines are where the delay is happening. And it's missing the step Shutting down httpd. -- Here is apachectl restart with the mod_ssl package removed: [root@localhost root]# apachectl restart Shutting down httpd-perl: [ OK ] Shutting down httpd: [ OK ] Starting httpd-perl: [ OK ] Starting httpd:[ OK ] [root@localhost root]# Bye, Phil
Re: RC1 installation report
Hi Brice, I get the same behaviour. Might this be because no certificate is installed? I haven't actually checked the configuration ... I know a little about Apache, so I might take a look at this tomorrow or the day after. I do run a web design/production company, so I should know something about this, right? :) Thank you for the confirmation; I thought I was overlooking something simple. Unfortunately I don't know enough about Apache to offer many troubleshooting tips, but thanks again for the feedback. See ya' Phil
