Re: Logging silence
> "Simon" == Simon Wilson writes: John> More details would help us help you. John> John Simon> I worked it out. journald.conf was set to MaxLevelStore=notice, Simon> so it wasn't just postfix not logging, just that was the Simon> symptom picked up. Simon> I really was missing something obvious. Now I need to work back Simon> to see how / who changed that. Glad you found the solution. It's always a pain keeping systems in sync like this, especially when someone else might be changing things behind your back. Been there!
Re: Logging silence
- Message from John Stoffel - Date: Sun, 28 Nov 2021 22:58:01 -0500 From: John Stoffel Subject: Re: Logging silence To: si...@simonandkate.net Cc: John Stoffel , postfix-users@postfix.org "Simon" == Simon Wilson writes: Simon> - Message from John Stoffel - Simon> Date: Sun, 28 Nov 2021 21:37:12 -0500 Simon> From: John Stoffel Simon> Subject: Re: Logging silence Simon> To: si...@simonandkate.net Simon> Cc: postfix-users@postfix.org Simon> "Simon" == Simon Wilson writes: Simon> I feel like I'm missing something really obvious here... :( Simon> Multiple RedHat8 servers, Postfix configured on all of them for Simon> internal network mail server (primarily server log updates, Simon> etc. to admin). Simon> Have you restarted syslog (or syslog-ng, or rsyslog, etc) on the Simon> problematic server? Simon> Yes, the server has been rebooted *many* times, and I have also Simon> tried restarting rsyslog. selinux running on there? Is it impossible to just clone one of the good systems and replace this problematic one? Compare the installed packages between the systems, along with the 'systemctl' output to look for differences. More details would help us help you. John I worked it out. journald.conf was set to MaxLevelStore=notice, so it wasn't just postfix not logging, just that was the symptom picked up. I really was missing something obvious. Now I need to work back to see how / who changed that. Thank you for support. Simon ___ Simon Wilson
Re: Logging silence
>>>>> "Simon" == Simon Wilson writes: Simon> - Message from John Stoffel - Simon>Date: Sun, 28 Nov 2021 21:37:12 -0500 Simon>From: John Stoffel Simon> Subject: Re: Logging silence Simon> To: si...@simonandkate.net Simon> Cc: postfix-users@postfix.org Simon> "Simon" == Simon Wilson writes: Simon> I feel like I'm missing something really obvious here... :( Simon> Multiple RedHat8 servers, Postfix configured on all of them for Simon> internal network mail server (primarily server log updates, Simon> etc. to admin). Simon> Have you restarted syslog (or syslog-ng, or rsyslog, etc) on the Simon> problematic server? Simon> Yes, the server has been rebooted *many* times, and I have also Simon> tried restarting rsyslog. selinux running on there? Is it impossible to just clone one of the good systems and replace this problematic one? Compare the installed packages between the systems, along with the 'systemctl' output to look for differences. More details would help us help you. John
Re: Logging silence
- Message from John Stoffel - Date: Sun, 28 Nov 2021 21:37:12 -0500 From: John Stoffel Subject: Re: Logging silence To: si...@simonandkate.net Cc: postfix-users@postfix.org "Simon" == Simon Wilson writes: Simon> I feel like I'm missing something really obvious here... :( Simon> Multiple RedHat8 servers, Postfix configured on all of them for Simon> internal network mail server (primarily server log updates, Simon> etc. to admin). Have you restarted syslog (or syslog-ng, or rsyslog, etc) on the problematic server? Yes, the server has been rebooted *many* times, and I have also tried restarting rsyslog. Simon - End message from John Stoffel - ___ Simon Wilson M: 0400 12 11 16
Re: Logging silence
> "Simon" == Simon Wilson writes: Simon> I feel like I'm missing something really obvious here... :( Simon> Multiple RedHat8 servers, Postfix configured on all of them for Simon> internal network mail server (primarily server log updates, Simon> etc. to admin). Have you restarted syslog (or syslog-ng, or rsyslog, etc) on the problematic server? Simon> On all of them bar one, I get relevant logging in /var/log/maillog. On Simon> the one - maillog remains empty, even though mail is being sent OK. Simon> I've diff-compared main.cf, master.cf and rsyslog.conf on one that Simon> logs to maillog and the one that doesn't. Main.cf has a different Simon> hostname specified, master.cf is identical. Both rsyslogd.conf have Simon> the following setup for mail: Simon> *.info;mail.none;authpriv.none;cron.none/var/log/messages Simon> mail.* -/var/log/maillog Simon> Yet nothing gets logged to /var/log/maillog on ONE of them. Mail is Simon> getting sent and received from the server. Simon> Logging is working for other services. Simon> journalctl -u postfix shows (at the end): Simon> Jan 09 03:43:06 emp80.simonandkate.lan postfix/pickup[3162096]: Simon> 35E30201E928: uid=0 from= Simon> Jan 09 03:43:06 emp80.simonandkate.lan postfix/cleanup[3169954]: Simon> 35E30201E928: Simon> message-id=<20210108174306.35e30201e...@emp80.simonandkate.lan> Simon> Jan 09 03:43:06 emp80.simonandkate.lan postfix/qmgr[1989]: Simon> 35E30201E928: from=, size=102096, nrcpt=1 Simon> (queue active) Simon> Jan 09 03:43:06 emp80.simonandkate.lan postfix/smtp[3169963]: Simon> 35E30201E928: to=, Simon> relay=192.168.1.235[192.168.1.235]:25, delay> Simon> Jan 09 03:43:06 emp80.simonandkate.lan postfix/qmgr[1989]: Simon> 35E30201E928: removed Simon> -- Reboot -- Simon> Jan 18 02:05:45 emp80.simonandkate.lan postfix/qmgr[1958]: warning: Simon> backward time jump detected -- slewing clock Simon> Jan 18 02:11:25 emp80.simonandkate.lan postfix/qmgr[1958]: warning: Simon> backward time jump recovered -- back to normality Simon> -- Reboot -- Simon> Jan 25 03:04:36 emp80.simonandkate.lan postfix/qmgr[1968]: warning: Simon> backward time jump detected -- slewing clock Simon> Jan 25 03:08:02 emp80.simonandkate.lan postfix/qmgr[1968]: warning: Simon> backward time jump recovered -- back to normality Simon> -- Reboot -- Simon> Mar 07 05:35:51 emp80.simonandkate.lan postfix/qmgr[1965]: warning: Simon> backward time jump detected -- slewing clock Simon> Mar 07 05:39:01 emp80.simonandkate.lan postfix/qmgr[1965]: warning: Simon> backward time jump recovered -- back to normality Simon> -- Reboot -- Simon> Apr 11 05:04:12 emp80.simonandkate.lan postfix/qmgr[2009]: warning: Simon> backward time jump detected -- slewing clock Simon> Apr 11 05:11:53 emp80.simonandkate.lan postfix/qmgr[2009]: warning: Simon> backward time jump recovered -- back to normality Simon> -- Reboot -- Simon> Jun 07 22:40:56 emp80.simonandkate.lan postfix/qmgr[1975]: warning: Simon> backward time jump detected -- slewing clock Simon> Jun 07 22:49:31 emp80.simonandkate.lan postfix/qmgr[1975]: warning: Simon> backward time jump recovered -- back to normality Simon> -- Reboot -- Simon> Nov 04 17:58:53 emp80.simonandkate.lan postfix/qmgr[2047]: warning: Simon> backward time jump detected -- slewing clock Simon> Nov 04 18:00:01 emp80.simonandkate.lan postfix/qmgr[2047]: warning: Simon> backward time jump recovered -- back to normality Simon> ...where as can be seen it was logging OK in January, then it stopped. Simon> Permissions on the log file: Simon> -rw--- 1 root root0 Nov 28 03:27 maillog Simon> What am I missing?? Simon> -- Simon> Simon Wilson
