My experience: roughly 30% of boots, squid starts and mid-startup it dies without logging any errors to its own files. At least one occurance, /var/log/messages reports "kernel: [ 42.178904] init: squid3 main process (1274) killed by HUP signal"
I've seen this "premature death" at various stages in the startup e.g. a quick scan of cache.log shows it being killed after: Set Current Directory to /var/spool/squid3 Adding nameserver 192.168.12.1 from /etc/resolv.conf My guess without much testing: there is some kind of race condition/timing issue going on. Squid3 is started by upstart and at roughly the same time /etc/resolvconf/update-libc.d/squid3 is triggered (e.g. by bind9 startup, which was the previous logged event in /var/log/messages) which then sends squid a HUP. Normally a HUP to squid is harmless (reload config), but it seems to be fatal during startup. -- 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/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+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