Your question, your audience. Choose who sees your identity—and your question—with question security.
ESXi 5.0 repeating event user root logged in/out
Hi,
I have been dealing with ESXi hosts having problems with constantly repeating root logged in / logged out event. Every 10 seconds these events repeat:
I always managed to drain it down to some monitoring software, which was guilty for these logs, but this time I cannot find the real suspect.
I have VEEAM monitoring installed, so I killed ALL Veeam services.
After that, I only see repeating every 10 seconds:
Ok, there must be something else.
I monitor TCP connections and I only see my Vsphere CLIENT connected to remote port 443, nothing else. If I close vSphere Client, all those 443 port TCP connections go away.
But I was using it fine for years now...and all of the sudden...here we have this annoying event again.
I am frustrated because this repeating event pushes out the IMPORTANT waringn about storage deterioration problem, which I hunt for - but if I have just those "root logged out" events all over, I cannot watch for realy importan event.
Any idea?
I have been dealing with ESXi hosts having problems with constantly repeating root logged in / logged out event. Every 10 seconds these events repeat:
User root@1.2.3.4 logged in 23.12.2012 23:29:59
User root logged out 23.12.2012 23:30:16
I always managed to drain it down to some monitoring software, which was guilty for these logs, but this time I cannot find the real suspect.
I have VEEAM monitoring installed, so I killed ALL Veeam services.
After that, I only see repeating every 10 seconds:
User root logged out 23.12.2012 23:31:26
Ok, there must be something else.
I monitor TCP connections and I only see my Vsphere CLIENT connected to remote port 443, nothing else. If I close vSphere Client, all those 443 port TCP connections go away.
But I was using it fine for years now...and all of the sudden...here we have this annoying event again.
I am frustrated because this repeating event pushes out the IMPORTANT waringn about storage deterioration problem, which I hunt for - but if I have just those "root logged out" events all over, I cannot watch for realy importan event.
Any idea?
Asked:
-
3
1 Solution
Hmmm...
It all seems that monitoring behavior is weird.
I took some time to reboot host several times:
TEST "no monitors"
When ESXi rebooted without any monitoring software being connected to it, it was all fine.
TEST "veeam"
When ESXi rebooted AND there was VEEAM monitoring on remote server turned ON, still there is no issue, all normal.
TEST "orchestrator"
Well, with orchestrator and whole VMware suite, it was all the different story. As soon as my remote server has Orchestrator and surrounding services running, the "root logged in/out" problem begun immediately!
Weird thing is that even if I shut down ALL orchestrator and VMware* and vSphere* services on remote machine, the problem did not disappear. Actually it went down to show only "root logged out", but still filling event log.
Could not stop it.... except of rebooting host.
It all seems that monitoring behavior is weird.
I took some time to reboot host several times:
TEST "no monitors"
When ESXi rebooted without any monitoring software being connected to it, it was all fine.
TEST "veeam"
When ESXi rebooted AND there was VEEAM monitoring on remote server turned ON, still there is no issue, all normal.
TEST "orchestrator"
Well, with orchestrator and whole VMware suite, it was all the different story. As soon as my remote server has Orchestrator and surrounding services running, the "root logged in/out" problem begun immediately!
Weird thing is that even if I shut down ALL orchestrator and VMware* and vSphere* services on remote machine, the problem did not disappear. Actually it went down to show only "root logged out", but still filling event log.
Could not stop it.... except of rebooting host.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
After I restart host Management Agents, this issue stops...
...BUT I loose hardware status in vSphere client.
Seems like some vendor-specific MIB/CIM is not up to date.