Hi Philippe, There is no 'proper' way to kill the running slon daemons, all you can do is send them a kill signal. If your server is shutting down, it will kill the slon daemons without you having to do anything. When any of the servers in your cluster (master or slave) shut down you will see cannot connect errors in the slon daemons running on the other machine. All you need to do on start up of the server is restart all the slon daemons that were running on it before the shut down. How many this is, will depend if you are running some slon daemons on each server, or all from one central place. The lines will be of the form slon -d1 <clustername> "dbname=<dbname> user=<pguser> host=<hostname>" >> logfile 2>&1 & Watch the log files and look for any errors which should be self explanatory, such as cannot connect. You definitely do not have to re subscribe the sets again. Hope this helps, Vicki
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brinon Philippe Sent: 20 November 2006 13:53 To: [email protected] Cc: Daniels Philippe Subject: [Slony1-general] shutdown/startup of a master Slony server Hi, everybody, I am a new comer to Slony product and to Slony Mailing List. In my company (BRGM, France), Slony has been installed and it is perfectly running. However, we are sure we have not understood everything. Our configuration is very simple. It consists of a master database installed on a master server and 10 slave replicas installed on 10 servers, in a two level structure. We have installed all our processes on the master server. A first problem: What if a server has to be stopped (let's say to increase the RAM... or to add a new disk...) ? If it is a "slave server", a stop seems not to have much consequence. On the other hand, what if I stop the master server? What should I specify in the automatic shutdown of the server in order to make it stop properly (considering SLONY processes)? What should I specify in the automatic startup of the server in order to restart all the processes and to re-establish the normal communication between master and slaves? Presently, should a start-up of the master occur, we re-subscribe each slave, which means that the full recreation of the copies is performed. Is this compulsory? I would be very pleased if you could help me or tell me if there is a document available dealing with my problems. Best regards, Philippe Brinon Le contenu de cet e-mail et de ses pièces jointes est destiné à l'usage exclusif du (des) destinataire(s) expressément désigné(s) comme tel(s). En cas de réception de cet e-mail par erreur, le signaler à son expéditeur et ne pas en divulguer le contenu. L'absence de virus a été vérifié à l'émission du message. Il convient néanmoins de vérifier l'absence de corruption à sa réception. The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies. eSafe scanned this email for viruses, vandals and malicious content. This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorized signatory.
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
