Jump to content

Recommended Posts

I'm experiencing some strange behavior on several of my windows servers.

 

I have an installation with a single full scan schedule every day at 3AM.  I noticed this on one of my servers this morning when it was after 9AM, and the scan was still running.  BUT it had only been running for 43 minutes.  I let the scan finish and then noticed that it started scanning again almost immediately after it had finished.

 

I clicked the stop scan button, and waited... within a minute another scan started.  I stopped that, and again another started within about a minute.  I could probably play this game all day, but alas I was getting bored.  SO, I removed the schedule.

 

That seems to have stopped it.  I've rescheduled the 3AM scan, so we'll see if this happens again.

 

I've only noticed this on a few of my servers, but I'm going to go check the rest of them to see if any others are showing this same issue.  Let me know if you want any debugging information.

 

I uploaded a shot of my scan history on another box that was exhibiting the same issue.

 

 

post-39787-0-89908500-1520272170_thumb.png

Share this post


Link to post
Share on other sites

This is strange, is this all on one specific operating system? (Windows 2018 R2?) or is it various operating systems?

Have you rebooted any of these machines to see if it "auto starts" the scheduled scan again?

 

The date and time is set correctly on the machine(s)?

Share this post


Link to post
Share on other sites

All the servers that I've identified so far are Windows Server 2012 R2 VM's; All have been rebooted many times since the schedule was set, which was when I installed the first version of Immunet (6.0.0 I believe).  They have been upgraded several times to keep them up-to-date.  T

 

he date and time are correct (set through the domain).

 

I noticed the issue because of high memory usage on these 4 specific servers during normal business hours.  Last time it happened I increased the amount of RAM on all 4 servers (and rebooted).  The issue seemed to go away, but obviously came back.

Share this post


Link to post
Share on other sites

Wow, that is really weird! I've never heard of "anyone" encountering this anomalous behavior before! Did Immunet create multiple scheduled scans with Windows TaskScheduler for some unknown reason?

 

If I ran into this situation that's the first thing I would have checked.
 

Robert, since the deletion of the scheduled scans seemed to have solved the problem how is the new scheduled scans behaving now? If you see the same or similar behavior on any of the machines by all means send Wookiee a SDT report via email per machine affected. http://support.immunet.com/index.php?/topic/1672-how-do-i-submit-a-support-diagnostic-tool-report/

 

Regards, Ritchie...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×