On 02/26/2016 04:30 PM, Rob Brucks wrote:
> I have Slony 2.2.4 installed on Centos 6.7 x86_64 from the PGDG 9.3 repo.
>
> No matter what settings I set in the slony.conf file, I cannot get the
> Slon daemon to include timestamps in the slon log output.
>

What output do you get if you start slon without a config file.

When I start slon  I get

slon  test 'host=localhost port=5432 dbname=test2'
2016-02-29 09:24:42 EST CONFIG main: slon version 2.3.0 starting up
2016-02-29 09:24:42 EST INFO   slon: watchdog process started
2016-02-29 09:24:42 EST CONFIG slon: watchdog ready - pid = 25047
2016-02-29 09:24:42 EST CONFIG slon: worker process created - pid = 25048
2016-02-29 09:24:42 EST CONFIG main: Integer option vac_frequency = 3
2016-02-29 09:24:42 EST CONFIG main: Integer option log_level = 0
2016-02-29 09:24:42 EST CONFIG main: Integer option sync_interval = 2000
2016-02-29 09:24:42 EST CONFIG main: Integer option 
sync_interval_timeout = 10000


the timestamps are printed.


What if you leave all of
log_timestamp, log_timestamp_format out of the config file.





> I've tried changing both "log_timestamp" and "log_timestamp_format"
> settings in various combinations ("true","yes","1", etc.; even "no" in
> the hopes it was mistakenly coded backwards) without any success.
>
> I know that the Slon daemon is using this config file because I have the
> DB connection set in it and if I change it then it fails to connect.
>
> The lack of timestamps makes it incredibly difficult to diagnose
> problems after they occur.
>
> I have tried enabling syslog logging, but the syslog logging doesn't
> include all the output that goes to the slon log.
>
> Any suggestions to get timestamps working would be greatly appreciated!
>
> Thanks,
> Rob
>
>
> _______________________________________________
> Slony1-bugs mailing list
> Slony1-bugs at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-bugs
>