- Joined
- Jan 7, 2018
- Messages
- 41
- Reaction score
- 2
I have a client with a brand new install (120+) users running on VMware v6.5, everything has been going well until recently the CPU in the VM spikes to 100% utilization and stays there. Of course this knocks all of the users off the system. This has happened twice this week around the same time frame each both days.
I see this CRON job kick off several times prior to the CPU spike:
CRON[31799]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Any ideas what that CRON is doing?
When the CPU locks up this is what the log file shows that sticks out:
"NULNULNULNULNULNULNULNULNULNULNUL" this repeats about (50) more times...
I don't see anything obvious in the log files. Has anyone else see anything like this? Or is this more of a Debian OS issue? Generally the CPU hovers around 3-5% utilization and there is 4G of RAM with roughly 20% utilization there.
I have other clients running the same basic config with no issues. Any and all help and feedback much appreciated.
I see this CRON job kick off several times prior to the CPU spike:
CRON[31799]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Any ideas what that CRON is doing?
When the CPU locks up this is what the log file shows that sticks out:
"NULNULNULNULNULNULNULNULNULNULNUL" this repeats about (50) more times...
I don't see anything obvious in the log files. Has anyone else see anything like this? Or is this more of a Debian OS issue? Generally the CPU hovers around 3-5% utilization and there is 4G of RAM with roughly 20% utilization there.
I have other clients running the same basic config with no issues. Any and all help and feedback much appreciated.