Re: [squid-users] Squid will not stop

I also did see that if I do service squid status, it says squid is
running, but than says this: "ACL name '209.213.210.178' not defined!"
"FATAL: Bungled squid.conf line 636: http_access allow 209.213.210.178"
"Squid Cache (Version 2.6.STABLE16): Terminated abnormally."

On Dec 9, 2007 8:03 PM, Steve Billig <unknownboogyman@gmail.com> wrote:
> Well doing squid -k parse in terminal doesn't do anything for me, and
> since I installed squid with a .rpm I don't know where the cache.log
> is actually.
>
>
> On Dec 9, 2007 7:59 PM, Steve Billig <unknownboogyman@gmail.com> wrote:
> > Well doing squid -k parse in terminal doesn't do anything for me, and
> > since I installed squid with a .rpm I don't know where the cache.log
> > is actually.
> >
> >
> > On Dec 9, 2007 7:55 PM, Amos Jeffries <squid3@treenet.co.nz> wrote:
> > >
> > > > Well, in Fedora 8, I changed some things in the squid.conf file, so I
> > > > try to restart squid. Both Stopping and Starting failed, so I tried to
> > > > do the commands individually. They both fail, coming up with:
> > > > "Stopping squid... [FAILED]" & "Starting squid... [FAILED]" while
> > > > using the commands service squid stop etc. in root. Since this did not
> > > > work I went to System -> Administration -> Services and it says that
> > > > Squid is running, so I try to stop it and get this message: "squid
> > > > failed. The error was: Stopping squid: [FAILED]". It does work fine to
> > > > my knowledge, using squidclient http://www.google.com/ in terminal and
> > > > it works, also on my Windows machine going through it works. Only
> > > > thing I changed in my configure file was adding a ACL, so I have no
> > > > idea.
> > > >
> > > > Anyone know of anything?
> > >
> > > Ah, this is a little catch-22 in squid.
> > > To pass the start/stop/etc a second instance of squid needs to start for a
> > > short while to generate a control signal.
> > >
> > > If squid.conf contains an error that second instance fails to start and do
> > > its thing. Running "squid -k parse" or a scan of the cache.log should show
> > > you where the problem is. Fix that and the squid controls should work
> > > again.
> > >
> > > Amos
> > >
> > >
> > >
> >
>
Received on Sun Dec 09 2007 - 18:17:58 MST