Error 500: can't activate storage 'Storage1' on node 'NodeB'

[Ravenrave]

Brand New installation - 2nd node - I have a disk for loading ISOs, cannot upload any iso, its starts uploading and gives me this error.
This same storage can load container templates and use them.
I am also able to use this disk for creating and running VMs and Containers, but cannot load ISOs. Even small ISOs
I have chosen all content types and also checked the config file to confirm it.

Error 500: can't activate storage 'Storage1' on node 'NodeB': command '/usr/bin/ssh -o 'BatchMode=yes' 10.20.20.5 -- /usr/sbin/pvesm status --storage Storage1' failed: exit code 255

What's wrong and please help me resolve this.

Thank you.

 

[apoc]

Looks like the system tries to initiate a remote call to your other node.
Have you checked things there?

 

[Ravenrave]

Things are good in that node.

Any idea, how to fix this?

 

[apoc]

command '/usr/bin/ssh -o 'BatchMode=yes' 10.20.20.5 -- /usr/sbin/pvesm status --storage Storage1'

I'd try executing this command manually and see if it reports more information instead of only the exitcode.
Aside that the proxmox team should hopefully be able to help @fabian @Dominic

 

[Dominic]

Hi,

in addition to trying this manually, please also post the output of the following commands:

pvecm status
cat /etc/pve/storage.cfg
fdisk -l
pvesm status

 

[martindupond]

Hello,
If you want to load an ISO on serverA you have to log into pve using https://serverA:8006. You probably used https://serverB:8006

 

[oxymoron290]

Hello,
If you want to load an ISO on serverA you have to log into pve using https://serverA:8006. You probably used https://serverB:8006

Made an account to specifically let you know that this was my issue and you helped me resolve it. Thank you!

 

[hamidm]

Hi,

I hit this page searching for same problem, leave a possible answer here, may help someone.

It could be issue with ssh failing to connect to that Node. as showed in error message, it is using ssh to the nodeB.

try manually ssh in cli from node that you use to for web panel to the NodeB and see if it can connect.

my case it returned with : "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" and failed to ssh.

i'vr removed the changed host in known_host file with:
ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R [IP]

and ssh again.
it's fixed the problem.

 

[w46n3r]

i'vr removed the changed host in known_host file with:
ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R [IP]

and ssh again.

Thanks!

 

[esi_y]

Linking through related: https://forum.proxmox.com/threads/s...ass-ssh-known_hosts-bug-s.137809/#post-615906