Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2012-02-21 Thread Jean-Michel Vourgère
severity 500558 important found 500558 1.4.2-6+squeeze3 found 500558 1.4.5-1.1 tags 500558 + patch thanks Reverting severity level after return from eglibc Patch posted upstream at https://issues.apache.org/bugzilla/attachment.cgi?id=28360action=diff signature.asc Description: This is a

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2010-12-17 Thread Simon Brady
I've hit the same error on a clean install of lenny with apache2.2-common-2.2.9-10+lenny8. The problem started when I changed the Listen directive in /etc/apache2/ports.conf from Listen 80 to Listen 127.0.1.1:80 (The host is behind a DSL router, but I specifically don't want Apache

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2010-09-12 Thread Stefan Fritsch
On Monday 06 April 2009, Ian Zimmerman wrote: For me, it happens with 127.0.0.1 . I really, really don't want to explicitly say in /e/n/i that lo is 127.0.0.1 . This is intermittent; I'd say it happens about 25% of the time. And, when I manually start apache (with invoke-rc.d apache2

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2010-09-12 Thread Ian Zimmerman
Stefan Do you still have this problem? No, but my interfaces file is slightly different; I have virtual interfaces hanging off lo now. IIRC it was the addition of those that stopped it. Stefan Do you use network-manager? No Stefan What entries do you have in /etc/hosts for ::1, 127.0.0.1,

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2009-04-05 Thread Ian Zimmerman
For me, it happens with 127.0.0.1 . I really, really don't want to explicitly say in /e/n/i that lo is 127.0.0.1 . This is intermittent; I'd say it happens about 25% of the time. And, when I manually start apache (with invoke-rc.d apache2 start) after the boot is done, it starts fine. So, I

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2009-04-05 Thread Ian Zimmerman
See also # 463783, which may or may not be a dupe. -- Ian Zimmerman i...@buug.org gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD Ham is for reading, not for eating. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2008-10-01 Thread Stefan Fritsch
On Wednesday 01 October 2008, Micha Lenk wrote: I wonder why Apache is able to start without these explicitly added addresses after boot has finished. What's the difference? Yes, that's strange. What is the output from cat /proc/sys/net/ipv4/ip_nonlocal_bind after boot? -- To UNSUBSCRIBE,

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2008-10-01 Thread Micha Lenk
Hi again, I wrote: The only Listen directives are in /etc/apache2/ports.conf. Its content is: Listen 127.0.0.1:80 NameVirtualHost 127.0.0.2:80 Listen 127.0.0.2:80 Listen 127.0.0.7:80 [...] The /etc/network/interfaces contains nearly nothing (network is managed by NetworkManager using

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2008-10-01 Thread Micha Lenk
Hi Stefan, Stefan Fritsch wrote: On Monday 29 September 2008, Micha Lenk wrote: recently I upgraded from Etch to Lenny. Now apache2 doesn't start on boot any more. [...] /usr/sbin/apache2ctl start [Mon Sep 29 10:33:20 2008] [crit] (EAI 9)Address family for hostname not supported:

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2008-10-01 Thread Stefan Fritsch
On Wednesday 01 October 2008, you wrote: I wonder why Apache is able to start without these explicitly added addresses after boot has finished. What's the difference? Yes, that's strange. What is the output from cat /proc/sys/net/ipv4/ip_nonlocal_bind after boot? 0 That's not

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2008-09-29 Thread Micha Lenk
Package: apache2.2-common Version: 2.2.9-7 Severity: important Hi, recently I upgraded from Etch to Lenny. Now apache2 doesn't start on boot any more. With -x in /etc/init.d/apache2 I get following output on boot (partial only, typos possible due to screenshot taken by a camera and typed in

Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny

2008-09-29 Thread Stefan Fritsch
On Monday 29 September 2008, Micha Lenk wrote: recently I upgraded from Etch to Lenny. Now apache2 doesn't start on boot any more. With -x in /etc/init.d/apache2 I get following output on boot (partial only, typos possible due to screenshot taken by a camera and typed in afterwards):