Restarting pmg-smtp-filter on the cluster

C

cdirk07

Member
Proxmox Subscriber
May 17, 2021
17
0
6
36
I have edited the custom.cf file on one of the servers. I know that file is synced between all of the servers in the cluster. My question is, is there a way to restart pmg-smtp-filter on all of the servers without having to run it on all of them?
 
cdirk07 said:
I have edited the custom.cf file on one of the servers. I know that file is synced between all of the servers in the cluster. My question is, is there a way to restart pmg-smtp-filter on all of the servers without having to run it on all of them?
Click to expand...
This should happen automatically during cluster sync?
please check the logs for a reload of pmg-smtp-filter
 
looks like there is a 'Filter daemon (re)started' at around 3am every day and then a 'reloading configuration Proxmox_ruledb' about every hour. Are one of these what you are talking about? If so, how do I know that my rule hasn't broken pmg-smtp-filter?
 
cdirk07 said:
ooks like there is a 'Filter daemon (re)started' at around 3am every day and then a 'reloading configuration Proxmox_ruledb' about every hour. Are one of these what you are talking about? If so, how do I know that my rule hasn't broken pmg-smtp-filter?
Click to expand...

There should have been a restart of pmg-smtp-filter after the first cluster synchronization (done by pmgmirror) after you changed the custom.cf - I just verified this here - these are the logs:
Code: 
Nov 30 15:20:04 pmg-node pmgmirror[57675]: starting cluster synchronization                         
Nov 30 15:20:05 pmg-node pmgmirror[57675]: cluster synchronization finished  (0 errors, 1.07 seconds (files 0.09, database 0.68, config 0.30))
Nov 30 15:20:05 pmg-node systemd[1]: Stopping Proxmox SMTP Filter Daemon...                         
Nov 30 15:20:05 pmg-node pmg-smtp-filter[57670]: 2021/11/30-15:20:05 Server closing!                
Nov 30 15:20:05 pmg-node systemd[1]: pmg-smtp-filter.service: Succeeded.                            
Nov 30 15:20:05 pmg-node systemd[1]: Stopped Proxmox SMTP Filter Daemon.                            
Nov 30 15:20:05 pmg-node systemd[1]: pmg-smtp-filter.service: Consumed 1.759s CPU time.             
Nov 30 15:20:05 pmg-node systemd[1]: Starting Proxmox SMTP Filter Daemon...                         
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: Process Backgrounded                               
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: 2021/11/30-15:20:06 main (type Net::Server::PreFork) starting! pid(75907)
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: Binding to TCP port 10023 on host 127.0.0.1 with IPv4
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: Binding to TCP port 10024 on host 127.0.0.1 with IPv4
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: Group Not Defined.  Defaulting to EGID '0'         
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: User Not Defined.  Defaulting to EUID '0'          
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: Setting up serialization via flock                 
Nov 30 15:20:06 pmg-node pmg-smtp-filter[75907]: Filter daemon (re)started (max. 17 processes)      
Nov 30 15:20:06 pmg-node systemd[1]: Started Proxmox SMTP Filter Daemon.                            
Nov 30 15:20:07 pmg-node pmg-smtp-filter[75907]: Beginning prefork (2 processes)                    
Nov 30 15:20:07 pmg-node pmg-smtp-filter[75907]: Starting "2" children                              
Nov 30 15:20:13 pmg-node pmgpolicy[57653]: starting policy database maintenance (greylist, rbl)     
Nov 30 15:20:13 pmg-node pmgpolicy[57653]: end policy database maintenance (21 ms, 1 ms)            
Nov 30 15:20:37 pmg-node pmg-smtp-filter[75907]: starting database maintenance                      
Nov 30 15:20:37 pmg-node pmg-smtp-filter[75907]: end database maintenance (8 ms)
 
You must log in or register to reply here.
Top Bottom