Jump to content

Log Files Filling Up C Drive


Recommended Posts

Hello

 

I had a client contact me yesterday morning regarding the c:drive on their server having 0 space available.  I Connected remote, saw the same, proceeded to allocate additional space on the vm server.  Added 45 Gb, verified this in windows explorer, thought all was well.  Get up this morning and the same client contacting me again with the same issue.  In 12 hours the additional 45Gb was down to 0 and it appears to be log files created by CLAMAV.  I cannot delete these files or anything.  This has crippled their server and their production entirely.  Please help.

 

D

Link to comment
Share on other sites

Hi guys, if one person reported this you could write it off as an isolated anomalous incident. If three people report the same thing in less than 24 hours than I have to extrapolate that a new bug has reared it's ugly head! Could you and Alex please submit a Diagnostic Tool Report directly to Support. Here is a link to a FAQ topic that outlines how to create & submit an effective support request using the SDT report and the other pertinent data. http://support.immunet.com/index.php?/topic/1672-how-do-i-submit-a-support-diagnostic-tool-report/

 

Also, I'll see to it that Support is aware of this situation.

Best Wishes, Ritchie...

Link to comment
Share on other sites

Hi all,

 

We are currently looking into the log file issue, and agree that it is not acceptable.

 

@Adrenaline - the sfc.exe.log files are expected. These log files are capped at 50 MB each, and we keep only a maximum of 10 log files. You should see the oldest log file being deleted as the current sfc.exe.log file reaches 50 MB and is rotated.

Link to comment
Share on other sites

Hey all, I have been experiencing the same issue since 2 days ago as well. I have multiple log files in the CLAMAV folder that are each taking up about 120,000 kb of space all adding to roughly 800 GB. I've tried uninstalling Immunet with no success and tried deleting the individual files with no success either. It happened on two desktops connected to the same network. The desktops are required for business processes and I want to avoid paying someone to fix this issue. If someone has found a fix can you please direct me to the solution?

 

Thanks,

 

Mario 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...