Sure the VM is shut down or is it killed? The later stems probably form resource exhaustion.I have a VM with Proxmox Backup Server which is linked with other severs (thanks to storage). Sometimes without knowing why, my VM shutdown what is dangerous !
That's the same when its killed. Please post the syslog or journal of the VM from the last time it happend.Yes I'm sure it is shut down. Every time its happens, I must start the VM by hand
Hello,That's the same when its killed. Please post the syslog or journal of the VM from the last time it happend.
This morning my VM shutdowns 3 times and when I read the log, I didn't see a connection attempt. So I would like to know where does the problem come from, because its very dangerous.I can't see much from the snippet (text files are preferred though). And anything in the logs on the PVE host?
If the PBS isn't under a subscription, then best replace the enterprise repository with the no-subscription to get all the updates of PBS.
Now I have this message in log "Could not generate persistent MAC address for... : No such file or directory"This morning my VM shutdowns 3 times and when I read the log, I didn't see a connection attempt. So I would like to know where does the problem come from, because its very dangerous.
Thanks
Did you check the log files on the PVE host?This morning my VM shutdowns 3 times and when I read the log, I didn't see a connection attempt. So I would like to know where does the problem come from, because its very dangerous.
yes, its the sameDid you check the log files on the PVE host?
Did it ! So after, what I have to do ?As I said earlier, check the resources of the PVE node. A good tool for it is atop.
What does atop show? By default it tracks resource usage in a 10min interval. You can then replay the data file and analyze the state of the affair.Did it ! So after, what I have to do ?
What does atop show? By default it tracks resource usage in a 10min interval. You can then replay the data file and analyze the state of the affair.
Atop shows the resource usage, even down to a process level. When there are to many resources consumed (over-committed) the OOM killer will kick in and kill the process that uses up a huge part of the resources.Sorry man, i don't understand what atop shows and in what this is shows why pbs shutdown
Can I do a "atop" to see whats happen two days ago for example ?Atop shows the resource usage, even down to a process level. When there are to many resources consumed (over-committed) the OOM killer will kick in and kill the process that uses up a huge part of the resources.
If it was already running two days ago, then you can load the old log (/var/lib/atop/).Can I do a "atop" to see whats happen two days ago for example ?
If I do /var/lib/atop/ its doesn't worksIf it was already running two days ago, then you can load the old log (/var/lib/atop/).
Best read up on atop, it's not the lightest tool.If I do /var/lib/atop/ its doesn't works
man atop