Search results

Hi, We just created a new cluster using Proxmox VE 4.3. One node out of 11 randomly shows it's offline in the GUI. Here's the proxmox version information. root@ProxmoxLV4:~# pveversion -v proxmox-ve: 4.3-66 (running kernel: 4.4.19-1-pve) pve-manager: 4.3-1 (running version: 4.3-1/e7cdc165)...

Thanks for replying Wolfgang. Would ypuind shRingntje steps with me. We don't have any vms yet on these hosts. Or if it's easier I can remove these servers from the cluster change their hostnames and readd them.

Hi Everyone, We just created a new cluster. Unfortunately we decided after the fact that we wanted to change the names of the servers to be more descriptive. Our servers are currently named Proxmox1 through Proxmox5. Is it possible to change Proxmox1 to ProxmoxSSD1 for example? We're mainly...

Thank you very much. I added the root delay to the GRUB_CMDLINE and now it works correctly. For anyone else who experiences the issue, here's the full line: GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=10" Here's the output of /proc/cmdline: # cat /proc/cmdline...

FYI I tried appending rootdelay=10 to /etc/default/grub, and the problem continued. I then changed rootdelay=10 to rootdelay=30 still with no luck. I ran update-grub after each change. Should that string go in a different file?

We're seeing this issue as well on a fresh 4.2 install. Anyone know of a permanent fix pveversion -v proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve) pve-manager: 4.2-2 (running version: 4.2-2/725d76f0) pve-kernel-4.4.6-1-pve: 4.4.6-48 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1...

I can confirm that this has been fixed in Proxmox VE 4.2

Can you post the output of ls -alh /etc/pve/priv/cep? Also if you looking the ceph-mon log it may give you some clues.

Hi Fabian, Running setfacl -b -R / then rebooting the container fixed the issue. Thanks for pointing out the bugs.

I opened a ticket yesterday. I got a few emails from Friedrich last night, but haven't heard from anyone in 24 hours. Here's the ticket number: IRW-893-90850

Hi Fabian, I just created another container based off a backup. I couldn't see where I could set the acl option in the gui, so I edited it in the config file before turning the container on. And I'm still having the same problem. We have maintenance subscriptions on all of our servers. Is it...

Thank you so much for the detailed response. I just tried setting acl=0 in the config file, but I'm still experiencing the same errors. Is this something that had to be set when the container was originally restored from a backup? Also I don't see where I can set that in the gui.

Also. I just installed created an LXC based on this same template on Proxmox 4.0 and it's working perfectly. Here's the info on the working proxmox server. root@ProxmoxNJ1:~# pveversion -v proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve) pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0)...

Here you go. root@proxmoxnj2:~# cat /etc/pve/lxc/100.conf arch: amd64 cpulimit: 1 cpuunits: 1024 hostname: mcintirere.hivepbx.com memory: 512 net0: bridge=vmbr0,gw=10.3.0.1,hwaddr=36:35:61:63:30:39,ip=10.3.0.50/21,name=eth0,type=veth onboot: 0 ostype: centos rootfs...

Upgraded to the latest versions. root@proxmoxnj1:~# pveversion -v proxmox-ve: 4.1-41 (running kernel: 4.2.8-1-pve) pve-manager: 4.1-22 (running version: 4.1-22/aca130cf) pve-kernel-4.2.6-1-pve: 4.2.6-36 pve-kernel-4.2.8-1-pve: 4.2.8-41 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1...

Here you go. Thanks for your help. root@proxmoxnj1:~# cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian jessie main contrib # security updates deb http://security.debian.org jessie/updates main contrib root@proxmoxnj1:~# cat /etc/apt/sources.list.d/pve-enterprise.list deb...

We haven't activated the enterprise licenses yet on these servers because they just came out of our lab. Could the fix for this problem only be in the commercial repo?

Thanks Fabian. But my repo's are set up correctly and I just did an apt-get update and an apt-get dist-upgrade less than an hour ago. Then I rebooted the hosts. I'm not sure what else I can do to upgrade these servers.

I'm on the latest version and the problem persists. root@proxmoxnj2:~# pveversion -v proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4) pve-kernel-4.2.6-1-pve: 4.2.6-26 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 0.17.2-1 pve-cluster...

I'm experiencing this same problem with LXC containers on ceph. root@proxmoxnj2:~# pveversion -v proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4) pve-kernel-4.2.6-1-pve: 4.2.6-26 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 0.17.2-1...