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-deb-proxy (Ubuntu Lucid)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, 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: squid-deb-proxy (Ubuntu Maverick)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bu
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: squid (Ubuntu Maverick)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Excerpts from Skilly's message of Wed Nov 23 12:01:39 UTC 2011:
> On 22 November 2011 05:44, Clint Byrum wrote:
>
> > Hi Skilly, it doesn't make sense that this would cause the bug to
> > regress:
> >
> >
> > http://launchpadlibrarian.net/78309117/squid_2.7.STABLE7-1ubuntu12.3_2.7.STABLE7-1ubuntu
On 22 November 2011 05:44, Clint Byrum wrote:
> Hi Skilly, it doesn't make sense that this would cause the bug to
> regress:
>
>
> http://launchpadlibrarian.net/78309117/squid_2.7.STABLE7-1ubuntu12.3_2.7.STABLE7-1ubuntu12.4.diff.gz
>
> It didn't touch the default args of squid at all. Make sure y
Hi Skilly, it doesn't make sense that this would cause the bug to
regress:
http://launchpadlibrarian.net/78309117/squid_2.7.STABLE7-1ubuntu12.3_2.7.STABLE7-1ubuntu12.4.diff.gz
It didn't touch the default args of squid at all. Make sure you don't
have a modified /etc/init/squid.conf, the exec line
It seems this bug is back with squid version 2.7.STABLE7-1ubuntu12.4 on
Lucid ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
To manage notif
** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
To manage notifications about this bug go to:
https://bugs.launchpad.net/
IF you're using Lucid it's there in updates
gimre@voy:~$ apt-cache policy squid
squid:
Installed: 2.7.STABLE7-1ubuntu12.3
Candidate: 2.7.STABLE7-1ubuntu12.3
Version table:
*** 2.7.STABLE7-1ubuntu12.3 0
500 http://ro.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
100
Is the updated package in the main or still in proposed?
I have run apt-get update and apt-get dist-upgrade, but nothing really happened.
It says that there are no packages to update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Thomas, as martin sya please upgrade to latest release. i use squid
2.7.STABLE7-1ubuntu12.2, and i can confirm that this problem is solved.
squid running very smooth. Thanks Clint!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Thomas C., the fix for Lucid was already released. You just need to
update to version 2.7.STABLE7-1ubuntu12.2 from your current version
2.7.STABLE7-1ubuntu12 as suggested by apt (see Installiert and Kandidat
lines).
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I also have the problem after reload squid service:
apt-cache policy squid
squid:
Installiert: 2.7.STABLE7-1ubuntu12
Kandidat: 2.7.STABLE7-1ubuntu12.2
Versions-Tabelle:
2.7.STABLE7-1ubuntu12.2 0
500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
*** 2.7.STABLE
I believe that the patch made for Natty should work on Maverick as well.
Would anyone more experienced care to make the Maverick package, please?
Clint?
Current Maverick-amd64:
root@localhost:~# apt-cache policy squid
squid:
Installed
On Tue, 2011-03-01 at 14:06 +, Pananza wrote:
> I'm not quite into this package branching thing. When will this fix be
> released in the lucid/main repository?
>
Pananza, the package that fixes this bug has been released into
lucid-updates already.
--
You received this bug notification beca
I'm not quite into this package branching thing. When will this fix be
released in the lucid/main repository?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknow
This bug was fixed in the package squid - 2.7.STABLE7-1ubuntu12.1
---
squid (2.7.STABLE7-1ubuntu12.1) lucid-proposed; urgency=low
* Run squid with -N and drop 'expect fork' to prevent HUP's from
causing upstart to lose track of squid. (LP: #573853)
-- Clint ByrumTue, 01 Feb
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
--
ubuntu-bugs mailing lis
I don't think you should install the Lucid package on Maverick though.
When there will be a package in maverick-proposed, you can test that
one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Ti
Works when installed on Maverick.
root@localhost:~# status squid
squid start/running, process 13708
root@localhost:~# reload squid
root@localhost:~# status squid
squid start/running, process 13708
root@localhost:~# restart squid
squid start/running, process 14256
root@localhost:~# status squid
Confirmed working on Lucid.
root@utest-lls32:~# start squid
squid start/running, process 1724
root@utest-lls32:~# status squid
squid start/running, process 1724
root@utest-lls32:~# reload squid
root@utest-lls32:~# status squid
squid start/running, process 1724
root@utest-lls32:~# ps ax |grep
I'm on maverick now, is it possible to create a package for maverick?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
--
ubuntu-bugs mailing lis
** Branch linked: lp:ubuntu/lucid-proposed/squid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
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!
** Changed in: squid (Ubuntu Lucid)
** Branch linked: lp:ubuntu/lucid/squid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Branch linked: lp:ubuntu/squid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
This bug was fixed in the package squid-deb-proxy - 0.3.4
---
squid-deb-proxy (0.3.4) natty; urgency=low
* Removing expect fork and passing -N to squid to prevent upstart
losing track of squid on reload (LP: #573853)
-- Clint ByrumTue, 11 Jan 2011 15:07:37 -0800
** Changed
This also needs to be fixed in squid-deb-proxy, and in maverick and
lucid.
I've submitted merge proposals for the lucid SRU's and for fixing squid-
deb-proxy in natty.
** Changed in: squid (Ubuntu Lucid)
Status: New => Triaged
** Changed in: squid (Ubuntu Maverick)
Status: New => T
** Branch linked: lp:~clint-fewbar/ubuntu/natty/squid-deb-proxy/no-
expect-fork
** Branch linked: lp:~clint-fewbar/ubuntu/lucid/squid-deb-proxy/no-
expect-fork
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Also affects: squid-deb-proxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
--
ubuntu-
** Description changed:
Binary package hint: upstart
I cannot control squid via upstart.
Squid is running, I want to stop it:
$ sudo stop squid
stop: Unknown instance:
$ ps -ef|grep squid
proxy 1986 1 0 19:44 ?00:00:00 (squid)
liptak3328 1689 0 19:54 pts/
** Description changed:
Binary package hint: upstart
I cannot control squid via upstart.
Squid is running, I want to stop it:
$ sudo stop squid
- stop: Unknown instance:
+ stop: Unknown instance:
$ ps -ef|grep squid
proxy 1986 1 0 19:44 ?00:00:00 (squid)
liptak
This bug was fixed in the package squid - 2.7.STABLE9-2.1ubuntu2
---
squid (2.7.STABLE9-2.1ubuntu2) natty; urgency=low
* Run squid with -N and drop 'expect fork' to prevent HUP's from
causing upstart to lose track of squid. (LP: #573853)
-- Clint ByrumTue, 11 Jan 2011 10:49
** Also affects: squid (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: squid (Ubuntu Maverick)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Clint, in 3.2 we use a process farm:
executed-squid (daemonises to create:
supervisor (listens)
worker
worker
worker
-N will simply mean that the executed process is the supervisor rather
than a daemoniser. Details may vary but I know of no reason that that
wouldn't be doable, easily,
** Branch linked: lp:~clint-fewbar/ubuntu/natty/squid/no-expect-fork
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown instance"
--
ubuntu-bugs mailing list
Setting importance to Medium as the reload command is fairly common and
may disrupt management of squid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573853
Title:
Cannot control squid "Unknown ins
Amos, if I understand you right, there's no way to properly disable
daemonization in squid 3.2+?
Seems that any program that forks and exits its main process on SIGHUP
is unsuitable for use with 'expect fork' or 'expect daemon', so this
begs the question, why can't we disable daemonization without
There seems to be some confusion over the way these squid processes
operates.
In your trace:
"
root 14719 0.0 0.0 24796 1076 ? Ss 14:26 0:00 /usr/sbin/squid
proxy 14721 2.2 0.2 40212 10352 ? Sl 14:26 0:00 (squid)
"
the process "/usr/sbin/squid" is a daemon supervisor. Ensuring worker
"(squid)" pr
Not adding -N, but instead replacing expect fork with expect daemon does
not work as upstart will wait for the middle process to exit, which it
never does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
It seems that what is happening is that squid forks twice to demonize,
but the "middle" process "forgets" to exit, and keeps hanging around.
# ps auxww | fgrep squid
root 2593 0.0 0.1 31792 4884 ?S01:27 0:03 /usr/bin/perl
/usr/sbin/squid-prefetch
root 14719 0.0 0.0 2
** Tags removed: regression-potential
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
btw, in maverick the linked '/etc/init.d/squid' won't be created anymore
-> No upstart hint.
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
A '/usr/bin/squid -k shutdown' returned some errors in my 'squid.conf', which I
corrected.
Afterwards 'start|restart|stop squid' worked.
So it seems that '/usr/bin/squid' causes squid to run even with a faulty
'squid.conf', with warnings, but a 'start squid' does not.
--
Cannot control squid "U
** Tags added: regression-potential
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
I solved it for my case by reducing the "shutdown_lifetime" to 1 seconds in
"/etc/squid/squid.conf" and modifying the
script in "/etc/resolvconf/update-libc.d/squid" to replace
restart squid
by
stop squid;sleep 1;start squid
Which defeat the "restart" intended behavior but doesn't need to wait
I have the very same behaviour. Using the modified post-stop script cures it a
bit as it makes stop and start working again. However, reloading does NOT work.
It seems, squid terminates somehow when a -HUP is received.
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/57
@goraxe, Your change certainly looks functional, but I have concerns
about the potential of waiting forever for it to terminate. I think it
would be really useful if a member of the Ubuntu foundations team looks
further at this. Thanks.
--
Cannot control squid "Unknown instance"
https://bugs.la
the problem is squid waits for 30 (default) seconds to terminate, and
prevents new squid process from spawning. I have just added this to my
/etc/init/squid.conf
this causes upstart to wait for squid to fully exit before declaring it
stopped, this means things like restart squid function as expec
Same issue here:
# service squid reload
reload: Unknown instance:
# reload squid
reload: Unknown instance:
Only with:
# squid -k reconfigure
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
B
This bug has a strange behaviour: Squid restarts just fine if I do it
right after reboot for some time. Can't add more so far, will try to
inspect logs deeper.
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a me
Same issue. Pretty much stock /etc/squid/squid.conf
# dpkg -l squid
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
I get the same error.
h...@home-server:~$ sudo /etc/init.d/squid restart
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service squid restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(
I get the same error,
karth...@ubuntu-desktop:~$ sudo start squid
start: Job failed to start
karth...@ubuntu-desktop:~$ sudo stop squid
stop: Unknown instance:
karth...@ubuntu-desktop:~$ sudo reload squid
reload: Unknown instance:
karth...@ubuntu-desktop:~$ sudo restart squid
restart: Unknown in
error al iniciar o reiniciar squid en ubuntu migrado desde 9.04 a 10.4 lucid al
reiniciar/iniciar
/etc/init.d/squid stard
da el siguiente error
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service squid stard
The script you are attempting to invoke ha
I'm using Squid 3.1 deb package building from source code.
It's working.
On Wed, May 12, 2010 at 8:21 PM, enrigp wrote:
> I have the same problem with network-manager, I cant stop, start o
> restart it
>
> --
> Cannot control squid "Unknown instance"
> https://bugs.launchpad.net/bugs/573853
> Y
I have the same problem with network-manager, I cant stop, start o
restart it
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I did a fresh installation of Lucid. I was also not able to control squid
initctl, immediately after reload.
Then, I did a "squid -k shutdown", and after that I am able to control through
"initctl".
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received t
I just tried with the stock config. It seems the problem appears after
"reload squid" is issued.
# !ps
ps -ef|grep squid
root 4828 1899 0 17:27 pts/700:00:00 grep squid
# !start
start squid
squid start/running, process 4849
# !ps
ps -ef|grep squid
root 4849 1 0 17:28 ?
It is an upgrade. I am using the old config file.
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is this a fresh install or an upgrade? If it is an upgrade do you use
the old config file or the one coming with squid?
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This will be an issue with the squid config
** Package changed: upstart (Ubuntu) => squid (Ubuntu)
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/47319921/Dependencies.txt
--
Cannot control squid "Unknown instance"
https://bugs.launchpad.net/bugs/573853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
63 matches
Mail list logo