6.3-3 admin console, ssh access, nfs host mounts all go offline after a few mins

Z

zanophol

Member
Apr 27, 2020
4
0
21
51
I had a stable PVE 6.3-3 install on a Dell T7910 with 128GB of RAM. Last night, I swapped the DIMMs from 8 16GB modules to 2 64GB modules. Everything seemed fine until a few minutes of the box being online and accessible, until the host machine (192.168.1.100 on my LAN) is unreachable via ssh or the web console. The samba and nfs shares are not accessible. The host IS pingable however, and vm/containers are all perfectly accessible. Host "ss -tlpn" shows the web console listening, so my guess is a host firewall, which has always been disabled. There is no other internal firewall for the 192.168.1.x network ('iptables --list' shows nothing).

I have changed nothing other than the RAM, and the box is completely up to date as of now. I have remote console access, and the box isn't throwing any errors. I have no idea what to look into considering this box was perfectly happy for at least 6 months before this latest twist.

UPDATE: If I turn off wifi on my phone and vpn into my router over LTE, I can access Proxmox via the Aprox app AND via the web console. My vpn uses a different ip scheme than 192.168.x.x. I have also tried to access the web console via a web browser on a vm with no success. If I execute 'curl -s -k https://192.168.1.100:8006' on the proxmox host, it returns a response.

UPDATE 2: If I 'telnet 192.168.1.100 8006' from my ubuntu box, the pve host web admin gui wakes up and I can log in, but only for a short period of time. Why do I think a recent update is to blame?

Any ideas???
 
Last edited:
BobhWasatch said:
What did you change on your network that you didn't think would affect your server?
Click to expand...
That's just it. I have changed NOTHING on my network. All network dns, dhcp, etc is handled on my router. No changes have been made, and I am the only one with access. If it was the internal proxmox firewall, it wouldn't allow access and then just drop it a few minutes later. This one has me mystified.
 
Last edited:
BobhWasatch said:
Your symptoms sound a lot like a new device has the same IP as your server, or there is a duplicate mac address, or something of that nature.
Click to expand...
I thought so to, but arp-scan only finds the pve host at 192.168.1.100, and the MAC it finds matches the pve host.
 
I loaded the bnx2x module from debian sid, and this appears to have fixed the troublesome network issue that was seemingly driver related.
 
You must log in or register to reply here.
Top Bottom