Hi Jim,
On 06.06.2014 02:58, Jim Barber wrote:
After reading the discussion on the upstream bug report, it looks like
perhaps these error messages in the logs were relevant after all...
- ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted
- ScanOnAccess: clamd must be
Control: tags -1 fixed-upstream pending
Hi Jim,
upstream fixed the problem and I have backported the fix for Debian, so
that it will be included in the next upload.
Until then just disable ScanOnAccess to work around the problem.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to
On 6/06/2014 2:24 AM, Andreas Cadhalpun wrote:
Control: tags -1 fixed-upstream pending
Hi Jim,
upstream fixed the problem and I have backported the fix for Debian, so that it
will be included in the next upload.
Until then just disable ScanOnAccess to work around the problem.
Best regards,
On June 5, 2014 6:58:07 PM MDT, Jim Barber jim.bar...@ddihealth.com wrote:
On 6/06/2014 2:24 AM, Andreas Cadhalpun wrote:
Control: tags -1 fixed-upstream pending
Hi Jim,
upstream fixed the problem and I have backported the fix for Debian,
so that it will be included in the next upload.
On June 5, 2014 6:58:07 PM MDT, Jim Barber jim.bar...@ddihealth.com wrote:
On 6/06/2014 2:24 AM, Andreas Cadhalpun wrote:
Control: tags -1 fixed-upstream pending
Hi Jim,
upstream fixed the problem and I have backported the fix for Debian,
so that it will be included in the next upload.
Hi Andreas.
On 29/05/2014 5:10 PM, Andreas Cadhalpun wrote:
Thanks for your help in finding the cause.
Since the logs are inconclusive, it would really help if you could get us a
backtrace, when clamd is hanging.
For this install clamav-dbg and gdb.
When it hangs again, please determine the
Control: forwarded -1 https://bugzilla.clamav.net/show_bug.cgi?id=11028
Hi Jim,
On 04.06.2014 10:40, Jim Barber wrote:
Okay, I have a hang, and I have the gdb output that you want.
Thanks for the backtrace.
First the PID and Threads:
# ps -eL | grep -P 'LWP|clamd'
PID LWP TTY
Hi Andreas.
On 29/05/2014 5:10 PM, Andreas Cadhalpun wrote:
On 28.05.2014 02:55, Jim Barber wrote:
On 2014-05-27 18:39, Andreas Cadhalpun wrote:
I think the problem here is that there is a second 'Restarting
on-access scan' message only 4 seconds after another one and without
the usual
Hi Jim,
On 28.05.2014 02:55, Jim Barber wrote:
On 2014-05-27 18:39, Andreas Cadhalpun wrote:
I think the problem here is that there is a second 'Restarting
on-access scan' message only 4 seconds after another one and without
the usual 'ERROR: ScanOnAccess: fanotify_init [...]' between them.
Hi Jim,
On 27.05.2014 07:18, Jim Barber wrote:
The ClamAV daemon hung again after rolling back to 0.98.3.
You could try it with 0.98.1, but I'm not sure if that would help.
It went longer than a day this time, but still less than 2 days.
Here's the havp log (with URL removed).
Hi Andreas
On 2014-05-27 18:39, Andreas Cadhalpun wrote:
Hi Jim,
You could try it with 0.98.1, but I'm not sure if that would help.
I think I'll keep moving on with the new versions, and hopefully we
can find the real problem.
I think the problem here is that there is a second 'Restarting
The ClamAV daemon hung again after rolling back to 0.98.3.
It went longer than a day this time, but still less than 2 days.
Here's the havp log (with URL removed).
25/05/2014 08:51:59 === Starting HAVP Version: 0.92
25/05/2014 08:51:59 Running as user: havp, group: havp
25/05/2014
On 2014-05-23 20:13:54 [+0800], Jim Barber wrote:
So the sequence of events was the upgrade on the 19th; freshclam on the
20th;
then the first hang on the 21st.
I see. Could you please go back to 0.98.3 and see if the issue goes
away? It might be a regression in the comming up 0.98.4 of
On 2014-05-24 22:23, Sebastian Andrzej Siewior wrote:
I see. Could you please go back to 0.98.3 and see if the issue goes
away? It might be a regression in the comming up 0.98.4 of clamav. Just
want to make sure.
Sebastian
Yes, I now have the following clamav packages installed on the
Sorry,
That last paragraph should have said that I fixed freshclam on the 20th
May.
Not the 23rd.
So the sequence of events was the upgrade on the 19th; freshclam on the
20th;
then the first hang on the 21st.
Regards,
Jim Barber
--
To UNSUBSCRIBE, email to
15 matches
Mail list logo
