** Description changed: On 12.04 x86 server during start-up. dmesg shows: [ 79.073519] init: squid3 main process (3562) killed by ABRT signal /var/log/squid3/cache.log.1 shows: $ sudo tail /var/log/squid3/cache.log.1 2012/04/26 11:12:23| Loaded Icons. 2012/04/26 11:12:23| Accepting intercepted HTTP connections at 0.0.0.0:3128, FD 14. 2012/04/26 11:12:23| HTCP Disabled. 2012/04/26 11:12:23| Squid plugin modules loaded: 0 2012/04/26 11:12:23| Adaptation support is off. 2012/04/26 11:12:23| Ready to serve requests. 2012/04/26 11:12:23| Store rebuilding is 3.22% complete 2012/04/26 11:12:24| Reconfiguring Squid Cache (version 3.1.19)... 2012/04/26 11:12:24| FD 14 Closing HTTP connection 2012/04/26 11:12:24| assertion failed: disk.cc:377: "fd >= 0" + + In /var/log/syslog + + Apr 26 11:12:23 jeeves dnsmasq-dhcp[3636]: DHCP, IP range 10.254.250.2 -- 10.254.250.254, lease time 1d + Apr 26 11:12:23 jeeves dnsmasq-dhcp[3636]: DHCP, IP range 10.254.251.50 -- 10.254.251.254, lease time 1d + Apr 26 11:12:24 jeeves kernel: [ 71.276249] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware + Apr 26 11:12:24 jeeves pptpd[3814]: MGR: connections limit (100) reached, extra IP addresses ignored + Apr 26 11:12:24 jeeves pptpd[3814]: MGR: connections limit (100) reached, extra IP addresses ignored + Apr 26 11:12:24 jeeves pptpd[3815]: MGR: Manager process started + Apr 26 11:12:24 jeeves pptpd[3815]: MGR: Maximum of 100 connections available + + I suspect this is related to bug #978356 "squid3 gets killed at startup + with dnsmasq and no networkmanager". + + It could be that the squid3 resolver script '/etc/resolvconf/update- + libc.d/squid3' that caused initctl to reload squid3 when dnsmasq starts + and updates '/etc/resolv.conf' causes this. + + The service can be successfully restarted manually but that is no + solution for an unattended server.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0" To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs