Shared storage across nodes not working - See comment #56.

Since you ranted about proxmox I was wondering if you never encountered problems with vmware. Every system has its quirks.
 
Tried uploading to NFS storage from pro07 and got the same error.
Was I supposed to reboot the node or something?

1662670132639.png
 
Getting this ssh stuff right was definitely important, but maybe the real culprit is yet to be found ...

Please execute the problematic command on pro07 and see if there are further information on the command line as well as in journalctl.
Code: 
/usr/sbin/pvesm status --storage nfs-iso
 
ph0x said:
Since you ranted about proxmox I was wondering if you never encountered problems with vmware. Every system has its quirks.
Click to expand...
I wasn't ranting, I was stating my experience. You can stop trying to chastising me any time, I'm still here wanting try proxmox thanks to your help.
From these experiences come better knowledge, just like those helping me had to do.
 
  • Like
Reactions: ph0x
Proximate said:
I wasn't ranting, I was stating my experience. You can stop trying to chastising me any time, I'm still here wanting try proxmox thanks to your help.
From these experiences come better knowledge, just like those helping me had to do.
Click to expand...
I don't, I'm trying to help objectively as possible. Otoh, as one calls into the canyon, so it echoes back.
There are a lot of Proxmox fan boys here (including me). Ranting (yeah, you might call it differently) about their beloved hypervisor when the error seems to be on the user side, is a bit offensive.
 
Sorry if that hurts you but it's how I feel. It felt like everything is coming apart and wondering if it will get worse. There are many production servers that were moved from esx to proxmox so that we'd have a real production environment to test. Mind you, all of the servers are redundant.

I like proxmox, I would like to keep using it and eventually to suggest supporting it by buying subs. When things start coming apart like that, you get nervous and you wonder if it's going to keep getting worse. So yeah, I wasn't happy with what I was seeing but would like it to get better.

At this moment, it is nice to know that ssh may have caused some or all of the problems but it's still not working right.
 
You're learning it the hard way, then. That's very honorable. Hope you don't loose too many years with it. :D
I guess it wasn't you who decided to switch to Proxmox? ;)

But back to topic: Please execute the problematic command on pro07 and see if there are further information on the command line as well as in journalctl.

Code: 
/usr/sbin/pvesm status --storage nfs-iso
 
Sure enough, all of the nodes had an ssh problem to that node 07.
I re-generated the key with the info you gave and now all nodes have access to each other again.
I tested each node to each node.
Now to find out what is happening that I cannot install rocky or almalinux.
 
So the nfs issue is solved, then?
I suggest to open a new thread for the OS issues since people tend to not look in long threads after a while.
 
Agreed on the other problem but I'm still not able to upload when doing so on node 07. I get the same ssh error.
 
Okay, then it's indeed most probably still an ssh issue, like @bbgeek17 already pointed out.

Two things to check:
1. Open the GUI of pro07 and try the upload from there
2. Try the complete command from the node that you tried from now:
Code: 
/usr/bin/ssh -o "BatchMode=yes" 10.0.0.76 -- usr/sbin/pvesm status --storage nfs-iso
 
You must log in or register to reply here.
Top Bottom