[SOLVED] Server lost network access

rhynchopinae

New Member
Mar 17, 2021
5
1
1
28
I'm running 2630L V3 + 16GB ECC ddr4, I can run proxmox for 10 hours +/- but after I leave it AFK I lose the Host and VMs, both no longer respond to pings, is there anything I could do to check what the error was after rebooting and getting network back?

I cannot turn it off pressing the power button when it loses networking but I can when it works.
Proxmox 6.2

Thanks.
 
Last edited:
Hi,

Check the Syslog for any hint and also post your network configuration please
Thank you so much for your answer, I have just tried to take the syslog but I need to wait for it to happen again since I have rebooted a few times and its not there. About my network config I'm not sure how to do that. Not sure if this is what you are looking for
vNvCMWB.png


QOR9khj.png



I have just noticed that my VM starts and a few minutes later shutdowns when I was sleeping (No one have done that)

1615981225300.png
 
Last edited:
Hi,

Thanks for the screenshots.

For the Syslog, you can find it in Datacenter -> Node Name -> Syslog, there you can either live mode or select time, if you can't get them anything in live mode you can then select the time from to.

For the network configuration, you can post the output of cat /etc/network/interfaces command
 
Code:
auto lo
iface lo inet loopback

iface enp5s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.192
        netmask 255.255.255.0
        gateway 192.168.0.1
        bridge_ports enp5s0
        bridge_stp off
        bridge_fd 0

I have tried the syslog using the web interface but it only gives since 2 hours ago
and running
head -n1 /var/log/syslog
gives me today at 6:39
(the started yesterday night)

My VM has the ip ending with .37 It has DHCP (I guess) but I have locked the ip into my router so it doesn't change
 
Thanks for output

your network configuration looks good, please send the Syslog after occurs the issue again
 
Thanks for output

your network configuration looks good, please send the Syslog after occurs the issue again
Happened again, I have the syslog

this jump here is kinda weird
Code:
Mar 17 14:52:01 local systemd[1]: Started Proxmox VE replication runner.
Mar 17 14:53:00 local systemd[1]: Starting Proxmox VE replication runner...
Mar 17 14:53:01 local systemd[1]: pvesr.service: Succeeded.
Mar 17 14:53:01 local systemd[1]: Started Proxmox VE replication runner.
Mar 17 17:00:22 local systemd-modules-load[499]: Inserted module 'iscsi_tcp'
Mar 17 17:00:22 local dmeventd[534]: dmeventd ready for processing.
Mar 17 17:00:22 local systemd-modules-load[499]: Inserted module 'ib_iser'

If you need the full syslog let me know if it's safe to post it here or if I PM it to you.

Thanks!

NOTE: I'm not sure but seeing the SYSLOG I think the problem may be the RAM as I have TONS of repeated messages saying weird things
 
Hi,
i got the same problem multiple times.
A few months ago it was a CIFS mounting problem, where i mounted a NAS samba share once over proxmox and additionally in a container. The mutliple mount seemed to crash the eth-port, maybe this information helps.

But since last week the problem occurs again, without cifs mounts. How can I enter the command line when i am at the machine running proxmox? I would like to share my syslog too. But as long as it gets a reset after rebot i cant access the cause.

Edit
my server has 4 LAN ports, could i use two or more as a backup port when the first fails as usual?
 
Last edited: