Search squid archive

Re: Disabling WCCP service on the router kills squid

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/06/2013 7:42 p.m., Philip Munaawa wrote:
Killing background squid is still not making any difference. It is
self compiled running on slackware 14

On 10 June 2013 21:51, Eliezer Croitoru <eliezer@xxxxxxxxxxxx> wrote:
Try to kill all squid that are might be in the background.
also what OS are you using squid on?
self compiled or from repository?

Eliezer


On 6/10/2013 8:24 PM, Philip Munaawa wrote:
Hi,

I have configured squid 3.3.5 to with wccp deployment mode.

If I disable wccp (no ip wccp web-cache) on the router, while wccp is
running on the squid server, squid shuts down with the debug below:


2013/06/10 17:19:23.732 kid3| wccp2.cc(1168) wccp2HandleUdp:
wccp2HandleUdp: Called.
2013/06/10 17:19:23.732 kid3| Ip::Address::GetSockAddr : Cannot
convert non-IPv4 to IPv4. from [::]
[2013-06-10 17:19:23 UTC] [WARNING] daemon 127.0.0.1 squid[8513]:
Ip::Address::GetSockAddr : Cannot convert non-IPv4 to IPv4. from [::]
[2013-06-10 17:19:23 UTC] [NOTICE] local4 127.0.0.1 squid[8506]: Squid
Parent: (squid-coord-3) process 8513 exited due to signal 6 with
status 0

Signal 6 (assertion) should be resulting in a core dump. If you can locate that and retrieve the stack trace form it you can identify what is leading up to the problem.

Amos




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux