Strange failure in pmg-smtp-filter

emanuelserpa

New Member
Apr 28, 2020
8
1
3
23
Yesterday I faced a problem that the service pmg-smtp-filter stopped abnormaly:

Code:
Nov 26 13:07:56 gateway systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=11/n/a
Nov 26 13:07:56 gateway systemd[1]: pmg-smtp-filter.service: Killing process 5291 (pmg-smtp-filter) with signal SIGKILL.
Nov 26 13:07:56 gateway systemd[1]: pmg-smtp-filter.service: Killing process 5309 (pmg-smtp-filter) with signal SIGKILL.
Nov 26 13:07:57 gateway systemd[1]: pmg-smtp-filter.service: Failed with result 'exit-code'.

I looked at syslog but I didn't find nothing that showed something that hinted why this happened. The service remained like that for some time and I had to manually start again to everything work normally. What I can do to avoid this to happen again? Thanks!
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
4,663
585
118
If possible please share the complete journal around the time the problem occured - from the 4 lines it's impossible to see what might have caused the issue.

Thanks!
 

emanuelserpa

New Member
Apr 28, 2020
8
1
3
23
Around this time I can see this error syncronizing with the cluster, then the process exited.

Code:
Nov 26 13:07:00 gateway pmg-smtp-filter[22813]: starting database maintainance 
Nov 26 13:07:02 gateway pmgmirror[24753]: starting cluster syncronization 
Nov 26 13:07:07 gateway pmgmirror[24753]: database sync 'cluster' failed - connect timeout 
Nov 26 13:07:07 gateway pmgmirror[24753]: cluster syncronization finished  (1 errors, 5.01 seconds (files 0.00, database 5.01, config 0.00)) 
Nov 26 13:07:23 gateway freshclam[842]: Received signal: wake up 
Nov 26 13:07:23 gateway freshclam[842]: ClamAV update process started at Thu Nov 26 13:07:23 2020 
Nov 26 13:07:23 gateway freshclam[842]: Received signal: wake up 
Nov 26 13:07:23 gateway freshclam[842]: ClamAV update process started at Thu Nov 26 13:07:23 2020 
Nov 26 13:07:56 gateway systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=11/n/a 
Nov 26 13:07:56 gateway systemd[1]: pmg-smtp-filter.service: Killing process 5291 (pmg-smtp-filter) with signal SIGKILL. 
Nov 26 13:07:56 gateway systemd[1]: pmg-smtp-filter.service: Killing process 5309 (pmg-smtp-filter) with signal SIGKILL. 
Nov 26 13:07:57 gateway systemd[1]: pmg-smtp-filter.service: Failed with result 'exit-code'. 
Nov 26 13:08:01 gateway kernel: [7310586.956855] [UFW BLOCK] IN=eth0 OUT= MAC=02:00:00:aa:a0:62:00:ff:ff:ff:ff:fe:08:00 SRC= DST= LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=44338 PROTO=TCP SPT=45764 DPT=50342 WINDOW=1024 RES=0x00 SYN URGP=0  
Nov 26 13:08:02 gateway kernel: [7310587.784341] [UFW BLOCK] IN=eth0 OUT= MAC=02:00:00:aa:a0:62:00:ff:ff:ff:ff:fe:08:00 SRC= DST=167.114.223.161 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=40610 PROTO=TCP SPT=57482 DPT=50547 WINDOW=1024 RES=0x00 SYN URGP=0  
Nov 26 13:08:08 gateway kernel: [7310593.792844] [UFW BLOCK] IN=eth0 OUT= MAC=02:00:00:aa:a0:62:00:ff:ff:ff:ff:fe:08:00 SRC=DST= LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=5027 PROTO=TCP SPT=45861 DPT=4420 WINDOW=1024 RES=0x00 SYN URGP=0
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
4,663
585
118
How much memory/RAM does the PMG have?
(The messages from ClamAV make mit think it might be an OOM condition)
 

About

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

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 your own in 60 seconds.

Buy now!