1 |
you should look at your vhost configs. take an example of the current |
2 |
default_vhost config and make sure to keep the -D DEFAULT_VHOST |
3 |
in /etc/conf.d/apache2 |
4 |
Ive had the same problem with one of my servers and after using the default |
5 |
thiggie it worked fine. |
6 |
|
7 |
Am Freitag, 7. September 2007 03:08:43 schrieb Kevin O'Gorman: |
8 |
> Somewhere in the update to 2.2.4-r12, listening got lost. I tried to |
9 |
> follow instructions, |
10 |
> but apparently failed. |
11 |
> |
12 |
> Here's what happens (minus a MaxClients warning that doesn't look like a |
13 |
> show-stopper): |
14 |
> |
15 |
> treat init.d # ./apache2 start |
16 |
> * Starting apache2 ... |
17 |
> (98)Address already in use: make_sock: could not bind to address |
18 |
> 64.166.164.49:80 |
19 |
> no listening sockets available, shutting down |
20 |
> Unable to open |
21 |
> logs |
22 |
> [ !! ] |
23 |
> treat init.d # |
24 |
> |
25 |
> So it got my instructions to listen, but failed. |
26 |
> |
27 |
> Looking at 'netstat --inet -l' does not show any listeners or open sockets |
28 |
> on port 80. |
29 |
> |
30 |
> What else should I look at? |
31 |
|
32 |
|
33 |
-- |
34 |
gentoo-user@g.o mailing list |