[Bucardo-general] Invalid log level

[Greg Sabino Mullane]

> ./bucardo start
> Checking for existing processes
> Invalid log_level! (INFO)

Well, that is interesting. We don't use INFO at all - that's a Postgres thing. 
It must be getting set from somewhere: the main culprits are the bucardo_config 
table and the .bucardorc file. When you startup Bucardo, the log file will have 
a section starting with "MCP Bucardo config:". Go down a few lines and look 
for log_level and see what it is set at there. Also check the bucardorc files: 
Bucardo will first look for a .bucardorc file in the current direectory, then 
for $ENV{HOME}/.bucardorc, then /etc/bucardorc. See if there is an errant 
log_level = INFO inside any of those.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20160606/78533e5f/attachment.sig>