Processing of apache2_2.2.9-10_i386.changes
apache2_2.2.9-10_i386.changes uploaded successfully to localhost along with the files: apache2_2.2.9-10.dsc apache2_2.2.9-10.diff.gz apache2.2-common_2.2.9-10_i386.deb apache2-mpm-worker_2.2.9-10_i386.deb apache2-mpm-prefork_2.2.9-10_i386.deb apache2-mpm-event_2.2.9-10_i386.deb apache2-utils_2.2.9-10_i386.deb apache2-suexec_2.2.9-10_i386.deb apache2-suexec-custom_2.2.9-10_i386.deb apache2-prefork-dev_2.2.9-10_i386.deb apache2-threaded-dev_2.2.9-10_i386.deb apache2-dbg_2.2.9-10_i386.deb apache2_2.2.9-10_all.deb apache2-doc_2.2.9-10_all.deb apache2-src_2.2.9-10_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
apache2 override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): apache2-mpm-event_2.2.9-10_i386.deb: package says section is web, override says net. apache2-mpm-prefork_2.2.9-10_i386.deb: package says section is web, override says net. apache2-mpm-worker_2.2.9-10_i386.deb: package says section is web, override says net. apache2-prefork-dev_2.2.9-10_i386.deb: package says priority is extra, override says optional. apache2-threaded-dev_2.2.9-10_i386.deb: package says priority is extra, override says optional. apache2-utils_2.2.9-10_i386.deb: package says section is web, override says net. apache2.2-common_2.2.9-10_i386.deb: package says section is web, override says net. apache2_2.2.9-10_all.deb: package says section is web, override says net. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. Please INCLUDE the list of packages as seen above, or we won't be able to deal with your mail due to missing information. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny
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, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny
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 Gnome's nm-applet): --- [ /etc/network/interfaces ] --- # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback I've now explicitly added the used ip addresses to the loopback interface: --- [ /etc/network/interfaces ] # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback up ip addr add 127.0.0.2 dev lo up ip addr add 127.0.0.7 dev lo ... and Apache now start on boot again. I wonder why Apache is able to start without these explicitly added addresses after boot has finished. What's the difference? As it works for me now, you can do what you like with this bug. :) Regards Micha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny
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: alloc_listener: failed to set up sockaddr for 127.0.0.1 Syntax error on line 1 of /etc/apache2/ports.conf: Listen setup failed Once the system has completed the boot sequence, I can manually start the apache daemon by running /etc/init.d/apache2 start without any problem. Please let me know if I can provide any further information. Please provide your /etc/apache2/ports.conf and any other Listen directives you might have in your apache config. 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 Also, please insert ifconfig near the beginning of the apache start script and provide the output during boot. ifconfig outputs the following lines right before apache2 should start: eth0 Link encap:Ethernet HWaddr 00:16:d3:b3:20:08 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:3017 (2.9 KiB) Interrupt:16 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:44 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:16573 (16.1 KiB) TX bytes:16573 (16.1 KiB) vbox0 Link encap:Ethernet HWaddr 00:ff:15:cf:47:17 inet6 addr: fe80::2ff:15ff:fecf:4717/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:19 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:1b:77:04:d2:af UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wmaster0_rename Link encap:UNSPEC HWaddr 00-1B-77-04-D2-AF-6C-6F-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) The /etc/network/interfaces contains nearly nothing (network is managed by NetworkManager using Gnome's nm-applet): --- [ /etc/network/interfaces ] --- # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback You can enable logging to /var/log/boot in /etc/default/bootlogd (no need for screen photos). Bootlogd doesn't work here. I have the same symptoms like those described here: https://bugs.launchpad.net/upstart/+bug/98955 Even though i've enabled it in /etc/default/bootlogd the file /var/log/boot does contain a single bogus line only :( Please provide the output of ifconfig during normal operation (when apache works), too. The output of ifconfig on the system completely booted up (and me logged in with Gnome): eth0 Link encap:Ethernet Hardware Adresse 00:16:d3:b3:20:08 inet Adresse:192.168.1.151 Bcast:192.168.1.255 Maske:255.255.255.0 inet6-Adresse: fe80::216:d3ff:feb3:2008/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:521 errors:0 dropped:0 overruns:0 frame:0 TX packets:581 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:483546 (472.2 KiB) TX bytes:67562 (65.9 KiB) Interrupt:16 loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metrik:1 RX packets:131 errors:0 dropped:0 overruns:0 frame:0 TX packets:131 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:39725 (38.7 KiB) TX bytes:39725 (38.7 KiB) vbox0 Link encap:Ethernet Hardware Adresse 00:ff:15:cf:47:17 inet6-Adresse: fe80::2ff:15ff:fecf:4717/64
Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch - Lenny
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 the reason, then. It seems that the 127.0.0.0/8 subnet is handled specially. I can bind to any address in that subnet without it being configured explicitly. I don't know where this behaviour comes from and why it does not work for you during boot. But I guess explicitly configuring the used ip addresses is always a good idea. Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
