Search results

Stand alone. Didnt look at IO at the time but heres maximums. The spike happened on 8/20 but looks normal around 8/22 and 8/27 where status update took longer than normal. Heres the disk IO of VM 137 which I originally reported.

I observed it for about an hour today and didnt see it happen so maybe self resolved. Logs from last week: Aug 22 03:03:33 proxmox systemd[1]: Reloading PVE Status Daemon. Aug 22 03:03:34 proxmox pvestatd[1597922]: send HUP to 3260 Aug 22 03:03:34 proxmox pvestatd[3260]: received signal HUP...

I havent had time to monitor it again but on monday or tuesday im going to watch for it again and check the logs fiona mentioned. I looked at syslog and journalctl yesterday but didnt see any reference to qm 139

Any log I can look at next time this happens?

VMs are stored locally. I only store back ups on NFS. BigRAID and OtherRAID are a raid 10 and raid 5 array on a dell r720 with LSI 9200-8e raid card. MediaRAID is a MD1200 connected to the r720 via sas cables and a LSI SAS 9211-8i. None of the drives show health errors on idrac. pvesm...

I updated in June. Ever since I updated, now randomly the web page will show random guests as status unknown, and it shows them this way for an undetermined period of time. Sometimes its 5 seconds sometimes its 2 minutes. It doesn't happen to specific guests it happens to random guests at random...

***LVM was full. I missed that. I am creating a new Ubuntu container, doing a release upgrade on it and then rebooting. After I reboot the container, it fails to start and gives the error in the title. I have deleted the container and tried again. I tried privielged and unprivileged. Both...