> ./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 [email protected]
End Point Corporation
PGP Key: 0x14964AC8
signature.asc
Description: PGP signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
