View previous topic :: View next topic |
Author |
Message |
Dreamchild n00b
Joined: 04 Mar 2004 Posts: 5
|
Posted: Fri Mar 05, 2004 12:41 pm Post subject: Apache2 problem |
|
|
I'm new to Apache2, so please bear with me.
After emerging Apache and setting it all up, I tried:
/etc/init.d/apache2 start
But was only met by this error:
[crit] (92)Protocol not available: make_sock: for address [::]:8080, apr_socket_opt_set: (IPV6_V6ONLY)
no listening sockets available, shutting down
Unable to open logs
I looked on the web for this but the only sites I found relate this problem to the Windows distro of Apache.
Can anyone help? |
|
Back to top |
|
|
adaptr Watchman
Joined: 06 Oct 2002 Posts: 6730 Location: Rotterdam, Netherlands
|
Posted: Fri Mar 05, 2004 1:01 pm Post subject: |
|
|
8080 is hardly the standard port for a webserver - though it should work if you want it to.
Have you looked at the output of
?
If there's something already running there then obviously apache can't bind to the port.
Squid comes to mind.
Apart from that - "after setting everything up" is not really informative.
What did you set up?
How did you configure it ? _________________ >>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
Back to top |
|
|
gorshing n00b
Joined: 18 Nov 2002 Posts: 39 Location: Oklahoma, US
|
Posted: Fri Mar 05, 2004 7:18 pm Post subject: |
|
|
Quote: | Unable to open logs |
What user are you trying to run this as?
That also looks like a permissions problem ... among other things. |
|
Back to top |
|
|
JoeS n00b
Joined: 07 Oct 2003 Posts: 2
|
Posted: Fri Mar 05, 2004 9:43 pm Post subject: |
|
|
I'm having exactly the same error (except port 80, not 8080) after upgrading apache2 ( emerge -uD world). Netstat indictes that port 80 is available. |
|
Back to top |
|
|
bulent n00b
Joined: 06 Mar 2004 Posts: 19
|
Posted: Sun Mar 07, 2004 2:00 am Post subject: same |
|
|
I have got the same problem. tried out different ports as well. Nothing changed. apache didn't like any port. |
|
Back to top |
|
|
MacAI n00b
Joined: 07 Mar 2004 Posts: 1 Location: Münster, Germany
|
Posted: Sun Mar 07, 2004 8:05 am Post subject: me too |
|
|
I have the same problem looking for a solution for hrs now.
ermerged apache with: emerge apache mod_php
USE says -ipv6
hosts doesn't have any ipv6 addresses in it (actually:
127.0.0.1 localhost
192.168.0.88 mysystem
)
starting apache with: /etc/init.d/apache2 start
as root
didn't mess too much with the conf-files, means: didn't change anything in there which could cause this problem (imho!!!!)
All I tried up to now didn't solve this problem and I was looking through all apache posts in this forum.
Bye
Mac |
|
Back to top |
|
|
bulent n00b
Joined: 06 Mar 2004 Posts: 19
|
Posted: Sun Mar 07, 2004 1:21 pm Post subject: |
|
|
you can use:
LISTEN 0.0.0.0:80
and delete -D SSL in apache conf |
|
Back to top |
|
|
gpreston n00b
Joined: 03 Sep 2003 Posts: 42 Location: West Chester, PA
|
Posted: Thu Mar 25, 2004 9:21 pm Post subject: |
|
|
bulent wrote: | you can use:
LISTEN 0.0.0.0:80
and delete -D SSL in apache conf |
What about those people (like myself) who require the "-D SSL" to still be there because we are running a secure web server? |
|
Back to top |
|
|
gpreston n00b
Joined: 03 Sep 2003 Posts: 42 Location: West Chester, PA
|
Posted: Thu Mar 25, 2004 9:28 pm Post subject: |
|
|
Okay, you DO NOT need to delete the "-D SSL" to get this to work. If you modify /etc/apache2/conf/modules.d/40_mod_ssl.conf and change "Listen 443" to "Listen 0.0.0.0:443" it will work. |
|
Back to top |
|
|
eXess Apprentice
Joined: 17 Aug 2003 Posts: 243 Location: Belgium
|
Posted: Fri Mar 26, 2004 8:04 am Post subject: |
|
|
Sorry I'm riding on you rpost, but I got the same problem. Updated Apache to 2.0.49 (emerge -u world), etc-updated config files (nothing unusual here) and upon restart Apache says this:
Code: | [Fri Mar 26 09:02:15 2004] [crit] (92)Protocol not available: make_sock: for address [::]:80, apr_socket_opt_set: (IPV6_V6ONLY)
no listening sockets available, shutting down
Unable to open logs [ !! ] |
I need this to run! How can a simple update do this !!! _________________ . . . . . . . .
eXess |
|
Back to top |
|
|
rumba n00b
Joined: 11 Nov 2002 Posts: 11
|
Posted: Fri Mar 26, 2004 8:46 am Post subject: |
|
|
In /usr/lib/apache2/conf/apache2.conf change
into
|
|
Back to top |
|
|
eXess Apprentice
Joined: 17 Aug 2003 Posts: 243 Location: Belgium
|
Posted: Fri Mar 26, 2004 4:32 pm Post subject: |
|
|
You are SO good... Phew... Praise, applause, thanx and so on...
Any chance we could get a tech advice on why and how this happens after an Apache upgrade?
Furthermore, I have to say that another strange thing happened after upgrading. Modules didn't load because the sumbolic link /etc/apache2/modules/ was pointing to /usr/lib/apache2 instead of /usr/lib/apache2/modules... Strange uh? This prevented Apache from starting (blablabla.so couldn't be found) and once I corrected the link, the other problem appeared.
Anyway: THANKS again _________________ . . . . . . . .
eXess |
|
Back to top |
|
|
dl7und n00b
Joined: 08 Nov 2003 Posts: 13
|
Posted: Wed Apr 07, 2004 11:10 am Post subject: |
|
|
eXess wrote: | You are SO good... Phew... Praise, applause, thanx and so on... |
I second that. This solution was the one that finally brought my apache up again, thanks! |
|
Back to top |
|
|
Gacha n00b
Joined: 24 Apr 2004 Posts: 10 Location: Latvia
|
Posted: Tue Apr 27, 2004 6:21 pm Post subject: |
|
|
I had the same problem as eXess and I did like gpreston sad. And it worked! But want to know why it worked? Why need to change the ports - 80 to 0.0.0.0:80 ? Can someone explain me this?
Sorry for my english |
|
Back to top |
|
|
|