[Dovecot] Reduce logging auth-worker
Hello Timo
We would like to reduce the logging by increasing severity, we don't use syslog since we use
log_path = /var/log/dovecot/pop3.log
Is there a way auth-worker can be made to log warn|error instead of info?
Constantly 1/5th of the log file is filled with auth-work info connecting to mysql socket, which we do not need to see unless, well, we need to see it either via debug, or if there is a problem, I know this can be done from syslog, but we prefer not to use syslog, and the wiki does not indicate it can be done?
Niki
Am 23.03.2013 02:31, schrieb Nick Edwards:
Hello Timo
We would like to reduce the logging by increasing severity, we don't use syslog since we use
log_path = /var/log/dovecot/pop3.log
why?
Is there a way auth-worker can be made to log warn|error instead of info?
Constantly 1/5th of the log file is filled with auth-work info connecting to mysql socket, which we do not need to see unless, well, we need to see it either via debug, or if there is a problem, I know this can be done from syslog, but we prefer not to use syslog, and the wiki does not indicate it can be done?
but that is exactly why syslog exists instead re-invent the wheel
[root@mail:~]$ cat /etc/rsyslog.conf | grep database :msg, contains, "Connected to database dbmail" ~
As usual you post with nothing helpful to say, I wont dignify your regular trolling by commenting any further
On 3/23/13, Reindl Harald h.reindl@thelounge.net wrote:
Am 23.03.2013 02:31, schrieb Nick Edwards:
Hello Timo
We would like to reduce the logging by increasing severity, we don't use syslog since we use
log_path = /var/log/dovecot/pop3.log
why?
Is there a way auth-worker can be made to log warn|error instead of info?
Constantly 1/5th of the log file is filled with auth-work info connecting to mysql socket, which we do not need to see unless, well, we need to see it either via debug, or if there is a problem, I know this can be done from syslog, but we prefer not to use syslog, and the wiki does not indicate it can be done?
but that is exactly why syslog exists instead re-invent the wheel
[root@mail:~]$ cat /etc/rsyslog.conf | grep database :msg, contains, "Connected to database dbmail" ~
[root@mail:~]$ cat /etc/rsyslog.conf | grep database :msg, contains, "Connected to database dbmail" ~
was not helpful? well, not if you insist in not use syslog
maybe you should explain why not using syslog as everybody else to taken serious because "i do not want" in case where it is clear you need is no reason
Am 23.03.2013 02:58, schrieb Nick Edwards:
As usual you post with nothing helpful to say, I wont dignify your regular trolling by commenting any further
On 3/23/13, Reindl Harald h.reindl@thelounge.net wrote:
Am 23.03.2013 02:31, schrieb Nick Edwards:
Hello Timo
We would like to reduce the logging by increasing severity, we don't use syslog since we use
log_path = /var/log/dovecot/pop3.log
why?
Is there a way auth-worker can be made to log warn|error instead of info?
Constantly 1/5th of the log file is filled with auth-work info connecting to mysql socket, which we do not need to see unless, well, we need to see it either via debug, or if there is a problem, I know this can be done from syslog, but we prefer not to use syslog, and the wiki does not indicate it can be done?
but that is exactly why syslog exists instead re-invent the wheel
[root@mail:~]$ cat /etc/rsyslog.conf | grep database :msg, contains, "Connected to database dbmail" ~
On Sat, 2013-03-23 at 03:28 +0100, Reindl Harald wrote:
maybe you should explain why not using syslog as everybody else
Why do you think you speak for everybody else? Because you sure as hell don't, so stop pretending to.
WTF is in the air this week, it seems to contain a few self proclaimed god's who apparently know what everyone else does, or, at least thought they did.
I too have always used dovecot logging to specific files for over a decade, I know plenty of others too.
Anyone who knows anything about syslog on large production servers knows avoiding it is best practice, it's also about the only thing DJB and I ever agreed on.
But back on topic, I think it would be an excellent option, less work for dovecot, in forseeable future though, editing source would be the way to go.
Am 23.03.2013 08:13, schrieb Noel Butler:
On Sat, 2013-03-23 at 03:28 +0100, Reindl Harald wrote:
maybe you should explain why not using syslog as everybody else
Why do you think you speak for everybody else? Because you sure as hell don't, so stop pretending to. WTF is in the air this week, it seems to contain a few self proclaimed god's who apparently know what everyone else does, or, at least thought they did
blablablanla
I too have always used dovecot logging to specific files for over a decade, I know plenty of others too
maybe you should RTFM, this is nothing you can't do easily with rsyslog and much more felxible as with any program option
# systemd-logind not in /var/log/messages :programname, isequal, "systemd-logind" -/var/log/secure :programname, isequal, "systemd-logind" ~
# log dhcpd in own file :programname, isequal, "dhcpd" -/var/log/dhcpd.log :programname, isequal, "dhcpd" ~ :programname, isequal, "vmnet-dhcpd" -/var/log/dhcpd.log :programname, isequal, "vmnet-dhcpd" ~
# log hostapd in own file :programname, isequal, "hostapd" -/var/log/hostapd.log :programname, isequal, "hostapd" ~
Anyone who knows anything about syslog on large production servers knows avoiding it is best practice, it's also about the only thing DJB and I ever agreed on
blablablanla
in large environments you even have your syslogd logging on a remote machine for auditing and security reasons
On Sat, 2013-03-23 at 10:57 +0100, Reindl Harald wrote:
_deleted usual drivell_
Anyone who knows anything about syslog on large production servers knows avoiding it is best practice, it's also about the only thing DJB and I ever agreed on
blablablanla
in large environments you even have your syslogd logging on a remote machine for auditing and security reasons
it shows you have never worked for a large ISP, or probably a small one at that, anyway going back to my usual not reading your trash talk.
Oh yeah, Nick, +1 to your previous.
Reindl Harald skrev den 2013-03-23 03:28:
maybe you should explain why not using syslog as everybody else to taken serious because "i do not want" in case where it is clear you need is no reason
blame apache for not using syslog by default, sure just show a patch to fix it :)
if you cant, why care on trying ?
you don't get it do you, troll, since your name is not Timo and you have no fucking idea about our requirements, or dovecot's code, STFU, you are contributing NOTHING, like always, so do not bother with this thread because you are not helpful, if we could use your beloved syslog, we would, but it again I'll say it because you have a serious comprehension problem, it does not suite our needs, and because of your whitenoise Timo or others who might help wont probably bother with this thread, but you're an expert at fucking it over for others.
you are nothing but a bored, arrogant and caustic person, who feels the need to berate others without knowing all the facts, this is evident by the many mailing lists you are subscribed to.
*PLONKED*
On 3/23/13, Reindl Harald h.reindl@thelounge.net wrote:
[root@mail:~]$ cat /etc/rsyslog.conf | grep database :msg, contains, "Connected to database dbmail" ~
was not helpful? well, not if you insist in not use syslog
maybe you should explain why not using syslog as everybody else to taken serious because "i do not want" in case where it is clear you need is no reason
Am 23.03.2013 02:58, schrieb Nick Edwards:
As usual you post with nothing helpful to say, I wont dignify your regular trolling by commenting any further
On 3/23/13, Reindl Harald h.reindl@thelounge.net wrote:
Am 23.03.2013 02:31, schrieb Nick Edwards:
Hello Timo
We would like to reduce the logging by increasing severity, we don't use syslog since we use
log_path = /var/log/dovecot/pop3.log
why?
Is there a way auth-worker can be made to log warn|error instead of info?
Constantly 1/5th of the log file is filled with auth-work info connecting to mysql socket, which we do not need to see unless, well, we need to see it either via debug, or if there is a problem, I know this can be done from syslog, but we prefer not to use syslog, and the wiki does not indicate it can be done?
but that is exactly why syslog exists instead re-invent the wheel
[root@mail:~]$ cat /etc/rsyslog.conf | grep database :msg, contains, "Connected to database dbmail" ~
From: Nick Edwards nick.z.edwards@gmail.com To: dovecot@dovecot.org Sent: Sunday, 24 March 2013, 3:42 Subject: Re: [Dovecot] Reduce logging auth-worker you don't get it do you, troll, since your name is not Timo and you have no fucking idea about our requirements, or dovecot's code, STFU, you are contributing NOTHING, like always, so do not bother with this thread because you are not helpful, if we could use your beloved syslog, we would, but it again I'll say it because you have a serious comprehension problem, it does not suite our needs, and because of your whitenoise Timo or others who might help wont probably bother with this thread, but you're an expert at fucking it over for others.
you are nothing but a bored, arrogant and caustic person, who feels the need to berate others without knowing all the facts, this is evident by the many mailing lists you are subscribed to.
*PLONKED*
Nick,
I don't think it's appropriate to use such language. We are all responsible people here trying to get answers to problems/questions.
I am sure you know your stuff, i don't doubt that.
And I am not trying to start a flame war :-)
Peace,
s.
"I merely function as a channel that filters music through the chaos of noise"
- Vangelis
On 23.3.2013, at 3.31, Nick Edwards nick.z.edwards@gmail.com wrote:
We would like to reduce the logging by increasing severity, we don't use syslog since we use
log_path = /var/log/dovecot/pop3.log
Is there a way auth-worker can be made to log warn|error instead of info?
Constantly 1/5th of the log file is filled with auth-work info connecting to mysql socket, which we do not need to see unless, well, we need to see it either via debug, or if there is a problem, I know this can be done from syslog, but we prefer not to use syslog, and the wiki does not indicate it can be done?
Well, you could do something like:
service auth-worker { executable = auth -w -L -o info_log_path=/dev/null }
Or you could increase process_min_avail so processes wouldn't all the time be created/destroyed and you wouldn't have so many mysql connection messages.
But then again, I can't really think of any use for those messages. LDAP for example doesn't log about it. So removed from v2.2 unless someone gives a good reason for why they should stay: http://hg.dovecot.org/dovecot-2.2/rev/33e78edac8f5
participants (6)
-
Benny Pedersen
-
Nick Edwards
-
Noel Butler
-
Reindl Harald
-
Spyros Tsiolis
-
Timo Sirainen