On 3/26/2018 6:02 AM, Wietse Venema wrote:
Viktor Dukhovni:
On Mar 25, 2018, at 11:59 PM, deoren <postfix-us...@whyaskwhy.org> wrote:
Is there an option somewhere to change that, so that all messages logged as as
a result of the debug_peer_* options are set at debug syslog level instead?
No.
Do not turn on debug_peer_* logging for routine usage.
Wietse
Hi Wietse,
Thank you for the reply.
I understand that it's not a good idea to use it for routine usage, but
I'm trying to debug a sporadic health check failure that tends to occur
(when it does happen) during very early morning hours. The first failure
usually occurs (+/- 15 minutes or so) around 2:30 am, again around 3:30
am and finally around 4:30 am before things settle out. This occurs
across all three backend relay nodes, usually one or two nodes at a time
(though it has occurred simultaneously against all of them on a few
occasions).
I'm hoping with the verbose details being logged that I can expose the
root cause for final resolution when this happens again. At that point I
plan to disable the use of the debug_peer_* options.
In the meantime (while I wait for it to happen again), this just means
that I'll need to use another means of filtering than the syslog
severity level in order to keep those messages from going into log
destinations that are not really equipped to handle the load. I have
setup a rsyslog filter that matches against the syslog_name value and
it's working well enough for now, though unfortunately the match does
catch some messages that I previously allowed on through to the
downstream nodes (including Graylog).
It would be nice though if there was an option to enable a specific
syslog severity level or messages generated as a result of using the
debug_peer_* options.
Do you accept feature requests here on the list or through another means?
Thank you for your time.
