Recent content by davidand

@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...

@dcsapak This is all I found: syslog: Oct 4 14:07:47 proxmox-2 kernel: [ 219.334459] FS-Cache: Netfs 'cifs' registered for caching Oct 4 14:07:47 proxmox-2 kernel: [ 219.336231] Key type cifs.spnego registered Oct 4 14:07:47 proxmox-2 kernel: [ 219.336243] Key type cifs.idmap registered...

Actually I have some more info, I found the following in the kern.log on the second node: Oct 4 14:07:47 proxmox-2 kernel: [ 219.336482] CIFS: Attempting to mount \\nas\ProxmoxInstall Oct 4 14:07:47 proxmox-2 kernel: [ 219.360348] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE...

@dcsapak Definitely yes, this results in a successful share: ssh root@proxmox-2 mkdir /mnt/test mount //nas/ProxmoxInstall /mnt/a -t cifs -o username=proxmox_user I can both read and write the share this way. However, I've still got the question marks in the Proxmox UI. Can I go further...