Hi Steve
Thank you for your reply I guess that would be /etc/slony1-94/slon.conf But see what confuses me is this. All slonik* perl script reference this slonik_drop_node:$CONFIG_FILE = '/etc/slony1-94/slon_tools.conf'; I guess then /etc/slony1-94/slon_tools.conf should be referencing /etc/slony1-94/slon.conf Will try that and see how that goes Thanks Armand On Nov 16, 2015, at 9:52 PM, Steve Singer <ssin...@ca.afilias.info> wrote: > On 11/16/2015 10:32 PM, Armand Pirvu (home) wrote: >> Hi >> >> Please pardon the length of this email but I felt it is best to give a >> global view >> >> I was looking at slonik for a project. >> All the setup info, tutorials etc etc seems to vary >> >> http://raghavt.blogspot.com/2012/07/simple-slony-i-replication-setup.html >> and >> http://www.linuxjournal.com/article/7834 >> > >> >> >> /usr/pgsql-9.4/bin/slon_start -c /etc/slony1-94/slon_tools.conf 1 & >> fails to start >> > > I think the config file should be to slon config file not a slon_tools.conf > > ie the format is > > cluster_name=myrep > pid_file='/opt/PostgreSQL/9.1/data/master_slon.pid' > conn_info='host=localhost dbname=master user=postgres port=5432' > > http://www.slony.info/documentation/2.2/runtime-config.html > > Or see slon_node.conf.sample which I think is included with the perl tools > > > >> 2015-11-16 20:59:50 CST ERROR syntax error in file >> "/etc/slony1-94/slon_tools.conf" line 13, near end of line >> 2015-11-16 20:59:50 CST CONFIG main: slon version 2.2.4 starting up >> usage: /usr/pgsql-9.4/bin/slon [options] clustername conninfo >> >> Options: >> -h print usage message and exit >> -v print version and exit >> -d <debuglevel> verbosity of logging (1..4) >> -s <milliseconds> SYNC check interval (default 10000) >> -t <milliseconds> SYNC interval timeout (default 60000) >> -o <milliseconds> desired subscriber SYNC processing time >> -g <num> maximum SYNC group size (default 6) >> -c <num> how often to vacuum in cleanup cycles >> -p <filename> slon pid file >> -f <filename> slon configuration file >> -a <directory> directory to store SYNC archive files >> -x <command> program to run after writing archive file >> -q <num> Terminate when this node reaches # of SYNCs >> -r <num> # of syncs for -q option >> -l <interval> this node should lag providers by this interval >> >> >> So what gives ? How do I debug, fix , move forward ? Aside the doc which >> maybe I missed , has an example which yes it works but it not going in all >> these details, any other examples and so on ? >> >> >> Many thanks >> Armand >> >> >> >> _______________________________________________ >> Slony1-general mailing list >> Slony1-general@lists.slony.info >> http://lists.slony.info/mailman/listinfo/slony1-general
_______________________________________________ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general