I just wanted to add that I am also getting these errors on 2x Debian/testing
hosts.
I am not using squidclamav but instead I'm using the libc-icap-mod-virus-scan
package.
Details of the installed packages that I think may be relevant are:
$ dpkg --list | grep -P 'clam|icap|squid'
ii c-icap
Can someone able to replicate this issue please test the upstream patch:
http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3-13407.patch
Amos
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian
> On Fri, 12 Sep 2014 08:01:25 -0500 Dale Schroeder wrote:
>> I don't understand how a log rotation can fail, yet succeed.
>
> The way the log rotation integrates with external log management tools
> is that Squid leaves the external tool to do file renaming or moving,
> and just re-opens the file
forwarded 760303 http://bugs.squid-cache.org/show_bug.cgi?id=4057
On Fri, 12 Sep 2014 08:01:25 -0500 Dale Schroeder wrote:
> I don't understand how a log rotation can fail, yet succeed.
The way the log rotation integrates with external log management tools
is that Squid leaves the external tool
signature Dale Schroeder
Technical Issues
Del Sol Food Company, Inc.
(979)836-5978(979) 836-5978
On 09/11/2014 2:34 PM, Gilles Darold wrote:
Le 10/09/2014 20:49, Dale Schroeder a écrit :
On 09/10/2014 11:41 AM, Mathieu Parent (Debian) wrote:
2014-09-10 17:02 GMT+02:00 Dale Schroeder
:
[...]
W
Le 10/09/2014 20:49, Dale Schroeder a écrit :
>
> On 09/10/2014 11:41 AM, Mathieu Parent (Debian) wrote:
>> 2014-09-10 17:02 GMT+02:00 Dale Schroeder
>> :
>> [...]
>>> With the squidclamav service commented out in c-icap.conf and
>>> squidclamav
>>> package uninstalled, this is the backtrace output
On 09/10/2014 11:41 AM, Mathieu Parent (Debian) wrote:
2014-09-10 17:02 GMT+02:00 Dale Schroeder :
[...]
With the squidclamav service commented out in c-icap.conf and squidclamav
package uninstalled, this is the backtrace output:
[...]
squidclamav directives were active in squid.conf. As men
2014-09-10 17:02 GMT+02:00 Dale Schroeder :
[...]
> With the squidclamav service commented out in c-icap.conf and squidclamav
> package uninstalled, this is the backtrace output:
[...]
> squidclamav directives were active in squid.conf. As mentioned in a
> previous email, commenting the squidclam
On 09/10/2014 1:11 AM, Mathieu Parent (Debian) wrote:
2014-09-09 19:06 GMT+02:00 Dale Schroeder :
[...]
Here's a picture of the screen when I type "run squid3" under gdb
[...]
If I did my research correctly, here's the backtrace output:
#0 0xb7fde424 in __kernel_vsyscall ()
#1 0xb792f267 in
2014-09-09 19:06 GMT+02:00 Dale Schroeder :
>
[...]
>
> Here's a picture of the screen when I type "run squid3" under gdb
>
> [...]
>
> If I did my research correctly, here's the backtrace output:
>
> #0 0xb7fde424 in __kernel_vsyscall ()
> #1 0xb792f267 in __GI_raise (sig=sig@entry=6) at
> ../n
On 09/09/2014 8:57 AM, Mathieu Parent (Debian) wrote:
Hello all,
2014-09-08 22:59 GMT+02:00 Dale Schroeder :
On 09/08/2014 3:24 PM, Gilles Darold wrote:
Le 08/09/2014 19:31, Dale Schroeder a écrit :
It looks like I have found the culprit, and it seems to be specific to
users of squidclamav, l
On 09/09/2014 8:57 AM, Mathieu Parent (Debian) wrote:
Hello all,
2014-09-08 22:59 GMT+02:00 Dale Schroeder :
On 09/08/2014 3:24 PM, Gilles Darold wrote:
Le 08/09/2014 19:31, Dale Schroeder a écrit :
It looks like I have found the culprit, and it seems to be specific to
users of squidclamav, l
On 09/09/2014 8:50 AM, Gilles Darold wrote:
Le 08/09/2014 22:59, Dale Schroeder a écrit :
On 09/08/2014 3:24 PM, Gilles Darold wrote:
Le 08/09/2014 19:31, Dale Schroeder a écrit :
It looks like I have found the culprit, and it seems to be specific to
users of squidclamav, like me. If I commen
Le 08/09/2014 22:59, Dale Schroeder a écrit :
>
> On 09/08/2014 3:24 PM, Gilles Darold wrote:
>> Le 08/09/2014 19:31, Dale Schroeder a écrit :
>>> It looks like I have found the culprit, and it seems to be specific to
>>> users of squidclamav, like me. If I comment the following lines in
>>> squid
Hello all,
2014-09-08 22:59 GMT+02:00 Dale Schroeder :
> On 09/08/2014 3:24 PM, Gilles Darold wrote:
>>
>> Le 08/09/2014 19:31, Dale Schroeder a écrit :
>>>
>>> It looks like I have found the culprit, and it seems to be specific to
>>> users of squidclamav, like me. If I comment the following lin
On 09/08/2014 3:24 PM, Gilles Darold wrote:
Le 08/09/2014 19:31, Dale Schroeder a écrit :
It looks like I have found the culprit, and it seems to be specific to
users of squidclamav, like me. If I comment the following lines in
squid.conf, then squid3 starts and restarts with no errors.
icap_s
Le 08/09/2014 19:31, Dale Schroeder a écrit :
>
> It looks like I have found the culprit, and it seems to be specific to
> users of squidclamav, like me. If I comment the following lines in
> squid.conf, then squid3 starts and restarts with no errors.
>
> icap_service service_req reqmod_precache b
It looks like I have found the culprit, and it seems to be specific to
users of squidclamav, like me. If I comment the following lines in
squid.conf, then squid3 starts and restarts with no errors.
icap_service service_req reqmod_precache bypass=1
icap://127.0.0.1:1344/squidclamav
adaptation_
Now, in addition to the sefault during startup, log rotation is failing
with the following error message:
/etc/cron.daily/logrotate:
2014/09/05 06:25:08| assertion failed: mem.cc:281: "size ==
StrPoolsAttrs[i].obj_size"
Aborted
error: error running shared postrotate script for '/var/log/squid3/
19 matches
Mail list logo
