We are having a similar problem with the 1.NOVM.4 version on DEC Alphas
(Digital Unix 3.2A). The cache.log output looks normal but it does not
accept any TCP connections anymore (it doesn't log them as denied - it
just freezes). I found out about it when I submitted a cachemgr query and
my browser kept waiting for a response. Interestingly, it logged the
cachemgr request but my browser never received a complete response. Squid
logged about 20 other requests after my cachemgr request and then froze.
Carlos
On Thu, 23 Jan 1997, Miguel A.L. Paraz wrote:
> Hi,
>
> I've hit the problem in the NOVM Squid version with two separate Linux
> machines - one with Linux 2.0.25, the other with 1.2.13. Both are
> 64 MB RAM and 2.5 GB swap machines. From the looks of it the TCP
> socket stops accepting connections, but does not refuse them - it just
> hangs. Strangely, a USR2 signal to stimulate detailed logging output
> reawakens it, but only for a while. The resulting log output is normal
> though it cannot be used to trace much since these are very busy caches,
> with lots of requests, and the machines have to be restarted very
> quickly. :)
>
> In the meantime I've moved them off to regular 1.1.5. I'll see if
> I can replicate the problem with a test server. I'm still looking
> forward to the stability of the VM edition because I'd like to have
> 8 GB of cache while retaining 64 MB of RAM.
>
> Regards,
> --
> miguel a.l. paraz <map@iphil.net> | pgp key id: 0x43F0D011
> iphil communications, makati city, philippines | <http://www.iphil.net>
>
>
>
>
>
>
>
>
>
>
>
>
Received on Thu Jan 23 1997 - 10:18:00 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:34:09 MST