** Changed in: squid
Status: Unknown = New
** Changed in: squid
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid3 gets
Sorry, I've been too busy / other problems since today.
I've upgraded the installation that was affected (3.1.19-1ubuntu3.12.04.1 has
been installed), removed the workaround in rc.conf, rebooted and works fine now!
Thanks a lot for the fix
--
You received this bug notification because you are a
This bug was fixed in the package squid3 - 3.1.19-1ubuntu3.12.04.1
---
squid3 (3.1.19-1ubuntu3.12.04.1) precise-proposed; urgency=low
* d/squid3.upstart: Work around squid not handling SIGHUP by
adding respawn to upstart job. (LP: #978356)
-- Clint Byrum cl...@ubuntu.com
** Changed in: squid3 (Ubuntu Precise)
Milestone: None = ubuntu-12.04.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid3 gets killed at startup with dnsmasq
Fixed for me:
Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148)
killed by ABRT signal
Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended,
respawning
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid3 gets killed at startup with dnsmasq and no
** Branch linked: lp:ubuntu/precise-proposed/squid3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid3 gets killed at startup with dnsmasq and no networkmanager
Here is the patch I have come up with, very simple, but I'm not sure of
the full ramifications:
** Patch added: ignore-sighup-early.patch
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/978356/+attachment/3196698/+files/ignore-sighup-early.patch
** Tags added: patch
--
You received
** Also affects: dnsmasq (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: squid3 (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in
This bug was fixed in the package squid3 - 3.1.19-1ubuntu5
---
squid3 (3.1.19-1ubuntu5) quantal; urgency=low
* d/squid3.upstart: Work around squid not handling SIGHUP by
adding respawn to upstart job. (LP: #978356)
-- Clint Byrum cl...@ubuntu.com Tue, 19 Jun 2012 15:35:19
** Description changed:
+ [ 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
** Branch linked: lp:ubuntu/squid3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid3 gets killed at startup with dnsmasq and no networkmanager
To manage
** Changed in: dnsmasq (Ubuntu Precise)
Status: New = Invalid
** Bug watch added: Squid Bugzilla #3574
http://bugs.squid-cache.org/show_bug.cgi?id=3574
** Also affects: squid via
http://bugs.squid-cache.org/show_bug.cgi?id=3574
Importance: Unknown
Status: Unknown
--
You
the squid patch looks reasonable to me; please forward to the squid-dev
list with a [PATCH] subject.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid3 gets killed
Hello Marco, or anyone else affected,
Accepted squid3 into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
I'm running 12.04 precise 64bit (upgraded from oneric) squid3 (ver
3.1.19) and bind9 and dansguardian. Was working fine until an hour ago
when I apt-get update and apt-get upgrade. Now squid3 is killed by HUP
(so says syslog) and I have to restart squid3 to get everything working.
--
You
For what it's worth, this does not happen with the squid-deb-proxy
package (which uses squid with an optimized config) - at least after
several boot processes.
The init/start script is different, for example, it uses
start on (local-filesystems and net-device-up IFACE!=lo)
instead of
Excerpts from Daniel Hahler's message of Tue May 15 08:53:06 UTC 2012:
For what it's worth, this does not happen with the squid-deb-proxy
package (which uses squid with an optimized config) - at least after
several boot processes.
The init/start script is different, for example, it uses
Have the same behaviour on a x86_64 server freshly-upgraded from Oneiric to
Precise.
On system reboot, squid3 does not start properly - gets killed by HUP signal as
recorded in syslog.
Logging into the system by ssh and manual starting service squid3 helps to
resolve the problem.
But having
And btw, my DNS server on this host is bind9, not dnsmasq.
--
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/978356
Title:
squid3 gets killed at startup with dnsmasq and no
And yes, I reproduced this on i386 as well as on x86_64
--
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/978356
Title:
squid3 gets killed at startup with dnsmasq and no networkmanager
I'm seeing a similar crash on a 12.04 32-bit server in similar
circumstances, however the error is different. Before I open a separate
bug report I thought I'd check with Marco if he sees the following
reports in /var/log/squid3/access.log.1 ?
11:12:24 | Reconfiguring Squid Cache (version
Oops, correction! the error message is in /var/log/squid3/cache.log.1.
I've found an upstream bug that matches the symptoms I see exactly so
I've created a new report bug #988802 squid3 killed by ABRT signal.
assertion failed: disk.cc377: fd = 0
--
You received this bug notification because
Do you think adding a workaround like sleep 5 above the reload into the
resolvconf script makes sense and is good enough for a workaround in Ubuntu
Precise?
Would it be possible to add a loop to detect if the SIGHUP handler is properly
setup already (and send HUP only after that)?
Another idea
Sorry, I've just now recognized that you have a patch already, and so any
workarounds might be void.
Have you uploaded it to a PPA already?
Do you want to propose this patch upstream in Squid's Bugzilla?
This would allow to gain feedback on it before including it in Ubuntu.
--
You received
I haven't had a chance to test it locally yet, other than building the
package. I was hoping to simulate the problem. Hopefully will test in a
few days.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
squid3 includes a resolvconf script to run whenever DNS servers change:
#!/bin/sh
PATH=/usr/sbin:/usr/bin:/sbin:/bin
# Make squid aware of changes to resolv.conf
if status squid3 | grep start/running /dev/null; then
reload squid3
fi
reconfigure also ends a HUP:
if
Where does the HUP signal come from?
Could squid3 -k reconfigure get used there instead? (if it's specific to
squid3)
(I assume you've meant that squid's handler is being installed to late
to map it to reload config instead)
--
You received this bug notification because you are a member of
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
--
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/978356
Title:
squid3 gets killed at startup with dnsmasq
** Branch linked: lp:~clint-fewbar/ubuntu/precise/squid3/ignore-sighup-
early
--
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/978356
Title:
squid3 gets killed at startup with dnsmasq
So I think what is happening is that the network interface is coming up
before squid has installed a handler for SIGHUP.
*tons* of stuff happens between squid starting, and squid installing its
signal handlers. I haven't gone through all of the code but I'm betting
at least one or two stall on
I experience the same issue, but have NetworkManager installed -
although it does not manage the eth0 interface (I am using guessnet for
that).
** Summary changed:
- squid3 crash at startup with dnsmasq and no networkmanager
+ squid3 gets killed at startup with dnsmasq and no networkmanager
--
32 matches
Mail list logo
