Search results

Greetings I've been using Proxmox for years, mainly form CTs, with a few VMs. Recently I started developing for Docker, so I created various VMs and CTs for testing. The last VM I created is problematic: when it's running, the whole machine (host + other guests) are slow and show messages like...

Very good point. Now a similar error appears: utils - utils.c:safe_mount:1187 - No such file or directory - Failed to mount "/dev/pts/11" onto "/dev/console" however the boot process goes on, so I assume it just happens that is it a non-blocking error happening just before the actual...

Thanks a lot for your help. Maybe it would be worth it to add it to the documentation because the error message is really unrelated and makes it very hard to find the error.

OK I got it: the bridge device on the host wasn't created... the error message is completely misleading :(

While chatting with a co-worker, we tried to remove the net devices, and the CTs started... if I add the net devices again, the same error happens...

# pct start 198 Job for pve-container@198.service failed because the control process exited with error code. See "systemctl status pve-container@198.service" and "journalctl -xe" for details. command 'systemctl start pve-container@198' failed: exit code 1 # lxc-start -F -f...

Also, ALL old vz CTs show the same behavior when imported in the latest Proxmox.

Thanks for your answer. I forgo t to mention I already removed the content from /etc/fstab in the guest. I found no mention of pts/8 anywhere in the guest. While googling I found mentions of changing the ownership of /dev/pts of the host, but I thought it very weird and didn't risk to try it...

BTW I tried adding `unprivileged: 0` to the config file, it doesn't change.

Greetings I'm trying to migrate an old Proxmox 3 VZ container to LXC. The import process works as documented; however, when trying to start it, it does't work. I tried to run it manually with `lxc-start` and got this error: utils - utils.c:safe_mount:1187 - No such file or directory - Failed...

Thanks for the answer. The error message was indeed unrelated, the actual problem is that a zfs snapshot referred to in Proxmox' list is missing... which is very disturbing. It's still in the GUI (since it's in the config file in /etc/pve), but missing from "zfs list...". Maybe it would be a...

Here is the content of /var/log/pve/replicate/141-0: 2018-12-31 16:21:01 141-0: start replication job 2018-12-31 16:21:01 141-0: guest => VM 141, running => 10901 2018-12-31 16:21:01 141-0: volumes => ct_A:vm-141-disk-1,ct_A:vm-141-state-After_install 2018-12-31 16:21:01 141-0: create snapshot...

Greetings I'm trying to run a replication between two nodes and get this weird error: 2018-12-28 17:17:01 141-0: start replication job 2018-12-28 17:17:01 141-0: guest => VM 141, running => 10901 2018-12-28 17:17:01 141-0: volumes => ct_A:vm-141-disk-1,ct_A:vm-141-state-After_install...

OK sorry I thought shared was common to all storage. I was investigating a problem with replication, I have an error message: () Replication Log 2018-12-28 17:13:01 114-0: start replication job 2018-12-28 17:13:01 114-0: guest => CT 114, running => 1 2018-12-28 17:13:01 114-0: volumes =>...

Thanks for your answer. $ pveversion -v proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve) pve-manager: 5.3-6 (running version: 5.3-6/37b3c8df) pve-kernel-4.15: 5.2-12 pve-kernel-4.15.18-9-pve: 4.15.18-30 pve-kernel-4.15.18-7-pve: 4.15.18-27 pve-kernel-4.15.18-5-pve: 4.15.18-24...

Greeting I can't figure out how to set/unset the flag parameter with pvesm: # pvesm set POOL --shared 1 (ok, the word "shared" with nothing behind is added to storage.cfg) # pvesm set POOL --shared 0 file /etc/pve/storage.cfg line 2 (section 'POOL') - unable to parse value of 'shared'...

Greetings I have 4 machines in the same hosting company, all running Proxmox, operating for a few years (with updates). 2 of them have been "bound" with Proxmox clustering for a quite a while, with a few problems over the years. After a crash, they now are "orphaned". What do you think should...

I finally got the key back by allowing writing to /etc/pve with: pmxcfs -l however, even after a reboot, the node doesn't rejoin the cluster.

I tried to get quorum like that: pvecm expected 1 but get this error: Cannot initialize CMAP service and service pve-cluster status returns active but with errors: pmxcfs[19604]: [dcdb] crit: cpg_initialize failed: 2 pmxcfs[19604]: [status] crit: cpg_initialize failed: 2

Greetings I have a 2-nodes cluster which was working well for quite a while. This morning, I deleted `/etc/pve/local/pve-ssl.pem` by mistake. I have a backup, but if I try to write this file I get a 'Permission denied' error. How can I write into this file? Thanks in advance Regards