slony on windows xp

hello,

im a complete beginner to enterprisedb. i am working on a special project in school and tasked to make a prototype distributed database. im using slony I in enterprisedb postgres 8.2. i created a 3 node cluster running on the same computer using localhost as the server just to test the software. the problem is that i cant start the slony engine. i successfully executed this command "slon -regservice Slony-I" on command prompt in the directory c:\enterprisedb\postgres\8.2\bin>.

however, when i tried to execute these commands
" C:\EnterpriseDB\Postgres\8.2\bin> slon -addengine Slony-I C:\enterprisedb\postgres\master.conf
C:\EnterpriseDB\Postgres\8.2\bin> slon -addengine Slony-I C:\enterprisedb\postgres\slave1.conf
C:\EnterpriseDB\Postgres\8.2\bin> slon -addengine Slony-I C:\enterprisedb\postgres\slave2.conf"

these resulted to errors:

C:\EnterpriseDB\Postgres\8.2\bin>slon -addengine Slony-I C:\enterprisedb\postgres\master.conf
File 'C:\slony\master.conf' could not be opened: 3

i know this sounds stupid: how can i make a master.conf file?pls give me some examples.

i badly need the help of anybody whose knowledgeable on this matter.

Here is a sample master.conf file.

The conf file basically contains some configuration parameters for a cluster node slon process.

You may need to update the database connection parameters based on you system configuration.

# Sets how many cleanup cycles to run before a vacuum is done.
# Range: [0,100], default: 3
#vac_frequency=3

# Debug log level (higher value ==> more output).  Range: [0,4], default 0
#log_level=0

# Check for updates at least this often in milliseconds.
# Range: [10-60000], default 100
#sync_interval=100

# Maximum amount of time in milliseconds before issuing a SYNC event, 
# This prevents a possible race condition in which the action sequence 
# is bumped by the trigger while inserting the log row, which makes 
# this bump is immediately visible to the sync thread, but 
# the resulting log rows are not visible yet.  If the sync is picked 
# up by the subscriber, processed and finished before the transaction 
# commits, this transaction's changes will not be replicated until the 
# next SYNC.  But if all application activity suddenly stops, 
# there will be no more sequence bumps, so the high frequent -s check 
# won't detect that.  Thus, the need for sync_interval_timeout.
# Range: [0-120000], default 1000
#sync_interval_timeout=1000

# Maximum number of SYNC events to group together when/if a subscriber
# falls behind.  SYNCs are batched only if there are that many available 
# and if they are contiguous. Every other event type in between leads to 
# a smaller batch.  And if there is only one SYNC available, even -g60 
# will apply just that one. As soon as a subscriber catches up, it will
# apply every single SYNC by itself.
# Range:  [0,100], default: 6
#sync_group_maxsize=6

# If this parameter is 1, messages go both to syslog and the standard 
# output. A value of 2 sends output only to syslog (some messages will 
# still go to the standard output/error).  The default is 0, which means 
# syslog is off.  
# Range:  [0-2], default: 0
#syslog=0

# If true, include the process ID on each log line.  Default is false.
#log_pid=false

# If true, include the timestamp on each log line.  Default is true.
#log_timestamp=true

# A strftime()-conformant format string for use with log timestamps.
# Default is '%Y-%m-%d %H:%M:%S %Z'
#log_timestamp_format='%Y-%m-%d %H:%M:%S %Z'

# Where to write the pid file.  Default:  no pid file
#pid_file='/path/to/your/pidfile'

# Sets the syslog "facility" to be used when syslog enabled.  Valid 
# values are LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.
#syslog_facility=LOCAL0

# Set the clsuter name that this instance of slon is running against
# default is to read it off the command line
cluster_name='slony_sample'

# Set slon's connection info, default is to read it off the command line
conn_info='dbname=postgres host=localhost port=5432 user=postgres'

# maximum time planned for grouped SYNCs
# If replication is behind, slon will try to increase numbers of
# syncs done targetting that they should take this quantity of
# time to process. in ms
# Range [10000,600000], default 60000. 
#desired_sync_time=60000

# Execute the following SQL on each node at slon connect time
# useful to set logging levels, or to tune the planner/memory
# settings.  You can specify multiple statements by seperating
# them with a ;
#sql_on_connection="SET log_min_duration_statement TO '1000';"

Please also glance through the pgAdmin3 documentation, it has built-in support for Slony-I replication.

thanks for the help. i got it.

however, i still got one problem.

i tried the slony example from the pgAdmin III documentation. i tried using pgbench.
i successfully set up three nodes and designated one database as the provider. the other two as slaves. i was able to set up subscriptions. the other two nodes successfully copied the contents of the tables belonging to the replication set from the provider.

i need to know how can i propagate changes in the tables from the provider node to the subscriber nodes.

there were four tables namely accounts,history,tellers,branches.(i successfully replicated these tables in the three nodes including its contents.)

i inserted a new entry in the history table in the provider node. however, this new entry was not propagated to the two slave nodes.

is there a way to update the slave nodes based on the changes done on the provider node? can i adjust the time interval to execute propagation of updates to the slave nodes?

pls help me on this matter.

hi,

i have also same issue

02/12/2007 03:12:16 Subject: Re:slony on windows xp

--------------------------------------------------------------------------------

thanks for the help. i got it.

after slony configuration in windows

i need to know how can i propagate changes in the tables from the provider node to the subscriber nodes.

there were four tables namely accounts,history,tellers,branches.(i successfully replicated these tables in the three nodes including its contents.)

i inserted a new entry in the history table in the provider node. however, this new entry was not propagated to the two slave nodes.

please help me

Thank you

Hi,

I am new and I am finding problem while running below mention script in windows xp.

define Clus WinReplica;
define Master 1;
define Slave 10;
cluster_name=@Clus;

logdir='/slony/'
log_level=0
syslog=1
log_pid=true
log_timestamp=true
log_timestamp_format='%Y-%m-%d %H:%M:%S %Z'
pid_file='/slony/pidfile'
#desired_sync_time=60000
#sql_on_connection="SET log_min_duration_statement TO '1000';"

node @Master admin conn_info='host=localhost dbname=Master user=postgres password=postgres port=5432'
node @Slave admin conn_info='host=localhost dbname=Slave user=postgres password=postgres port=5432'

#Cluster Set
init cluster (id=1,comment='Master Node')

#Create Set
create set (id = 1, origin=@Master, comment='tables')

#Create Sequence
set add sequence (set id=1, origin=@Master, id=1, fully qualified name = 'public.seq_1', comment = 'Sequence')

#Add Tables
set add table (set id=1, origin=@Master, id=3, fully qualified name = 'public.address', comment='Table')

#Store Node
store node (id = @Slave, comment = 'Slave Node 10')

#Store Path
store path (server=@Master, client=@Slave, conninfo='host=localhost port=5432 dbname=Master user=postgres password=postgres')
store path (server=@Slave, client=@Master, conninfo='host=localhost port=5432 dbname=Slave user=postgres password=postgres')

#Store Listen
store listen (origin = @Master, Provider = @Master, receiver = @Slave)
store listen (origin = @Slave, Provider = @Slave, receiver = @Master)

#Subscribe Set
subscribe set (id=1, provider=@Master, receiver=@Slave, forward = no)

-------------------------------------------------------------------------------------------------------

I am adding script at command prompt using and getting msg

C:\Program Files\PostgreSQL\8.2\bin\slon -addengine c:\slony\secondScript.conf

C:\Slony>"C:\Program Files\PostgreSQL\8.2\bin\"slon -addengine c:\slony\secondScript.conf
Engine added.
NOTE! You need to restart the Slony service before this takes effect.

To restart the Slony Service I am stopping server and start service again, I hope it is correct way if not please let me know how to do it.

-------------------------------------------------
The problem what I am having :
-------------------------------------------------

While checking in PGADMIN III I can't see any changes are happend in Master of Slave DB. It is not creating Cluster (WinReplica) and rest of script function?

To know is anything is wrong in my script I don't know log file is not created.

Please let me know how to debug this correct me is anything wrong in my script.

Thanks in Advance.

Tushar

I would like to know is anything wrong in my script

ezra_undag wrote:

thanks for the help. i got it.

however, i still got one problem.

i tried the slony example from the pgAdmin III documentation. i tried using pgbench.
i successfully set up three nodes and designated one database as the provider. the other two as slaves. i was able to set up subscriptions. the other two nodes successfully copied the contents of the tables belonging to the replication set from the provider.

i need to know how can i propagate changes in the tables from the provider node to the subscriber nodes.

there were four tables namely accounts,history,tellers,branches.(i successfully replicated these tables in the three nodes including its contents.)

i inserted a new entry in the history table in the provider node. however, this new entry was not propagated to the two slave nodes.

is there a way to update the slave nodes based on the changes done on the provider node? can i adjust the time interval to execute propagation of updates to the slave nodes?

pls help me on this matter.

Did you start the slon service in services.msc?

Here's the process, you create the replication set
Create the services
Start the services
Subscribe

After that, you should be up and running.

Can i have reply pls

This message was edited 1 time. Last update was at 24 Oct 2009 18:06:02

Can i have reply pls

Did you try Scott's suggestion?
Below are the steps:
1. Create Slony Services, using following command:

2. Start the services, using following command:

Subscribe the set using pgAdmin3.

Thanks for reply,

I have tried net stop and start but due to some reason my cluster is not getting created.

define Clus WinReplica;
define Master 1;
define Slave 10;
cluster_name=@Clus;

node @Master admin conn_info='host=localhost dbname=Master user=postgres password=postgres port=5432';
node @Slave admin conn_info='host=localhost dbname=Slave user=postgres password=postgres port=5432' ;

#Cluster Set
init cluster (id=1,comment='Master Node') ;

So do you think some thing wrong in my script ?
[img]
If you can send me sample script.

Will anybody will be able to help me for writting script (If it is in part also it is fine).

Result what I want to achive is that I want to create cluster in my windows xp pc using script then do replication between two machine.

It will be appricate someone please help me for same.

Have you looked in the eventviewer for any logs?

If you have some, please copy all of the slony lines and upload them here.

Thanks