Search results

@UdoB Sorry, my bad, actually the second node was still up when I was issuing the command. The command works when the second node is down. Please never mind my comment.

@UdoB pvecm expected 1 doesn't seem to work anymore :( It used to, though... Any idea why? $ pvecm expected 1 Unable to set expected votes: CS_ERR_INVALID_PARAM

@LnxBil Thanks, I will give it a shot then!

@LnxBil Good point, thanks! I did have a look at the documentation that describes installing a QDevice. Is it really that easy? I found other guides, as well, that are way more complicated than installing an empty PVE node. If the below is all what I need then this could run in a NAS Docker...

@fiona Got it! The other node is down due to a hardware fault, so I can be sure that this happens only on the second node right now. Regarding the QDevice, does it make sense to install a QDevice in a VM on each node independently? This way there would be 4 nodes: 2 PVE and 2 QDevices, where if...

@fiona @LnxBil One possible solution would be setting the expected number of nodes to one. In that case I can write to the filesystem. Are there any drawbacks of this? Before: - no quorum - cannot create snapshot Action: - pvecm expected 1 After: - quorum achieved - can create...

@LnxBil I have a script set up to solve the quorum problem (https://gitlab.rickelobe.com/virtualiztion/proxmox-2n-ha-monitor) which has been working great. I cannot (at this moment) afford a third hardware and I don't want to fake the quorum with a third Raspberry PI machine like some people do...

I'm trying to create a snapshot of my VM ID=101 and I'm getting a Permission denied message: WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools...

@dcsapak Confirming that the directory structure has changed indeed. The PVE 6 to 7 migration script tells that: $ pve6to7 ... WARN: CIFS credentials '/etc/pve/priv/ProxmoxBackup.cred' will be moved to '/etc/pve/priv/storage/ProxmoxBackup.pw' during the update WARN: CIFS credentials...

@dcsapak Ok, the source code you shared with me (https://git.proxmox.com/?p=pve-stor...025957dc6791c05d29b1;hb=refs/heads/master#l72) brought my attention to one thing: 31 sub cifs_cred_file_name { 32 my ($storeid) = @_; 33 return "/etc/pve/priv/storage/${storeid}.pw"; 34 } The...

@dcsapak Any idea how can I debug the inactive CIFS shares? I can't make them work and this way I can't backup any of my VMs :( I have no idea what's wrong. I can easily mount the NAS share manually on the affected node: mkdir /mnt/x mount //192.168.x.x/ProxmoxBackup /mnt/x -t cifs -o...

@dcsapak Ok, this hasn't been the most relaxing moment of my life but I was able to return to field #1, both nodes are working and I was able to edit the /etc/pve/storage.cfs file on the 'master' node. Here are my findings: - no smbversion: works on node1, does not work on node 2 -...

@dcsapak Ok, I managed to get my second node up thanks to this post: https://forum.proxmox.com/threads/unable-to-load-access-control-list-connection-refused.72245/page-2 I had to rename /etc/pve to something else and then reboot the machine. It means that editing /etc/pve/storage.cfs on the...

Ok, I managed to resolve my problem thanks to this post: https://forum.proxmox.com/threads/unable-to-load-access-control-list-connection-refused.72245/page-2 TL;DR I had to remove the /etc/pve folder on my second node (as storage.cfs config got stuck in there and paralyzed the entire system)...

One of the two nodes of my Proxmox cluster won't start after reboot. This is what I tried: $ pvecm status ipcc_send_rec[1] failed: Connection refused ipcc_send_rec[2] failed: Connection refused ipcc_send_rec[3] failed: Connection refused Unable to load access control list: Connection refused...

I'm getting the same 'Connection refused' error on: Linux proxmox-2 5.11.22-4-pve #1 SMP PVE 5.11.22-8 (Fri, 27 Aug 2021 11:51:34 +0200) x86_64 GNU/Linux PVE does not start, cannot do anything with it :(

@galphanet Have you solved this issue? How?

@dcsapak I followed the documentation here: https://pve.proxmox.com/wiki/Storage:_CIFS and edited the /etc/pve/storage.cfs file by adding the following to my CIFS shares: smbversion 3.0 The I restarted the machine and I got into a much bigger trouble: PVE doesn't start. Even when reverted...

@dcsapak Good idea, may I ask you where can I configure the SMB version? The Help button suggests there should be a SMB version field but I don't see one in the Edit window:

@dcsapak Very good catch, they aren't. uname-a: node-1: Linux proxmox 5.4.119-1-pve #1 SMP PVE 5.4.119-1 (Tue, 01 Jun 2021 15:32:00 +0200) x86_64 GNU/Linux node-2: Linux proxmox-2 5.11.22-4-pve #1 SMP PVE 5.11.22-8 (Fri, 27 Aug 2021 11:51:34 +0200) x86_64 GNU/Linux Should I upgrade...