I was having an issue connecting remotely to our client's web server this morning, but after trying multiple times finally managed to get onto it.
Running the TOP command I see that Veeam is running 11 instances, which I can understand because it has 12 cores, but what I can't understand is why the backup was done last night (11 hours ago) and finished successfully and yet it appears to be running near or above 100% CPU? Any idea why? Is there a command I can use to find out what it is doing? Has something gone wrong and I need to kill it?
I ended up having to run sudo killall veeam as the server was running like it was on it's last legs. I would still like to know why this happened and how I can stop this from occurring again.
//edit: Interestingly, one CPU is now running at 101.0% by Veeam after completing a manual backup.
I've just run sudo killall veeam again, opening Veeam Agent and then closing it (and not even doing a backup!) will make the CPU go to 101% and sit there constantly. 3 hours later it is still sitting on 101%.
I've been trying different things and it only happens after closing the GUI interface. No idea why.
vmniels wrote:Alex, this behaviour isn't normal. Could you please contact support for further investigation?
How do I open a ticket for a client that uses the free Veeam Agent for Linux? When I try to open a case in the Veeam Support website it says "Select a customer".
//edit: I've given Veeam a call and opened a ticket that way. I didn't want to bother anyone.
Hi Alex,
I am running with the latest Veeam agent for linux on Ubuntu 18 and i am experiencing the exact same issue; one of my CPU cores is running at max all the time even if at idle status; did you get a solution for this issue ?
