[squid-users] Squid 2.6 testing

Hi,

Testing the 2.6 Pre.

With "pipeline_prefetch on " run into a lot of problems.

Jun 18 19:06:16 dns2 squid[20839]: parseHttpRequest: NF
getsockopt(SO_ORIGINAL_DST) failed: (92) Protocol not available
Jun 18 19:07:45 dns2 squid[20839]: parseHttpRequest: NF
getsockopt(SO_ORIGINAL_DST) failed: (92) Protocol not available
Jun 18 19:07:45 dns2 squid[20839]: assertion failed: HttpHeader.c:576: "0"
Jun 18 19:07:45 dns2 squid[20837]: Squid Parent: child process 20839 exited
due to signal 6
Jun 18 19:07:48 dns2 squid[20837]: Squid Parent: child process 20879 started
Jun 18 19:07:48 dns2 squid[20879]: Starting Squid Cache version
2.6.PRE2-20060618 for i686-pc-linux-gnu...

This comes out everytime cachemgr tries to access squid with
'pipeline_prefetch on '. ( Tried new and old versions of cachemgr.cgi ) and
child dies and respawns.

The same cachemgr works fine on my production 2.5.14 caches.

Also for some sites the message is seen( access to many sites, even
connection by cachemgr after pipeline option is removed).

2006/06/18 20:54:46| parseHttpRequest: NF getsockopt(SO_ORIGINAL_DST)
failed: (92) Protocol not available
2006/06/18 21:00:46| parseHttpRequest: NF getsockopt(SO_ORIGINAL_DST)
failed: (92) Protocol not available
2006/06/18 21:00:46| CACHEMGR: root@203.189.128.29 requesting 'info'
2006/06/18 21:02:10| parseHttpRequest: NF getsockopt(SO_ORIGINAL_DST)
failed: (92) Protocol not available
2006/06/18 21:02:11| CACHEMGR: root@203.189.128.29 requesting
'filedescriptors'
2006/06/18 21:02:26| CACHEMGR: root@203.189.128.29 requesting
'filedescriptors'
 ( a refresh doesn't return that error as shown above)

Conclusions.
1. pipeline_prefetech and cachemgr don't like each other ;-)
2. May be transparent mode requires some more fine tuning. ( i used wccp1 )

Couldn't find a way to do stack trace properly, if guided will do more
debugging.

RGDS
Sk
Received on Sun Jun 18 2006 - 08:05:12 MDT