Shared storage across nodes not working - See comment #56.
- Thread starter Proximate
- Start date
if these two lines were included in the opening post, it would have saved a lot of back and forth and frustration, I'd say all of it.
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.
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-isoI 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.
From what I see the ssh is still not working. That 255 error is from ssh not from pvesm:
https://docs.platform.sh/development/ssh/troubleshoot-ssh.html
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
https://forum.proxmox.com/threads/migration-issue-after-replacing-a-node.13968/
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
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.
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. 
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.
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-isoSure 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.
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.
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:
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