this version is older than what was shipped in precise. Tested on
xenial, and updating the package from main -> updates worked just fine.
Re-open if you can repro with modern versions.
** Changed in: squid (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification beca
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: squid (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
cache.log, attached, shows nothing odd AFAICS, normal shutdown. dist-
upgrade failed,
Preparing to replace squid 2.7.STABLE9-2ubuntu5.1 (using
.../squid_2.7.STABLE9-2ubuntu5.2_amd64.deb) ...
Unpacking replacement squid ...
Processing triggers for ureadahead ...
ureadahead will be
I'm new to this forum. :) I have Ubuntu 11.04 and squid 2.7 was freshly
installed after DansGuardian2. When I tried to start squid fresh, I get
this error message:
maj@Emeth:~$ sudo squid start
2011/07/28 00:15:10| ACL name 'all' not defined!
FATAL: Bungled squid.conf line 176: http_reply_access a
Judging by the number of dupe reports, I'm raising this to High, as it
seems to affect more than just a small subset of users.
** Changed in: squid (Ubuntu)
Importance: Medium => High
** Changed in: squid (Ubuntu Lucid)
Importance: Medium => High
--
You received this bug notification beca
My cache.log surrounding the time when the update failed (2011/04/09
08:32:11):
2011/04/09 06:48:00| storeDirWriteCleanLogs: Starting...
2011/04/09 06:48:00| Finished. Wrote 4384 entries.
2011/04/09 06:48:00| Took 0.0 seconds (2124031.0 entries/sec).
2011/04/09 06:48:00| logfileRotate: /var/l
My cache.log doesn't show errors. Only a few warnings (I think at shutdown
or hibernate):
2011/03/25 20:10:10| Beginning Validation Procedure
2011/03/25 20:10:10| Completed Validation Procedure
2011/03/25 20:10:10| Validated 1151 Entries
2011/03/25 20:10:10| store_swap_size = 90128k
2011/03/
jdiasn, This is an issue with your configuration file. You'll need to
read squid's manual (there is a lot of help in the squid.conf itself) to
know how its supposed to work. The error message says that on line 176
there's an error, so try fixing that line.
--
You received this bug notification be
Clint Byrum, how fix I this problem?
Can you help me?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729288
Title:
squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2
--
ubuntu-b
jdiasn, in that case you actually have an error in your squid.conf.. you
need to fix that or squid won't be able to start.
Could all those affected check their /var/log/squid/cache.log and make
sure its not just a config problem?
--
You received this bug notification because you are a member of
** Changed in: squid (Ubuntu)
Importance: Undecided => Medium
** Also affects: squid (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: squid (Ubuntu Lucid)
Importance: Undecided => Medium
** Changed in: squid (Ubuntu Lucid)
Status: New => Confirmed
--
You r
opps, What do I do?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729288
Title:
squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
I have same problem, In cache.log I found it
FATAL: Bungled squid.conf line 176: http_reply_access allow all
Squid Cache (Version 2.7.STABLE7): Terminated abnormally.
https://bugs.launchpad.net/bugs/730041
What do I now?
--
You received this bug notification because you are a member of Ubuntu
Oops, I meant bug #726348 , not bug #736348
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729288
Title:
squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2
--
ubuntu-bugs mailing
For all affected parties, while we figure out what has caused this
exactly, if you could possibly provide your /etc/squid/squid.conf , and
the logs from /var/log/squid/cache.log and the output of 'grep init:
/var/log/daemon.log', that would be extremely helpful in debugging the
issue. Please be car
I've been unable to reproduce this, but there are a ton of duplicates so
there is no doubt that there is something wrong with the lucid updates.
I actually think this is directly related to bug #736348 . By calling
'restart' directly, we are not re-loading the new job file. So until the
system is
** Summary changed:
- package squid 2.7.STABLE7-1ubuntu12.2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
+ squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2
--
You received this bug notification because you are a membe
17 matches
Mail list logo