1

Topic: Cluebringer logs to STDOUT instead of logfile by default

==== Required information ====
- iRedMail version: 0.8.7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Linux/BSD distribution name and version: Debian 7.5
- Related log if you're reporting an issue: /var/log/cbpolicyd.log
====

Hello,

cluebringer logs to STDOUT and floods my console, even if my unmodified conf (snip below) says it should log to a file:

# User to run this daemon as
user=cluebringer
group=cluebringer

# Log level:
# 0 - Errors only
# 1 - Warnings and errors
# 2 - Notices, warnings, errors
# 3 - Info, notices, warnings, errors
# 4 - Debugging
log_level=1

# File to log to instead of stdout
log_file=/var/log/cbpolicyd.log

# Log destination for mail logs...
log_mail=mail@syslog:native

The logfile itself:

# ls -l /var/log/cbpolicyd.log
-rw-rw---- 1 cluebringer adm 0 Jan  4 16:14 /var/log/cbpolicyd.log

Doing a chown cluebringer:cluebringer on the logfile via ssh and restarting postfix-cluebringer results in a working console and a flooded ssh-terminal ... logfile itself still empty.
System has been installed freshly with 0.8.6 a while ago and upgraded to 0.8.7 recently, the problem seems to occure since then.
What do i miss here ?

Thanks for help

2

Re: Cluebringer logs to STDOUT instead of logfile by default

No idea yet. Any related setting in syslog config file?

3

Re: Cluebringer logs to STDOUT instead of logfile by default

Thanks for the fast response. Hmmm. Logging works with rsyslog now, since the new installation. Mail seems to be handled pretty well, but I guess there could be some missing directives for cluebringer ? Since my system is on production - and i don't want to mess it up trying - any suggestion ?

4

Re: Cluebringer logs to STDOUT instead of logfile by default

No idea.