you should look at your vhost configs. take an example of the current default_vhost config and make sure to keep the -D DEFAULT_VHOST in /etc/conf.d/apache2 Ive had the same problem with one of my servers and after using the default thiggie it worked fine.
Am Freitag, 7. September 2007 03:08:43 schrieb Kevin O'Gorman: > Somewhere in the update to 2.2.4-r12, listening got lost. I tried to > follow instructions, > but apparently failed. > > Here's what happens (minus a MaxClients warning that doesn't look like a > show-stopper): > > treat init.d # ./apache2 start > * Starting apache2 ... > (98)Address already in use: make_sock: could not bind to address > 64.166.164.49:80 > no listening sockets available, shutting down > Unable to open > logs > [ !! ] > treat init.d # > > So it got my instructions to listen, but failed. > > Looking at 'netstat --inet -l' does not show any listeners or open sockets > on port 80. > > What else should I look at? -- [EMAIL PROTECTED] mailing list
