This issue was marked as fixed by an earlier release.
--
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/561750
Title:
squid starts and stops immediately (after upgrade from karmic to
This issue was marked as fixed by an earlier release.
** 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/561750
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: squid3 (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as Won't Fix.
** Changed in: squid3 (Ubuntu Maverick)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
** Also affects: squid3 (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/561750
Title:
squid starts and stops immediately (after
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid3 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid3 (Ubuntu Lucid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid3 (Ubuntu Maverick)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
well, i guess originally this bug had been about 'reload' not working
correctly (#7), but focus has shifted over time.
To keeps things simple I have created a new bug report for the remaining
maverick problem at
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526
--
You received this
Ernst, is the reload vs. restart issue really related to this bug? This
was about doing DNS checks, not a bug in the upstart script. Should
there be a new bug report instead?
BTW, reload is not supposed to kill the daemon. For oneiric, reload
should be fixed to actually work, instead of using
This bug was fixed in the package squid - 2.7.STABLE9-2ubuntu5.1
---
squid (2.7.STABLE9-2ubuntu5.1) maverick-proposed; urgency=low
* debian/squid.upstart: SQUID_ARGS default value set to -D so DNS
checks are not performed at startup (LP: #561750)
-- Clint Byrum
Ernst, thanks for verifying on maverick. We still need somebody to
verify on lucid!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561750
Title:
squid starts and stops immediately
I tested the package from maverick-proposed against the current package
from maverick: both of the problems that were discussed in this bug
report are now gone (squid starts sucessfully with network not being
available yet, resolvconf script reloads the squid configuration and
does not kill squid)
** Tags added: verification-done-maverick
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561750
Title:
squid starts and stops immediately (after upgrade from karmic to
lucid)
--
Accepted squid into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
** Branch linked: lp:ubuntu/maverick-proposed/squid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561750
Title:
squid starts and stops immediately (after upgrade from karmic to
** Branch linked: lp:ubuntu/lucid-proposed/squid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561750
Title:
squid starts and stops immediately (after upgrade from karmic to
** Changed in: squid (Ubuntu Lucid)
Assignee: (unassigned) = Clint Byrum (clint-fewbar)
** Changed in: squid (Ubuntu Lucid)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
Uploaded fixes to maverick-proposed and lucid-proposed.
** Changed in: squid (Ubuntu Maverick)
Assignee: Chuck Short (zulcss) = Clint Byrum (clint-fewbar)
** Changed in: squid (Ubuntu Maverick)
Status: Triaged = Fix Committed
** Changed in: squid (Ubuntu Lucid)
Status: In
** Branch linked: lp:ubuntu/squid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561750
Title:
squid starts and stops immediately (after upgrade from karmic to
lucid)
--
Haven't checked if this is included too but the second Fix is also
(more) important for us (#11):
2) replaced restart squid with reload squid in /etc/resolvconf
/update-libc.d/squid.
Hopefully this is included too. If not squid will continue stopping
right after starting it. This is what I've
Excerpts from Dominik's message of Mon Apr 04 17:30:54 UTC 2011:
Haven't checked if this is included too but the second Fix is also
(more) important for us (#11):
2) replaced restart squid with reload squid in /etc/resolvconf
/update-libc.d/squid.
Hopefully this is included too. If not
This bug was fixed in the package squid - 2.7.STABLE9-2.1ubuntu6
---
squid (2.7.STABLE9-2.1ubuntu6) natty; urgency=low
* debian/squid.upstart: start on changed to start on transition to
runlevel 2 (LP: #561779)
* debian/squid.upstart: SQUID_ARGS default value set to -D so DNS
** Changed in: squid (Ubuntu)
Assignee: Chuck Short (zulcss) = Clint Byrum (clint-fewbar)
** Changed in: squid (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
** Branch linked: lp:~clint-fewbar/ubuntu/natty/squid/beta-fixes
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561750
Title:
squid starts and stops immediately (after upgrade from
** Also affects: squid (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: squid (Ubuntu Lucid)
Status: New = Triaged
** Changed in: squid (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: squid (Ubuntu Lucid)
Milestone: None = ubuntu-10.04.3
--
D J, I would agree with you that -D should be in the default args for
squid. I'm not sure why it was removed, but this counts as a regression
as in karmic -D would allow squid to start without a valid network
connection.
Marking as regression-release, and changing back to Triaged, as I don't
feel
It seems, that this is not fixed in 10.04. We need this fixed in LTS.
# dpkg -l |grep squid
ii squid
2.7.STABLE7-1ubuntu12.2 Internet object cache (WWW
proxy cache)
ii squid-common
** Changed in: squid (Ubuntu Maverick)
Status: In Progress = Fix Released
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs/561750
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Branch linked: lp:ubuntu/squid
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs/561750
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in ubuntu.
--
Ubuntu-server-bugs
** Tags added: server-mrs
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs/561750
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in ubuntu.
--
Ubuntu-server-bugs mailing
** Changed in: squid (Ubuntu)
Status: Fix Committed = In Progress
** Also affects: squid (Ubuntu Maverick)
Importance: Medium
Assignee: Chuck Short (zulcss)
Status: In Progress
--
squid starts and stops immediately (after upgrade from karmic to lucid)
I've done the following and this seems to have solved the issue for me:
1) added a line in /etc/default/squid
SQUID_ARGS='-D'
(disable startup DNS checks, since my server is not always fully started by
the time squid starts)
I'm fairly sure that squid used to be started with -D by default and
I am having the same symptoms on lucid with 2.7.STABLE7-1ubuntu12 . When
I boot the server, squid will not start. I have to manually start it.
All boot methods ; service squid start, squid start, /etc/init.d/squid
start are behaving erractically. Sometimes they work fine, sometimes
they say
Chuck, you said it should be fixed for Lucid back in April. Unfortunately,
I'm still observing
exactly the same problem, of squid starting then immediatly stopping on boot.
I have resolvconf, along with a local copy of bind9 for my home network.
My /etc/resolvconf/update-libc.d/squid has the
This should be fixed now for lucid, thanks for the bug report.
Regards
chuck
** Changed in: squid (Ubuntu)
Status: Incomplete = Fix Committed
** Changed in: squid (Ubuntu)
Assignee: (unassigned) = Chuck Short (zulcss)
--
squid starts and stops immediately (after upgrade from
I have an ethernet interface with a static IP address, there is no
traffic routed to the internet over this interface.
Secondly there is a dsl-connection (pppoe) that provides the route to
the internet.
See also attached file /etc/network/interfaces
But I also have changed /etc/default/squid to
** Attachment added: /etc/default/squid
http://launchpadlibrarian.net/44118845/squid
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs/561750
You received this bug notification because you are a member of Ubuntu
Server Team, which is
$ grep squid /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
$ grep init: /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
Apr 14 07:38:33 rechner6 init: ssh main process (1095) terminated with status
255
On Wed, Apr 14, 2010 at 05:55:34AM -, Ernst Kloppenburg wrote:
$ grep squid /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
$ grep init: /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
Apr 14
- there is no respawn option in /etc/init/squid.conf (but I think this
wouldn't normally be a problem, except when squid crashed by itself)
- there is exactly one thing that does something to squid when the dsl-
interface is brought up (I have resolvconf installed which is suggested
by the squid
Could you outline your network configuration?
Do you see any messages related to init and squid in /var/log/syslog?
** Changed in: squid (Ubuntu)
Importance: Undecided = Medium
** Changed in: squid (Ubuntu)
Status: New = Incomplete
--
squid starts and stops immediately (after
** Attachment added: squid log file
http://launchpadlibrarian.net/43955964/cache.log
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43955337/Dependencies.txt
--
squid starts and stops immediately (after upgrade from karmic to lucid)
43 matches
Mail list logo
