Recent content by ph0x

I encountered this problem as well and finally found someone who dug into it. More than six years ago ... I had the most problems with VMs which have a lot of virtual nics. Setting the input policy to DROP rather than REJECT seems to resolve it.

That's what I would do, yes. If you want to reuse the OSDs there might even be a way to restore them without having the cluster go through a backfill. I didn't dig into the necessary steps so far, but that should be possible. If you deploy a completely new node I'd just create the new OSDs...

Maybe you should define eno1.1 first? Apart from that I don't think that this will work as expected. I doubt that a vlan can work with ipv4 while the native vlan is ipv6. However, that's just a guess.  

As I said one cannot really know what causes the problem. That's kind of your task to ensure that passwordless login works flawlessly because only you know your exact setup. It's definitely not an error that is very common, what can be seen by us poking in the dark. However we were able to...

There are a lot of possibilities where to look at, regarding those ssh problems. You mentioned strict ssh rules, that's where I would begin. Loosen up on the rules, try to encircle the problem. We don't know why ssh works and the above command does not, but as long as this issue isn't resolved...

If you don't need a permanent pbs this can as well be a VM.

Yeah well, there you have your problem. Fix the ssh issue and the upload will most probably work.

Won't pbs import the datastore if the .chunks folder already exists during creation of the datastore?

You would probably need to set up another pbs instance, import the data store from that network share and define the new pbs as a storage in pve. Then you can restore the machines backuped there.

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: /usr/bin/ssh -o "BatchMode=yes" 10.0.0.76 -- usr/sbin/pvesm...

Irgendwas wird's gewesen sein. :D

Yep.

Ich würde auf eine Einstellung in BIOS oder auf einen Hardware-Defekt tippen. Schau dir mal an, was das BIOS zu den Power-Optionen zu sagen hat.

Dass die Netzwerkkonnektivität vom Storage der vDisk abhängt, wäre äußerst ungewöhnlich. Funktionieren denn Verbindungen im lokalen Netz per IP-Adresse? Ssh z.B.?

Was macht der Node, wenn du es über die Konsole versuchst? shutdown -hP now