Proxmox stopped and did nothing until system reboot

[Unisonic]

Hello everyone!
Proxmox stopped and did nothing until system reboot. The web interface was not available, mail did not go through it. Linux Server was online, ssh worked. The logs are empty

Nov 29 17:53:35 proxmox02 postfix/qmgr[961]: ADEAC281683: removed
Nov 29 17:53:35 proxmox02 postfix/smtpd[209547]: connect from unknown[x.x.x.x]
Nov 29 17:53:36 proxmox02 postfix/smtpd[209547]: disconnect from unknown[x.x.x.x] ehlo=1 auth=0/1 rset=1 quit=1>
Nov 29 17:53:44 proxmox02 pmg-smtp-filter[91013]: starting database maintenance
Nov 29 17:53:44 proxmox02 pmg-smtp-filter[91013]: end database maintenance (10 ms)
Nov 29 17:53:53 proxmox02 pmgdaemon[192604]: successful auth for user 'xxx@pam'
Nov 29 17:54:28 proxmox02 postfix/postscreen[198250]: CONNECT from [x.x.x.x]:50886 to [x.x.x.x]:25
Nov 29 17:54:28 proxmox02 postfix/postscreen[198250]: WHITELISTED [x.x.x.x]:50886
Nov 29 17:54:28 proxmox02 postfix/smtpd[209547]: connect from unknown[x.x.x.x]
Nov 29 17:54:29 proxmox02 postfix/smtpd[209547]: disconnect from unknown[x.x.x.x] ehlo=1 auth=0/1 rset=1 quit=1>
Nov 29 17:54:43 proxmox02 postfix/smtpd[209103]: timeout after END-OF-MESSAGE from unknown[x.x.x.x]
-- Boot 745ce129c0074d3fb16074fa0f46ff5e --
Nov 30 10:50:07 proxmox02 kernel: Linux version 5.15.74-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110>
Nov 30 10:50:07 proxmox02 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.74-1-pve root=/dev/mapper/pmg-root ro >
Nov 30 10:50:07 proxmox02 kernel: KERNEL supported cpus:
Nov 30 10:50:07 proxmox02 kernel: Intel GenuineIntel
Nov 30 10:50:07 proxmox02 kernel: AMD AuthenticAMD
Nov 30 10:50:07 proxmox02 kernel: Hygon HygonGenuine
Nov 30 10:50:07 proxmox02 kernel: Centaur CentaurHauls
Nov 30 10:50:07 proxmox02 kernel: zhaoxin Shanghai

My proxmox configuration
Proxmox MailGateway 7.1.9
Debian GNU/Linux 11
8cpu, 16gb ram, 100gb HDD

The server is running in a cluster. It is slave.

Maybe there are other logs where I can see what caused this strange server behavior.

 

[Stoiko Ivanov]

hmm - maybe a full filesystem? - check the journal (journalctl -b -1 to get the logs from the last boot)

 

[Unisonic]

I see only this
Nov 29 17:53:33 proxmox02 pmg-smtp-filter[208929]: WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE x.ru$/ at /usr/share/perl5/PMG/RuleDB/WhoRegex.pm line 100.
Maybe something wrong in hypervisor, but other vm work without issues.

 

[Stoiko Ivanov]

Nov 29 17:53:33 proxmox02 pmg-smtp-filter[208929]: WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE x.ru$/ at /usr/share/perl5/PMG/RuleDB/WhoRegex.pm line 100.

That's something you should fix (you probably want to use '.*x.ru' instead of '*x.ru' in the Who Object which causes this) - but unrelated to the issue

else - the log does not indicate any issue - so it's still not clear where the issue originated
- if you can ssh to it - could you connect to port 25 as well?

 

[Unisonic]

That's something you should fix (you probably want to use '.*x.ru' instead of '*x.ru' in the Who Object which causes this) - but unrelated to the issue

That problem i found and fix in WhoObjects

else - the log does not indicate any issue - so it's still not clear where the issue originated
- if you can ssh to it - could you connect to port 25 as well?

Yes, i can connect to 25 port

220 x.ru xxx
HELO x-x
250 x.ru
EHLO x.ru
250-x.ru
250-PIPELINING
250-SIZE 100485760
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-SMTPUTF8
250 CHUNKING

 

[Stoiko Ivanov]

Then everything should be working - are pmgproxy and pmgdaemon running (they are needed for the web-interface)

 

[Unisonic]

Yes it works, but why it stopped? If this happens again I'll try to collect more diagnostic information

 

[Stoiko Ivanov]

Yes it works, but why it stopped? If this happens again I'll try to collect more diagnostic information

Sadly without any more info I'm also at a loss as to the reason - if it occurs again - share the info here then we'll have a look