SEP services fail to start (Hyper-V guest OS)
Hello,
I have several machines which I noticed today weren't getting Virus Defintions, I'm showing the servers as last checking in during our patching window (or later that night).
The information I have is as follows:
- Each Server is a Guest OS on a Hyper-V Cluster.
- The servers have two Errors in the System Event Log (see attachments).
- Most servers have the errors during the patching window. While some have it later that night.
- All Services are set to start automatically, but aren't started.
- The services startup just fine when I run "start smc" in the command prompt.
I believe the fact that most of the errors in the event logs are during the patching window it looks like the services didn't start up during the reboot from patching. For those that have them later in the night, I believe this is from a Hyper-V node failure (resulting in a failover of Guest OSes from one Node to another).
Even more concerning is that I haven't received any emails on this even though i should receive emails when definitions are 7 days or more out of date according to my notifications in SEPM.
Has anyone seen anything like this before or would they know why something like this would happen on these systems.
Comments
hi
have you excluded these?
http://www.symantec.com/business/support/index?page=content&id=TECH133846&locale=en_US
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
I have seen this happen in
I have seen this happen in our environment several times - particularly after patching.
What I suspect is that there is a bit of a race for resources with virtual machines (I've noticed it's worse on smaller, less grunty virtual environments).
If many of the systems are rebooting at the same time, SEP misses out with the timing and therefore does not start.
Often I would see in the console a machine hadn't updated for about a month and jump on, open the GUI and get the "Symantec Management Client Service is not started. Would you like to start it now?" message.
Since beefing up some of the virtual environment, I haven't noticed this problem as much.
That's not an official line, just my experience :)
Regards,
Chris Bulovic
Chris, That sounds identical
Chris,
That sounds identical to my issue; though I would consider our environment to be some what beefy.
These servers only get rebooted during patching (unless something bad or non-routine happens), and the window we use to do that is only a few hours, during which most of those servers are rebooting at the same time. So it sounds
Just out of curiosity what did you do to do to beef up your environment? I'm assuming you're talking about increasing the physical resources of the actual Hyper-V environment.
I can't imagine there are not more people having this same issue and that there isn't anything directly from Symantec to address this. :-(
Also Rafeeq, I'm referring to the guest OS Servers, not the actual Hyper-V servers (They do not have SEP yet).
-Thanks
Curtiplas
Well this is no longer an
Well this is no longer an issue for us, we're moving back to VM Ware, so far it seems to work better on a hypervisor than the Hyper-V Host/Guest system...
Would you like to reply?
Login or Register to post your comment.