Question Does Plesk possibly monitor this file /var/log/messages?

[Azurel]

Server operating system version

AlmaLinux 8.10

Plesk version and microupdate number

18.0.65

My server was no longer accessible and a restart then showed these errors in the /var/log/messages:

kernel: NETDEV WATCHDOG: enp35s0 (igb): transmit queue 1 timed out
kernel: WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:472 dev_watchdog+0x272/0x280
kernel: Modules linked in: xt_state xt_conntrack nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nft_reject nft_ct ip6t_REJECT nf_reject_ipv6 ip_set_hash_net nf_tables_set ipt_REJECT nf_reject_ipv4 xt_multiport nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set binfmt_misc nf_tables libcrc32c nfnetlink intel_rapl_msr intel_rapl_common snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi edac_mce_amd snd_hda_codec kvm_amd snd_hda_core snd_hwdep snd_pcm kvm irqbypass snd_timer snd sp5100_tco rapl wmi_bmof soundcore i2c_piix4 k10temp gpio_amdpt gpio_generic acpi_cpufreq ext4 mbcache jbd2 drm_vram_helper drm_ttm_helper raid1 ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ahci drm crc32c_intel libahci igb ghash_clmulni_intel nvme libata ccp nvme_core dca t10_pi i2c_algo_bit wmi dm_mirror dm_region_hash dm_log dm_mod
kernel: CPU: 6 PID: 0 Comm: swapper/6 Kdump: loaded Tainted: G W --------- - - 4.18.0-348.7.1.el8_5.x86_64 #1
kernel: Hardware name: Hetzner /B450D4U-V1L, BIOS L1.02U 05/11/2020
kernel: RIP: 0010:dev_watchdog+0x272/0x280
kernel: Code: 48 85 c0 75 e4 eb 9b 4c 89 f7 c6 05 a0 e1 fb 00 01 e8 f2 a4 fa ff 89 d9 4c 89 f6 48 c7 c7 58 e8 37 ad 48 89 c2 e8 97 01 8d ff <0f> 0b e9 7a ff ff ff 0f 1f 80 00 00 00 00 0f 1f 44 00 00 41 57 41
kernel: RSP: 0018:ffffaabbc6594e88 EFLAGS: 00010282
kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000007
kernel: RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff89d68e996850
kernel: RBP: ffff89b8831e845c R08: 0000000000000bf0 R09: ffff89b7000b95e0
kernel: R10: ffffffffac713960 R11: ffffaabbc6594d30 R12: 0000000000000006
kernel: R13: ffff89b8831e8480 R14: ffff89b8831e8000 R15: 0000000000000008
kernel: FS: 0000000000000000(0000) GS:ffff89d68e980000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 00007f1d8e982188 CR3: 00000009ceb18000 CR4: 0000000000350ee0
kernel: Call Trace:
kernel: <IRQ>
kernel: ? pfifo_fast_enqueue+0x140/0x140
kernel: call_timer_fn+0x2d/0x130
kernel: run_timer_softirq+0x1d8/0x410
kernel: ? __hrtimer_run_queues+0x130/0x280
kernel: ? ktime_get+0x36/0xa0
kernel: __do_softirq+0xd7/0x2d6
kernel: irq_exit+0xf7/0x100
kernel: smp_apic_timer_interrupt+0x74/0x130
kernel: apic_timer_interrupt+0xf/0x20
kernel: </IRQ>
....

It is displayed that something has not worked with the network and at some point the system is no longer responsive and stops everything, including writing logs.

kernel: NETDEV WATCHDOG: enp35s0 (igb): transmit queue 1 timed out
...
kernel: igb 0000:23:00.0 enp35s0: Reset adapter
kernel: igb 0000:23:00.0 enp35s0: igb: enp35s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
...

Should Plesk possibly recognize this and inform by e-mail, as well as in case of high load (monitoring) or is this something where you should set up monitoring itself or is there already something in Plesk? What would be your solution here to make such errors more noticeable?

 

[AYamshanov]

Hi!

It looks like a hardware issue. It makes sense to use external monitoring to detect such issues (e.g. Server Monitoring - 360 Monitoring) because when a server stops responding, it can't send any notifications as well, but external monitoring can just because it is located outside the server. By default, with the Plesk Monitoring extension, it is possible to monitor 1 server and 5 websites for free (the pricing plan "Lite").

I recommend opening a support ticket with a service/server provider to investigate and solve a hardware issue.