On 19/05/2006 6:24 p.m., Henrik Nordstrom wrote:
fre 2006-05-19 klockan 14:05 +1200 skrev Reuben Farrelly:
I've just found a minor bug related to this. By specifying in my squid.conf:
wccp2_router 192.168.0.1
then I get no debugging, no wccp2 functionality, and no warning that the syntax
is incorrect (bungled?). Unfortunately the documentation example in squid.conf
doesn't state that a port number is required. (Although the README.wccpv2 does,
but we can't assume that everyone will go looking for it in /doc).
I suggest that if no port is specified, we default to 2048, the same as WCCPv1,
or else I guess I can write a patch to fix the documentation.
Right,
to make it even more fun it currently ignores the port entirely..
Please try if the current source works better for you. Should understand
hosts proper.
Thankyou, yes that seems to have fixed it. Actually works now with an IP
address specified or a hostname and no port required.
Also still seeing a repeatable crash with reconfiguring which only occurs when
WCCPv2 is enabled, if you have a chance to look at it:
2006/05/19 18:29:46| Reconfiguring Squid Cache (version 2.6.DEVEL-CVS)...
2006/05/19 18:29:46| FD 21 Closing HTTP connection
2006/05/19 18:29:46| FD 22 Closing WCCP socket
2006/05/19 18:29:46| FD 22 Closing WCCP socket
2006/05/19 18:29:46| assertion failed: comm.c:726: "F->flags.open"
2006/05/19 18:29:50| Starting Squid Cache version 2.6.DEVEL-CVS for
x86_64-unknown-linux-gnu...
2006/05/19 18:29:50| Process ID 14670
2006/05/19 18:29:50| With 1024 file descriptors available
2006/05/19 18:29:50| DNS Socket created at 0.0.0.0, port 33857, FD 6
(A gdb dump of this was posted to the list a few days ago.)
Thanks,
Reuben
