Search results

shit I think I messed it up. we are doing both pve and pve2, give me a sec

ok, doing same but ssh target pve: Mar 03 15:18:25 pve.ifire.net sshd[912557]: Accepted publickey for root from 181.199.63.171 port 8488 ssh2: RSA SHA256:ZRgHJSjs9COoTp8AP1SSCua5bjeULMFfDYvdi0+0OUo Mar 03 15:18:25 pve.ifire.net sshd[912557]: pam_unix(sshd:session): session opened for user...

I use public key, never password. I will do the test: a. close connections b. open workstation > pve2 c. run on pve2 > journalctl -efu ssh d. open workstation tab 2 > pve2 e. Mar 03 15:15:36 pve2.ifire.net sshd[2330521]: Accepted publickey for root from 181.199.63.171 port 9594 ssh2: RSA...

1. done 2. done 3-5 below 6. qdevice is 'pbs-ifire', its local on 192.168.1.253. it is working. it is a PBS host. 7. node 3 I should have said more accurately "qdevice" 3, my workstation is the 181 ip. I aborted after running the command on pve which failed: Mar 03 14:56:07 pve2.ifire.net...

Let me also add I can ssh from pve to pve2 without error. It's only the replication job that seems to be complaining. pvecm says we have quorum. Will also add that I use tailscale. But that pre-dated things breaking. The fault started today after adding qdevice on third node (pbs install...

Times are synced. Cluster replication broke this morning sometime after I added the qdevice for node 3. The 192.168.x.x is on its own interface and is a private connection between pve and pve2 and the qdevice, its own vlan or whatever at the datacenter. 02:40 PM [pve]~ root # traceroute...

pve1: 02:09 PM [pve]~ root # journalctl -u ssh --since "2024-03-03 13:50" Mar 03 13:50:01 pve.ifire.net sshd[819164]: Accepted publickey for root from 192.168.1.252 port 39698 ssh2: RSA SHA256:> Mar 03 13:50:01 pve.ifire.net sshd[819164]: pam_unix(sshd:session): session opened for user...

From pve1: 02:09 PM [pve]~ root # ssh-keygen -L -f /etc/ssh/ssh_host_ed25519_key-cert.pub /etc/ssh/ssh_host_ed25519_key-cert.pub: Type: ssh-ed25519-cert-v01@openssh.com host certificate Public key: ED25519-CERT SHA256:BcZpML7q+U6nUn4YoHj9Qr+uzqT1ZAnFfFxBSaOmj+s Signing...

That is correct. 01:51 PM [pve]~ root # /usr/bin/ssh -vvv -o 'HostKeyAlias=pve2' root@192.168.1.252 -- /bin/true OpenSSH_9.2p1 Debian-2+deb12u2, OpenSSL 3.0.11 19 Sep 2023 debug1: Reading configuration data /root/.ssh/config debug1: /root/.ssh/config line 2: Applying options for * debug1...

# pvecm status Cluster information ------------------- Name: ifire Config Version: 11 Transport: knet Secure auth: on Quorum information ------------------ Date: Sun Mar 3 13:33:01 2024 Quorum provider: corosync_votequorum Nodes: 2 Node ID...

01:32 PM [pve2]~ root # ls -l /etc/ssh/ssh_known_hosts lrwxrwxrwx 1 root root 25 Mar 3 12:52 /etc/ssh/ssh_known_hosts -> /etc/pve/priv/known_hosts 01:32 PM [pve2]~ root #

Thank you for responding. 01:22 PM [pve]~ root # ls -l /etc/ssh/ssh_known_hosts lrwxrwxrwx 1 root root 25 Mar 3 12:52 /etc/ssh/ssh_known_hosts -> /etc/pve/priv/known_hosts 01:22 PM [pve]~ root # pve/node 1: 1545 openssl x509 -in /etc/pve/pve-root-ca.pem -inform pem -pubkey -noout |...

Ok, I did it on the two nodes (third is qdevice, assumed no need to touch). Restarted ssh. Went to a replication job, scheduled, and log looks same as before I issued the commands: 2024-03-03 13:02:02 102-0: (remote_prepare_local_job)...

Is this bug still present in 8.1.4? Trying to decide if I need to try such a risky maneuver or if this isn't going to help my ssh key issues

I see you increased token to 10000 and your WAN was running around 10ms. I need to achieve cluster with WAN closer to 100ms for one of the nodes. Is this a linear scale,, such as to simply increase token to 100000?

Did it work as laid out in the guide? I am in production, remote from datacenter, and need to modify our cluster home network to a new subnet.

I don't want to return to nginx. I worked another workaround solely for this issue but it's unique to my deployment. I really want to see this fixed in PBS.

I'm having the same issue. Hardware unchanged for 13 months. 11 months zero problems but recently it's randomly rebooting after hours or days. Logs of course show nothing. I just now updated to pvetest repo because this is becoming a serious production issue. I'm using i7 13th gen 128gb ECC.

@McTwist I hope you can try my last post settings and see if you get it working. If so lets compare configs. I have two PBS on different continents and both behind Caddy. one works as a remote for the other. In one direction it works fine, and in the other direction I get these errors (now...

I'm running 3.1.2 on both sides and the problem still exists.