Too Many Log Files & No Clamav Updates

[tm-107]

I use Immunet 5.0.2.10301 and have 2 problems:

1. ClamAV updates won't install. The log file says
2016-08-31 16:07:20 - Log file initialized
2016-08-31 16:07:20 - INFO: custom freshclam return code: 56
2016-08-31 16:07:47 - ERROR: freshclam exit code 58
2016-08-31 16:07:47 - ERROR: failed to read stop event from pipe
2016-08-31 16:07:47 - Log file closed

 

edit: the files (main.cvd, daily.cvd and bytecode.cvd) were downloaded once after installing Immunet 5, but no updates since that.

2. There's a log rotation for the log files in C:\Program Files\Immunet\5.0.2\, thats okay.
But after only 7 days there are 12 files, each one has a size of >50MB and they can not be deleted.
Is there any way to decrease the amount of log files. For example only 10 files or only the files of the last 3 days ...

Sorry for my bad English. The school is already a few years ago ...

OS: Windows 7 Pro x64 SP1 german

Installed Antivirus Products: Immunet & MS Security Essentials

I recently used Immunet 3.x, but deinstalled it before installing Immunet 5.

[tm-107]

Sometimes it is another exit code:

 

2016-09-01 17:53:40 - Log file initialized

2016-09-01 17:53:40 - INFO: custom freshclam return code: 56

2016-09-01 17:54:09 - ERROR: freshclam exit code 59

2016-09-01 17:54:09 - ERROR: failed to read stop event from pipe

2016-09-01 17:54:09 - Log file closed

 

Have it now also tested on another computer -> there the updates do without error.

So i deinstalled and reinstalled Immunet 5 -> same problem

[ritchie58]

It looks like the signatures are being downloaded but are prevented from being installed on your Hard Drive. Have you created an "Exception Rule" for Immunet with MSE? If not, create an exception rule for Immunet's entire Program Files folder. Then reboot and run the updater again to see if that corrects the issue.

 

If you're not sure how to add permissions with MSE here's a Youtube video that explains how it's done. https://www.youtube.com/watch?v=4XQsRVYeMJc

Cheers, Ritchie...

[tm-107]

Yes, the "Exception Rule" was already created.

 

It looks like it is sometimes working (22:15):

2016-09-02 15:11:03 - Log file initialized
2016-09-02 15:11:03 - INFO: custom freshclam return code: 56
2016-09-02 15:11:33 - ERROR: freshclam exit code 59
2016-09-02 15:11:33 - ERROR: failed to read stop event from pipe
2016-09-02 15:11:33 - Log file closed
2016-09-02 16:11:36 - Log file initialized
2016-09-02 16:11:36 - INFO: custom freshclam return code: 56
2016-09-02 16:12:06 - ERROR: freshclam exit code 58
2016-09-02 16:12:06 - ERROR: failed to read stop event from pipe
2016-09-02 16:12:06 - Log file closed
2016-09-02 17:12:09 - Log file initialized
2016-09-02 17:12:09 - INFO: custom freshclam return code: 56
2016-09-02 17:12:38 - ERROR: freshclam exit code 58
2016-09-02 17:12:38 - ERROR: failed to read stop event from pipe
2016-09-02 17:12:38 - Log file closed
2016-09-02 18:12:41 - Log file initialized
2016-09-02 18:12:41 - INFO: custom freshclam return code: 56
2016-09-02 18:13:10 - ERROR: freshclam exit code 58
2016-09-02 18:13:10 - ERROR: failed to read stop event from pipe
2016-09-02 18:13:10 - Log file closed
2016-09-02 19:13:13 - Log file initialized
2016-09-02 19:13:13 - INFO: custom freshclam return code: 56
2016-09-02 19:13:45 - ERROR: freshclam exit code 59
2016-09-02 19:13:45 - Log file closed
2016-09-02 20:13:48 - Log file initialized
2016-09-02 20:13:48 - INFO: custom freshclam return code: 56
2016-09-02 20:14:20 - ERROR: freshclam exit code 58
2016-09-02 20:14:20 - ERROR: failed to read stop event from pipe
2016-09-02 20:14:20 - Log file closed
2016-09-02 21:14:23 - Log file initialized
2016-09-02 21:14:23 - INFO: custom freshclam return code: 56
2016-09-02 21:14:57 - ERROR: freshclam exit code 58
2016-09-02 21:14:57 - ERROR: failed to read stop event from pipe
2016-09-02 21:14:57 - Log file closed
2016-09-02 22:15:00 - Log file initialized
2016-09-02 22:15:00 - INFO: custom freshclam return code: 56
2016-09-02 22:16:03 - Log file closed
2016-09-02 23:16:21 - Log file initialized
2016-09-02 23:16:21 - INFO: custom freshclam return code: 56
2016-09-02 23:17:54 - ERROR: freshclam exit code 58
2016-09-02 23:17:54 - ERROR: failed to read stop event from pipe
2016-09-02 23:17:54 - Log file closed

But once a day is not what i want 

[ritchie58]

Good, glad to hear you already added permissions for Immunet with MSE. I thought that there might have been a conflict there. It's not a bad idea to add MSE's entire Program Files folder into Immunet's Exclusion List too if you haven't already. Thought I'd mention that.

 

Speaking from experience of using Immunet for years with the ClamAV module enabled, that sounds about right. ClamAV does usually get updated about once a day. So this really is normal behavior for the ClamAV module tm-107.

Regards, Ritchie...

[tm-107]

Of course, there isn't a new signature every hour.

But my daily.cld is from 02 August 2016 ... today we have August the 5th and my computer is online since more than 5 hours.

 

On another machine, i'm using ClamAV as standalone-service (for mail-scanning). So I can see, that there are updates every 1-6 hours.

Since Friday, there are almost 16 updates for the daily.cld.

 

edit:

Immunet also says, that there are updates available. But they couldn't be installed:

 

[ritchie58]

Come to think of it I've seen this kind of behavior myself in earlier builds. Sometimes just closing the updater window, waiting a few minutes, then running the updater again would solve this issue. It's not a bad idea to wait until Windows & your other 3rd party software & security apps are done looking for and installing updates before running Immunet's updater. That way Immunet's updater is not competing for resources at the same time. if this fails a simple re-boot is an option too. This can correct things if one of Immunet's process didn't launch properly at the first startup.

Don't forget that updates for the ClamAV module can be automatic if you have that setting turned on. That usually occurs about 5 or so minutes after Immunet has been launched at startup.

You needn't worry about the log files taking up too much HD space. Immunet will automatically trim those back if they reach a certain limit or time period.
 

Regards, Ritchie...