This issue was reported as fixed by LP: #978356.
** Changed in: squid3 (Ubuntu)
Status: Confirmed => Fix Released
--
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:
** Changed in: squid3 (Ubuntu)
Assignee: (unassigned) => miau (marcos-brav)
--
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/upda
This bug also fixed by patch in bug #978356
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 mem
Since applying the patch my server is now getting good at hitting another squid
bug:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/988802
Since that one is related to reconfiguring the cache during cache-rebuild, I
don't find that surprising.
I expect that this will be the case for a
The attachment "Catch HUP earilier in initialisation" of this bug report
has been identified as being a patch. The ubuntu-reviewers team has
been subscribed to the bug report so that they can review the patch. In
the event that this is in fact not a patch you can resolve this
situation by removin
I've just had a very brief look at the code... I didn't see any reason why the
HUP handling should be delayed (all the handler does is set a variable), so
I've moved it earlier in the code. Patch attached.
Wiser heads than mine might want to check that I've put it in a sane place
(i.e. is ther
Mine is an atom netbook mini server too.
--
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 n
I can see the same on most my reboots on a Atom based mini-server. An
educated guess would be that SIGHUP happens before squid3 actually has
set up its own sighandler for it. And the default is exit.
** Changed in: squid3 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug n
At runtime kill -sighup works fine without any messages in
/var/log/syslog. Service reload as well. The problem seems only to
occure at boot and the only message I found about this the "killed by
HUP signal" mentioned above.
--
You received this bug notification because you are a member of Ubuntu
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 sta
Hi Steffen
Thanks for taking the time to report this bug in Ubuntu.
1) Also /etc/resolvconf/update-libc.d/squid can be deleted in precise
because squid is only a transitional package which leads to an failure
message in upstart.
Agreed - the squid package needs to tidy up files that are no longe
11 matches
Mail list logo