Jump to content
ataraxy

Agent.exe Constantly Writing To Disk After Scheduled Scan

Recommended Posts

Firstly Ced - thank you very much for the in-depth bug report!

 

Secondly, apologies to everyone else for my tardiness in responding to the forum posts lately. We've been very busy getting 3.0.2 ready for release, and we've finally gotten to a point where were confident enough to release a beta, which can be found here: http://forum.immunet.com/index.php?/topic/1104-immunet-302-beta-available/

 

The beta contains several updates that addressed the history.db (and other db files) which may resolve the disk hashing issues.

Share this post


Link to post
Share on other sites
Before then no such problem has been reported. One way, is to load a computer with an old version of Immunet, let's say from the autumn 2010 to see if the "agent.exe" problem will then appear.

 

You only need to go back to the version before v3.0.1.6056 to test this. It was when I updated to v3.0.1.6056 that the problems started.

 

Have any of the people with this problem tried the v3.02 beta yet?

Share this post


Link to post
Share on other sites

You only need to go back to the version before v3.0.1.6056 to test this. It was when I updated to v3.0.1.6056 that the problems started.

 

Have any of the people with this problem tried the v3.02 beta yet?

 

I just tried the latest beta. Did a flash scan. and now my disk is constantly spinning. I have two computers side by side. One is running Immunet 3.01.6112 and Trend Micro Titanium. Immnet doesn't seem to realize trend micro is installed, but I don't have the spinning problem. The other is running the latest Beta (3.02.6548), with Avast free edition, which immunet recognizes. It seems to have the spinning issue.

 

Actually, while I was typing this, it looks like the disk settled down. So it was maybe 20 minutes (had to register) of crazy disk activity.

Share this post


Link to post
Share on other sites

Firstly Ced - thank you very much for the in-depth bug report!

 

Secondly, apologies to everyone else for my tardiness in responding to the forum posts lately. We've been very busy getting 3.0.2 ready for release, and we've finally gotten to a point where were confident enough to release a beta, which can be found here: http://forum.immunet.com/index.php?/topic/1104-immunet-302-beta-available/

 

The beta contains several updates that addressed the history.db (and other db files) which may resolve the disk hashing issues.

 

Hello again,

 

It pleases me to know that this issue has not been overlooked. I might setup a cloned workstation soon, with nearly a million files and see if the latest Immunet release is good enough for what I need it to do. If it holds abuse for a week on that system, being monitored, having tons of background processes and services (think about mixing server services with workstation duties), then I would be willing to come back to Immunet for our workstations.

 

If it doesn't, I will be very disappointed by the failure to meet expectations, again, after 6 months. If that happens, I don't think I will bother with any other Immunet 3.x release. I will say it again: Immunet is a great piece of software, with a really great concept backing it up. But, like any other software, it needs to be able to do what I need it to do, in order for me to put it to use.

 

We'll see...

Share this post


Link to post
Share on other sites

Unfortunately, right after the first scan completed (which took a long time, as expected due to the monster file count) the problem manifested again. File historyex.db is locked in the usual write-stop-write-stop-... sequential access.

 

Same conditions, same errors, same types of write access.

 

So, no. It's not fixed, and for the looks of it it, it may never be until Immunet changes something fundamental in it's design for a better implementation. Sometimes, software design is the "bug". You can't patch something if it's fundamentally ill conceived, in my opinion...

Share this post


Link to post
Share on other sites

Just installed new version 3.0.5.7980..after a long hiatus! Same problem different day..constant disk hashing after installation and initial flash scan..Agent.exe keeps running. This problem has been going on for ever. I have seen many inquires regarding this problem. The program is totally useless..at least for me. Such a waste since the program that had such good beginnings. Maybe some day they will make an effort to fix it. Uninstalled!!

Davey..Win XP/SP3

 

 

 

 

Have any of the people who have had this problem tested v3.0.5.7980?

 

I don't have time to do this at the moment (no time to fix the problems if they occur), but I'll give this version a go when I get some free time

Share this post


Link to post
Share on other sites

Just installed new version 3.0.5.7980..after a long hiatus! Same problem different day..constant disk hashing after installation and initial flash scan..Agent.exe keeps running. This problem has been going on for ever. I have seen many inquires regarding this problem. The program is totally useless..at least for me. Such a waste since the program that had such good beginnings. Maybe some day they will make an effort to fix it. Uninstalled!!

Davey..Win XP/SP3

 

Thanks for the feedback Davey!

 

No need for me to test it out now.

Share this post


Link to post
Share on other sites

I'm having the same (or very similar) issue with Immunet (Plus) 3.0.6.8512.

 

I have a daily full scan scheduled at 2:00 AM, so that there should be enough time before I get back from work (typically after 5PM. When get home and start using the machine it's very slow and there is 'a lot' of disc activity by Agent.exe.

 

After I stop / restart the service (net stop immunetprotect) the machine almost immediately becomes normally responsive.

 

 

Regards,

Danilo

Share this post


Link to post
Share on other sites

Hi danci1973, here are some things that RobT has suggested that may help with system degradation and the hashing problem. I hope it helps. Here's the info: 1. Clear your Immunet history.db:

- Please note that once you complete this step you will not be able to restore anything that was previously quarantined.

- Download the attached "clear_db.zip", extract it, and run the clear_db.bat script.

or

- If you know your way around the cmd prompt you can clear the database files yourself:

net stop immunetprotect

del "c:\program files\immunet\*.db"

net start immunetprotect

 

2) Configure Immunet settings for best performance:

- These settings will make Immunet run as fast as possible, however you will be sacrificing some Security for extra performance.

- Open the Immunet interface (right click the Immunet icon in your system tray and select "Open Immunet 3.0"), click settings

- Turn Blocking Mode off (General Settings -> Protection -> Blocking Mode)

- Disable archive file scanning (Scan Settings -> Scan Archived Files and Scan Packed Files)

- Turn ClamAV off (General Settings -> Clam AV Detection Engine -> Enable ClamAV Engine and Allow Definition Updates)

 

3) Add exclusions to prevent dual and circular scanning:

- If you have any other AV products installed on the computer ensure you have added exclusions to Immunet to prevent scanning them.

- Vice-versa, ensure you have added an exclusion for C:\Program Files\Immunet to any other other AV products you have to prevent them from scanning Immunet.

- If you run any continious backup software, ensure Immunet is excluded from scanning it, and ensure it does not back up C:\Program Files\Immunet

Attached File(s)

zip.gif clear_db.zip (778bytes) If you continue to have problems please submit a SDT Report.

Share this post


Link to post
Share on other sites

I tried no. 1 and no. 2, but it didn't make much of difference.

 

No. 3 is a bit trickier. I completely forgot that I had to install 'ISS Proventia Desktop' because it's required by one of my employers in relation with Cisco VPN client - I'm not allowed to connect without it. I added it's folder 'I:\Program Files\ISS\' to Immunet's exclusion list.

 

Unfortunately the ISS Proventia version I've been given and have to use is locked-down, so I can't change any settings. I can stop it's agent and exit the 'console' - which I did so we'll see how it goes tomorrow.

 

 

 

Regards,

 

Danilo

Share this post


Link to post
Share on other sites

Hi Danilo, if that ISS Proventia software uses Temp files while writing to disk that could cause agent.exe to scan those files while they're being created. That was a good idea to exclude that software's Program Files folder. Let us know how it goes but like I said in the other thread, feel free to send in a SDT Report if you continue to experience issues. Best wishes, Ritchie...

Share this post


Link to post
Share on other sites

Unfortunately, there's no change. When I got back from work there was Agent.exe again with over 50MB/s of disk activity. ISS Proventia is stopped / disabled, so it's probably not the cause.

 

I ran the SDT (before stopping Immunet service) and sent the files via email (Subject is the same as thread title).

 

 

Regards,

 

Danilo

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...