Search results

Ok thank you. Any idea where to find logs on Proxmox server that might explain what happened to make the VM crash? Also, the storage server backing the VMs does not seem to be heavily utilized except for one 60% utilization spike - but maybe that would do it..(https://imgur.com/a/U9oaFvH) ...

Hi - just a follow up. A second VM was discovered crashed today as well. Sorry, only a screendump of the console.

Hi, Is there a way to get more info on the crash? The screenshot is all that was on the console. I couldn't page up/down or login to the VM. I grep'd for 'Task' in the logs after a reboot of the VM but nothing turned up. pveversion output below. Thanks # pveversion -v proxmox-ve: 5.2-2...

Since upgrading to 5.2, I've been getting VM crashes intermittently. They don't seem to be related to any one hypervisor and I can't actually tell what's wrong from the console message (below). Anyone have any ideas where to look for the problem? Seems like we used to get these years ago when...

ramza - thanks for the script. works great. For anyone else reading this, make sure NODE= matches your proxmox node name in the web UI. I initially had NODE set to the FQDN of the Proxmox server, which is not correct in my case. My Proxmox node is just the short hostname. After making that...

Hello, Anyone know where to look for this problem? It was happening on two hosts I recently upgraded to 5.2. Today it seems only one. 3rd party subscription vendor says it might be permissions on /etc/pve but I am running the update as root from the shell and have read access to everything under...

Ok, thanks for the info. We bought our licenses from a 3rd party so as I understand, we dont actually have an account with shop.maurer-it.com. Would there be any possible way to integrate that functionality for 3rd party licenses (or maybe I'm completely mistaken)? It would be so handy.

Looks like the BIOS update fixed it. It reset the boot order, so after selecting the correct volume, Proxmox/Grub booted right up. PS: after booting, noticed my subscription is invalid now. Is that something I'll have to be aware of anytime I update BIOS firmware?

root fs is ext4 over LVM on top of a raid 1. BIOS details are here: https://postimg.cc/image/cu7d87t1j/ Areca here : https://postimg.cc/image/n49s7f8mf/ I booted with the installer Rescue boot yesterday and was able to get into the system. I installed all the latest patches...

I've installed Proxmox 5.2 on a Supermico X10DRI-LN4 board and Xeon 2637 v3 CPUS. Areca raid controller with a sata array as the boot volume. Have installed twice. After the grub menu disappears, I get: Loading Linux 4.15.17-1-pve... Loading initial ramdisk... But no boot actually happens...

We wanted to go with Maurer IT from the start but the available payment options apparently don't work for our billing department. Proxmox is great, we love it, but I'm concerned these constant license issues will be a detriment. I understand it's not your problem, but in a way it kinda is. Our...

Hello, Is there some tip for reinstalling Proxmox that will not mess up the status of the Subscription Key? I've been waiting (so far) 12 hours for the "Invalid Server ID" status to clear (two support tickets with a third party license provider) so I can begin provisioning the server. Is there...

No hardware errors that I know of. pve-data is on Areca HW RAID1 with a hotspare and battery backup. pve-data is only used locally on each Proxmox node. it is not shared over any network filesystem. We have Infiniband backend serving gluster and iSCSI for virtual machines. When storage must...

I upgraded from 4.4 to 5.2 recently and noticed my /var/lib/vz ext4 filesystem didn't survive the upgrade. Is this a known issue with Debian 9 or something? On 4.4 this system was rebooted, and fsck'd, practically every weekend for either Proxmox or SAN upgrades so I'm wondering if the error is...

Thanks for taking the time to look at the post. It seems to be OK for the past couple days now. I'll have to check it after the weekend and see if it's tanked again. `shm` is there and properly linked to /run/shm which is 32G in size (via df). I just don't see anything amiss yet.

That would be disastrous. I'd like to get this thread back OT however.. Since rsync didn't touch /dev in the container, any thoughts why it's becoming full? On other systems (Virtuals) /dev is several gigabytes in size. Some up to 32G. On the proxmox containers it is 492K. That's quite small...

Do you mean to say rsync will exclude a file such as dev.txt if --exclude=dev is used? It seems to work differently than that. At least the way I've always used it (for excluding root directory entries). # dev directory, and regular files containing 'dev' localhost $ find src -ls 131086 4...

I don't understand. -x instructs rsync not to cross filesystem boundaries so if you have separate partitions for usr, tmp, home and var this may not be useful. Are you meaning to '--exclude=dev' in the rsync command?

Decided to check my second "cloned" container on a different hypervisor. This one has a full /dev also.. hrm. This host was done from the rsync link above as well. Some CLI from the second container. 492K is not much but I can't tell where the space is being used. # df -mh Filesystem...

Thanks @wbumiller , just getting back to this.. /dev/ full again today. All of the CLI pastes abover are from inside the container. I see those *pve2* files exist on the hypervisor (in /dev/shm) as well. Are they created inside the container also? I should point out also that this container was...