On 10/4/2012 12:06 PM, Tom H wrote: > On Thu, Oct 4, 2012 at 7:23 AM, Stan Hoeppner <s...@hardwarefreak.com> wrote: >> On 10/4/2012 3:46 AM, Rick Thomas wrote: >>> On Oct 3, 2012, at 8:40 PM, Satoru Otsubo wrote: >>>> >>>> But the phenomena are same, that is, >>>> When booting my PC, apache2 failed to start. >>>> And when I executed the following: >>>> # /etc/init.d/apache2 restart >>>> apache2 started successfully with the dual stack. >>>> >>>> Why this phenomena happens ? >>>> >>> >>> Is the apache2 daemon starting before the ipv6 part of the network >>> configuration is completely up? >> >> His log error does seem to indicate Apache is starting before the ipv6 >> stack is available--one of the downsides of parallel init. > > Where did you see the log?
The OP pasted this in his 2nd post: Starting web server: apache2[Thu Oct 04 01:02:03 2012]: [crit] (EAI 9)Address family for hostname not supported: Alloc_listener: failed to set up sockaddr for pppp:qqqq:....:rrrr Syntax error on line 2 of /etc/apache2/ports.conf Listen setup failed. Action 'start' failed. The Apache error log may have more information. failed! I think Chris Bannister is onto something. I previously overlooked the syntax error msg. A syntax error would explain the socket setup failure. Probably something as simple as a typo in ports.conf. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/506ebc4f.3060...@hardwarefreak.com