Proxmox Host unreachable after few hours

F

frox

New Member
Mar 5, 2021
17
0
1
35
Hello,

two weeks ago I changed the CPU in my server from athlon 200GE ot an R5 3600X. But, after a few hours of operation, the server is no longer accessible via ssh for inexplicable reasons. There is also nothing in the syslog.

does anyone know what is going on?
 
Did you also checked "/var/log/syslog.1" to see messages from before the reboot?
 
Yes, but I cant find strings with such a error. Thats the End of the File:

Code: 
Mar  5 18:46:30 vms-1 kernel: [   10.882543] snd_hda_codec_realtek hdaudioC0D0:    inputs:
Mar  5 18:46:30 vms-1 kernel: [   10.882543] snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Mar  5 18:46:30 vms-1 kernel: [   10.882544] snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Mar  5 18:46:30 vms-1 kernel: [   10.882545] snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Mar  5 18:46:30 vms-1 kernel: [   10.894279] input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:0a:00.4/sound/card0/input3
Mar  5 18:46:30 vms-1 kernel: [   10.894323] input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:0a:00.4/sound/card0/input4
Mar  5 18:46:30 vms-1 kernel: [   10.894356] input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:0a:00.4/sound/card0/input5
Mar  5 18:46:30 vms-1 kernel: [   10.894382] input: HD-Audio Generic Line Out as /devices/pci0000:00/0000:00:08.1/0000:0a:00.4/sound/card0/input6
Mar  5 18:46:30 vms-1 kernel: [   10.894417] input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:0a:00.4/sound/card0/input7
Mar  5 18:46:30 vms-1 kernel: [   10.896021] Adding 4194300k swap on /dev/mapper/pve-swap.  Priority:-2 extents:1 across:4194300k SSFS
Mar  5 18:46:30 vms-1 kernel: [   10.952359] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   10.952361] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   10.952361]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   10.952361]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.016413] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.016414] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.016414]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.016414]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.088325] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.088326] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.088326]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.088326]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.148641] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.148642] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.148642]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.148642]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.212629] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.212630] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.212630]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.212630]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.272857] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.272858] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.272858]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.272858]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.328833] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.328834] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.328834]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.328834]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.396977] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.396978] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.396978]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.396978]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.452920] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.452922] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.452922]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.452922]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.512989] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.512990] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.512990]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.512990]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   11.580949] EDAC amd64: Node 0: DRAM ECC disabled.
Mar  5 18:46:30 vms-1 kernel: [   11.580951] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Mar  5 18:46:30 vms-1 kernel: [   11.580951]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Mar  5 18:46:30 vms-1 kernel: [   11.580951]  (Note that use of the override may cause unknown side effects.)
Mar  5 18:46:30 vms-1 kernel: [   12.040868] audit: type=1400 audit(1614966390.811:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=783 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.044771] audit: type=1400 audit(1614966390.815:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=784 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.044774] audit: type=1400 audit(1614966390.815:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=784 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.047672] audit: type=1400 audit(1614966390.815:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=786 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.047675] audit: type=1400 audit(1614966390.815:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=786 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.047677] audit: type=1400 audit(1614966390.815:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=786 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.051603] audit: type=1400 audit(1614966390.819:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default" pid=785 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.051606] audit: type=1400 audit(1614966390.819:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-cgns" pid=785 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.051608] audit: type=1400 audit(1614966390.819:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-with-mounting" pid=785 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.051609] audit: type=1400 audit(1614966390.819:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-with-nesting" pid=785 comm="apparmor_parser"
Mar  5 18:46:30 vms-1 kernel: [   12.104492] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
Mar  5 18:46:30 vms-1 kernel: [   12.144169] new mount options do not match the existing superblock, will be ignored
Mar  5 18:46:30 vms-1 kernel: [   12.172334] vmbr0: port 1(enp8s0) entered blocking state
Mar  5 18:46:30 vms-1 kernel: [   12.172336] vmbr0: port 1(enp8s0) entered disabled state
Mar  5 18:46:30 vms-1 kernel: [   12.172378] device enp8s0 entered promiscuous mode
Mar  5 18:46:30 vms-1 smartd[800]: Device: /dev/sdb [SAT], WDC WDS240G2G0B-00EPW0, S/N:19449D801249, WWN:5-001b44-8b18708a4, FW:UJ220400, 240 GB
Mar  5 18:46:30 vms-1 smartd[800]: Device: /dev/sdb [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Mar  5 18:46:30 vms-1 kernel: [   12.201853] Generic FE-GE Realtek PHY r8169-800:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE)
Mar  5 18:46:30 vms-1 smartd[800]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Mar  5 18:46:30 vms-1 smartd[800]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.WDC_WDS240G2G0B_00EPW0-19449D801249.ata.state
Mar  5 18:46:30 vms-1 smartd[800]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Mar  5 18:46:30 vms-1 dbus-daemon[791]: [system] AppArmor D-Bus mediation is enabled
Mar  5 18:46:30 vms-1 systemd[1]: Started Proxmox VE LXC Syscall Daemon.
Mar  5 18:46:30 vms-1 systemd[1]: Started System Logging Service.
Mar  5 18:46:30 vms-1 systemd[1]: Started Kernel Samepage Merging (KSM) Tuning Daemon.
Mar  5 18:46:30 vms-1 systemd[1]: Started PVE Qemu Event Daemon.
Mar  5 18:46:30 vms-1 sensors[862]: acpitz-acpi-0
Mar  5 18:46:30 vms-1 sensors[862]: Adapter: ACPI interface
Mar  5 18:46:30 vms-1 sensors[862]: temp1:        +16.8°C  (crit = +20.8°C)
Mar  5 18:46:30 vms-1 sensors[862]: k10temp-pci-00c3
Mar  5 18:46:30 vms-1 sensors[862]: Adapter: PCI adapter
Mar  5 18:46:30 vms-1 sensors[862]: Tdie:         +64.5°C  (high = +70.0°C)
Mar  5 18:46:30 vms-1 sensors[862]: Tctl:         +64.5°C
Mar  5 18:46:30 vms-1 systemd[1]: Started Initialize hardware monitoring sensors.
Mar  5 18:46:31 vms-1 smartd[800]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 57
Mar  5 18:46:31 vms-1 smartd[800]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-7HK659MN.ata.state
Mar  5 18:46:31 vms-1 smartd[800]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.WDC_WDS240G2G0B_00EPW0-19449D801249.ata.state
Mar  5 18:46:31 vms-1 systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
Mar  5 18:46:31 vms-1 pvefw-logger[775]: received terminate request (signal)
Mar  5 18:46:31 vms-1 pvefw-logger[775]: stopping pvefw logger
Mar  5 18:46:31 vms-1 systemd[1]: Stopping Proxmox VE firewall logger...
Mar  5 18:46:31 vms-1 kernel: [   12.321229] r8169 0000:08:00.0 enp8s0: Link is Down
Mar  5 18:46:31 vms-1 kernel: [   12.322535] vmbr0: port 1(enp8s0) entered blocking state
Mar  5 18:46:31 vms-1 kernel: [   12.322536] vmbr0: port 1(enp8s0) entered forwarding state
Mar  5 18:46:31 vms-1 ifup[788]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
Mar  5 18:46:31 vms-1 ceph-crash[793]: INFO:ceph-crash:monitoring path /var/lib/ceph/crash, delay 600s
Mar  5 18:46:31 vms-1 systemd[1]: Started Login Service.
Mar  5 18:46:31 vms-1 systemd[1]: Started Raise network interfaces.
Mar  5 18:46:31 vms-1 systemd[1]: Reached target Network.
Mar  5 18:46:31 vms-1 systemd[1]: Reached target Network is Online.
Mar  5 18:46:31 vms-1 systemd[1]: Started Grafana instance.
Mar  5 18:46:31 vms-1 systemd[1]: Started InfluxDB is an open-source, distributed, time series database.
Mar  5 18:46:31 vms-1 systemd[1]: Starting Postfix Mail Transport Agent (instance -)...
Mar  5 18:46:31 vms-1 systemd[1]: Starting LXC network bridge setup...
Mar  5 18:46:31 vms-1 systemd[1]: Starting Map RBD devices...
Mar  5 18:46:31 vms-1 systemd[1]: Starting Daily apt download activities...
Mar  5 18:46:31 vms-1 systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
Mar  5 18:46:31 vms-1 systemd[1]: Started LXC Container Monitoring Daemon.
Mar  5 18:46:31 vms-1 systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Mar  5 18:46:31 vms-1 systemd[1]: Started Unattended Upgrades Shutdown.
Mar  5 18:46:31 vms-1 systemd[1]: Starting OpenBSD Secure Shell server...
Mar  5 18:46:31 vms-1 systemd[1]: Started Map RBD devices.
Mar  5 18:46:31 vms-1 kernel: [   12.525068] bpfilter: Loaded bpfilter_umh pid 946
Mar  5 18:46:31 vms-1 systemd[1]: pvefw-logger.service: Succeeded.
Mar  5 18:46:31 vms-1 systemd[1]: Stopped Proxmox VE firewall logger.
Mar  5 18:46:31 vms-1 systemd[1]: Starting Proxmox VE firewall logger...
Mar  5 18:46:31 vms-1 pvefw-logger[953]: starting pvefw logger
Mar  5 18:46:31 vms-1 systemd[1]: Started Proxmox VE firewall logger.
Mar  5 18:46:31 vms-1 iscsid: iSCSI logger with pid=956 started!
Mar  5 18:46:31 vms-1 systemd[1]: Started iSCSI initiator daemon (iscsid).
Mar  5 18:46:31 vms-1 systemd[1]: Started LXC network bridge setup.
Mar  5 18:46:31 vms-1 systemd[1]: Starting Login to default iSCSI targets...
Mar  5 18:46:31 vms-1 iscsiadm[962]: iscsiadm: No records found
Mar  5 18:46:31 vms-1 systemd[1]: Started Login to default iSCSI targets.
Mar  5 18:46:31 vms-1 systemd[1]: Starting Availability of block devices...
Mar  5 18:46:31 vms-1 systemd[1]: Reached target Remote File Systems (Pre).
Mar  5 18:46:31 vms-1 systemd[1]: Reached target Remote File Systems.
Mar  5 18:46:31 vms-1 systemd[1]: Reached target PVE Storage Target.
Mar  5 18:46:31 vms-1 systemd[1]: Starting LSB: disk temperature monitoring daemon...
Mar  5 18:46:31 vms-1 systemd[1]: Starting LSB: start or stop rrdcached...
Mar  5 18:46:31 vms-1 systemd[1]: Starting Permit User Sessions...
Mar  5 18:46:31 vms-1 systemd[1]: Starting LXC Container Initialization and Autoboot Code...
Mar  5 18:46:31 vms-1 systemd[1]: Started Availability of block devices.
Mar  5 18:46:31 vms-1 systemd[1]: Started Permit User Sessions.
Mar  5 18:46:31 vms-1 systemd[1]: Started Getty on tty1.
Mar  5 18:46:31 vms-1 systemd[1]: Reached target Login Prompts.
 
avw said:
Is there anything shown on the console (maybe disable consoleblank first) when network stops working?
Click to expand...
No, it's like when the server is completely offline. It is not accessible via VNC, ping does not work either.
 
frox said:
No, it's like when the server is completely offline. It is not accessible via VNC, ping does not work either.
Click to expand...
Sorry for asking again but do you have physical access to the machine? Can you connect a screen and keyboard to the machine and login to the console when all network stops working? Apologies if I misunderstood and you meant that the physical display shows nothing, but this could also be caused by the default console blanking after some time.
 
avw said:
Sorry for asking again but do you have physical access to the machine? Can you connect a screen and keyboard to the machine and login to the console when all network stops working? Apologies if I misunderstood and you meant that the physical display shows nothing, but this could also be caused by the default console blanking after some time.
Click to expand...
I don't know if you can find anything in the logs, but it looks buggy

Code: 
Mar 13 16:35:46 vms-1 systemd[8655]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 13 16:35:46 vms-1 systemd[8655]: Starting D-Bus User Message Bus Socket.
Mar 13 16:35:46 vms-1 systemd[8655]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 13 16:35:46 vms-1 systemd[8655]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 13 16:35:46 vms-1 systemd[8655]: Reached target Timers.
Mar 13 16:35:46 vms-1 systemd[8655]: Listening on GnuPG network certificate management daemon.
Mar 13 16:35:46 vms-1 systemd[8655]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 13 16:35:46 vms-1 systemd[8655]: Listening on D-Bus User Message Bus Socket.
Mar 13 16:35:46 vms-1 systemd[8655]: Reached target Sockets.
Mar 13 16:35:46 vms-1 systemd[8655]: Reached target Basic System.
Mar 13 16:35:46 vms-1 systemd[8655]: Reached target Default.
Mar 13 16:35:46 vms-1 systemd[8655]: Startup finished in 87ms.
Mar 13 16:35:46 vms-1 systemd[1]: Started User Manager for UID 0.
Mar 13 16:35:46 vms-1 systemd[1]: Started Session 1 of user root.
Mar 13 16:35:47 vms-1 pvesh[2618]: Starting VM 106
Mar 13 16:35:47 vms-1 pve-guests[8904]: start VM 106: UPID:vms-1:000022C8:00000C76:604CDBD3:qmstart:106:root@pam:
Mar 13 16:35:47 vms-1 pve-guests[2789]: <root@pam> starting task UPID:vms-1:000022C8:00000C76:604CDBD3:qmstart:106:root@pam:
Mar 13 16:35:47 vms-1 systemd[1]: Started 106.scope.
Mar 13 16:35:47 vms-1 systemd-udevd[609]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 13 16:35:47 vms-1 systemd-udevd[609]: Could not generate persistent MAC address for tap106i0: No such file or directory
Mar 13 16:35:47 vms-1 kernel: [   32.346280] device tap106i0 entered promiscuous mode
Mar 13 16:35:47 vms-1 systemd-udevd[597]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 13 16:35:47 vms-1 systemd-udevd[597]: Could not generate persistent MAC address for fwbr106i0: No such file or directory
Mar 13 16:35:47 vms-1 systemd-udevd[626]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 13 16:35:47 vms-1 systemd-udevd[626]: Could not generate persistent MAC address for fwpr106p0: No such file or directory
Mar 13 16:35:47 vms-1 systemd-udevd[609]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 13 16:35:47 vms-1 systemd-udevd[609]: Could not generate persistent MAC address for fwln106i0: No such file or directory
Mar 13 16:35:47 vms-1 kernel: [   32.362660] fwbr106i0: port 1(fwln106i0) entered blocking state
Mar 13 16:35:47 vms-1 kernel: [   32.362662] fwbr106i0: port 1(fwln106i0) entered disabled state
Mar 13 16:35:47 vms-1 kernel: [   32.362733] device fwln106i0 entered promiscuous mode
Mar 13 16:35:47 vms-1 kernel: [   32.362768] fwbr106i0: port 1(fwln106i0) entered blocking state
Mar 13 16:35:47 vms-1 kernel: [   32.362769] fwbr106i0: port 1(fwln106i0) entered forwarding state
Mar 13 16:35:47 vms-1 kernel: [   32.364699] vmbr0: port 5(fwpr106p0) entered blocking state
Mar 13 16:35:47 vms-1 kernel: [   32.364701] vmbr0: port 5(fwpr106p0) entered disabled state
Mar 13 16:35:47 vms-1 kernel: [   32.364738] device fwpr106p0 entered promiscuous mode
Mar 13 16:35:47 vms-1 kernel: [   32.364754] vmbr0: port 5(fwpr106p0) entered blocking state
Mar 13 16:35:47 vms-1 kernel: [   32.364754] vmbr0: port 5(fwpr106p0) entered forwarding state
Mar 13 16:35:47 vms-1 kernel: [   32.366404] fwbr106i0: port 2(tap106i0) entered blocking state
Mar 13 16:35:47 vms-1 kernel: [   32.366405] fwbr106i0: port 2(tap106i0) entered disabled state
Mar 13 16:35:47 vms-1 kernel: [   32.366452] fwbr106i0: port 2(tap106i0) entered blocking state
Mar 13 16:35:47 vms-1 kernel: [   32.366453] fwbr106i0: port 2(tap106i0) entered forwarding state
Mar 13 16:35:51 vms-1 pvesh[2618]: Starting CT 110
Mar 13 16:35:51 vms-1 pve-guests[2789]: <root@pam> starting task UPID:vms-1:000028F1:00000E07:604CDBD7:vzstart:110:root@pam:
Mar 13 16:35:51 vms-1 pve-guests[10481]: starting CT 110: UPID:vms-1:000028F1:00000E07:604CDBD7:vzstart:110:root@pam:
Mar 13 16:35:51 vms-1 systemd[1]: Created slice PVE LXC Container Slice.
Mar 13 16:35:51 vms-1 systemd[1]: Started PVE LXC Container: 110.
Mar 13 16:35:51 vms-1 kernel: [   36.318128] EXT4-fs warning (device dm-11): ext4_multi_mount_protect:322: MMP interval 42 higher than expected, please wait.
Mar 13 16:35:51 vms-1 kernel: [   36.318128]
Mar 13 16:35:57 vms-1 systemd-timesyncd[872]: Synchronized to time server for the first time [2a02:8106:19::3]:123 (2.debian.pool.ntp.org).
Mar 13 16:36:00 vms-1 systemd[1]: Starting Proxmox VE replication runner...
Mar 13 16:36:00 vms-1 systemd[1]: pvesr.service: Succeeded.
Mar 13 16:36:00 vms-1 systemd[1]: Started Proxmox VE replication runner.
Mar 13 16:36:01 vms-1 CRON[18394]: (root) CMD (./temp.sh)
Mar 13 16:36:06 vms-1 kernel: [   51.285696] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
 
The errors about MAC address and autonegotiation are normal. Not sure about the EXT4-fs warning. Feel free to keep ignoring my question about information from the physical console once the system becomes unreachable.
 
avw said:
The errors about MAC address and autonegotiation are normal. Not sure about the EXT4-fs warning. Feel free to keep ignoring my question about information from the physical console once the system becomes unreachable.
Click to expand...
problem is, i have physical access but no suitable graphics card, because the 2U case is too small for it.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back