Search squid archive

Re: c-icap crashing on signal 10 and 11

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

 



On 26/02/2014 11:05 p.m., Marko Cupać wrote:
> Hi,
> 
> I have squid + squidclamav setup, it serves ~1000 users from FreeBSD
> server with 2Gb of RAM. C-icap is crashing frequently on signal 10 and
> 11:

http://lists.freebsd.org/pipermail/freebsd-hardware/2004-January/001060.html

* sig 10 is usually either broken compile or critical hardware failures.

* sig 11 is usually bad coding but may also be caused by the same issues
leading to sig10.

> 
> Feb 26 09:37:57 rsbgyucnix04 kernel: pid 1534 (c-icap), uid 959: exited
> on signal 10
> Feb 26 09:39:33 rsbgyucnix04 kernel: pid 1536 (c-icap), uid 959: exited
> on signal 10
> ...
> Feb 26 10:39:22 rsbgyucnix04 kernel: pid 1553 (c-icap), uid 959: exited
> on signal 11
> Feb 26 10:39:22 rsbgyucnix04 kernel: pid 5099 (c-icap), uid 959: exited
> on signal 11
> 
> Perhaps squid-users is not the best place to ask about c-icap problem,
> but maybe someone will give me a clue where to start looking.
> 

Best place to look after finding out what the signals mean (above) is at
the vendor you got c-icap or squidclamav from (the relevant FreeBSD
package maintainers) or their upstream projects developers.

Amos





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

  Powered by Linux