touch-packages team mailing list archive

[Thomas Hood <978356@xxxxxxxxxxxxxxxxxx>]

** Summary changed:

- squid3 gets killed at startup with dnsmasq and no networkmanager
+ squid3 gets killed at startup with dnsmasq

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356

Title:
  squid3 gets killed at startup with dnsmasq

Status in Squid Web Proxy Cache:
  New
Status in dnsmasq package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Precise:
  Invalid
Status in squid3 source package in Precise:
  Fix Released

Bug description:
  [ Test case ]
  This is difficult to test as it is a race condition, however there are multiple users affected.

  1. install squid3 on a system which has a system level network connection
  2. reboot
  3. on bootup, check to see if squid3 is running (service squid3 status). If it is not running, check /var/log/syslog and the system console for a message about squid3 being killed by SIGHUP.
  4. Install updated package
  5. repeat step 3, If it is running, this *might* be fixed (but as it is a race, there are no guarantees).

  [ Regression Potential ]
  This update only touches the upstart job, so it will only affect that. Upstart's respawn code is fairly conservative, and the upstart job is fairly straight forward. Definitely a few reboots with updates installed should prove this update regression-free.

  -------------

  I've 12.04 - 32bit pae, and removed networkmanager (aptitude purge) since I'm using it as a LTSP server.
  squid3 3.1.19-1ubuntu1,  dnsmasq 2.59-4
  Linux gnusc 3.2.0-22-generic-pae #35-Ubuntu SMP Tue Apr 3 20:37:36 UTC 2012 i686 athlon i386 GNU/Linux

  I install dnsmasq and squid3. I've noticed that squid3 was never working at boot.
  dmesg shows a:
  root@gs1204:~# dmesg | grep squid
  [   20.227964] init: squid3 main process (1310) killed by HUP signal

  If I remove dnsmasq (aptitude purge) squid has no problem. Don't know if is related to the recent mechanism so resolv.conf is automatically updated by dnsmasq or not.
  At the moment I've setup the workaround of run squid3 from rc.local, but of course is not a clean solution

To manage notifications about this bug go to:
https://bugs.launchpad.net/squid/+bug/978356/+subscriptions