You seem to be bombarding this list with similar messages!  Slow down ...

The message means that postgres is shutting down, not slony.

Fix that first, probably using pg_ctl.  $ pg_ctl --help shows the options.

When postgres is up and running, on both master and slave databases,
start your slony processes.

To stop slony, you can kill the slon processes.  Googling for "stop
slon" will find you more information.



--
Ian.


On Mon, Jul 20, 2009 at 10:08 AM, roctaiwan<nettreeinc at gmail.com> wrote:
>
> I was trying to start my slon cluster and following messages says:
>
>
> -bash-3.2$ slon sql_cluster "dbname=contactdb user=postgres"
> 2009-07-20 17:02:08 CST CONFIG main: slon version 1.2.15 starting up
> 2009-07-20 17:02:08 CST DEBUG2 slon: watchdog process started
> 2009-07-20 17:02:08 CST DEBUG2 slon: watchdog ready - pid = 12620
> 2009-07-20 17:02:08 CST FATAL  main: Cannot connect to local database -
> FATAL:  the database system is shutting down
>  - sleep 10s
> 2009-07-20 17:02:08 CST DEBUG2 slon: worker process created - pid = 12621
> 2009-07-20 17:02:18 CST DEBUG2 slon_retry() from pid=12621
> 2009-07-20 17:02:18 CST DEBUG1 slon: retry requested
> 2009-07-20 17:02:18 CST DEBUG2 slon: notify worker process to shutdown
> 2009-07-20 17:02:18 CST DEBUG2 slon: child terminated status: 0; pid: 12621,
> current worker pid: 12621
> 2009-07-20 17:02:18 CST DEBUG1 slon: restart of worker
> 2009-07-20 17:02:18 CST CONFIG main: slon version 1.2.15 starting up
> 2009-07-20 17:02:18 CST DEBUG2 slon: watchdog process started
> 2009-07-20 17:02:18 CST DEBUG2 slon: watchdog ready - pid = 12620
> 2009-07-20 17:02:18 CST DEBUG2 slon: worker process created - pid = 12649
> 2009-07-20 17:02:18 CST FATAL  main: Cannot connect to local database -
> FATAL:  the database system is shutting down
>  - sleep 10s
> 2009-07-20 17:02:28 CST DEBUG2 slon_retry() from pid=12649
> 2009-07-20 17:02:28 CST DEBUG1 slon: retry requested
> 2009-07-20 17:02:28 CST DEBUG2 slon: notify worker process to shutdown
> 2009-07-20 17:02:28 CST DEBUG2 slon: child terminated status: 0; pid: 12649,
> current worker pid: 12649
> 2009-07-20 17:02:28 CST DEBUG1 slon: restart of worker
> 2009-07-20 17:02:28 CST CONFIG main: slon version 1.2.15 starting up
> 2009-07-20 17:02:28 CST DEBUG2 slon: watchdog process started
> 2009-07-20 17:02:28 CST DEBUG2 slon: watchdog ready - pid = 12620
> 2009-07-20 17:02:28 CST DEBUG2 slon: worker process created - pid = 12651
> 2009-07-20 17:02:28 CST FATAL  main: Cannot connect to local database -
> FATAL:  the database system is shutting down
>  - sleep 10s
> 2009-07-20 17:02:33 CST DEBUG1 slon: shutdown requested
> 2009-07-20 17:02:33 CST DEBUG2 slon: notify worker process to shutdown
> 2009-07-20 17:02:33 CST DEBUG2 slon_retry() from pid=12651
> 2009-07-20 17:02:33 CST DEBUG1 slon: retry requested
> 2009-07-20 17:02:33 CST DEBUG2 slon: notify worker process to shutdown
> 2009-07-20 17:02:33 CST DEBUG1 slon: shutdown requested
> 2009-07-20 17:02:33 CST DEBUG2 slon: notify worker process to shutdown
> 2009-07-20 17:02:33 CST FATAL  main: write to worker pipe failed -(9) Bad
> file descriptor
> 2009-07-20 17:02:33 CST DEBUG2 slon: exit(-1)
> (I press ctrl+c to stop it)
> -bash-3.2$
>
>
> I seems like my server is shutting down? Does it mean my Postgresql or Slony
> is shutting down? shutting down meaning it's not down yet and is still
> trying to shut down? how can i fix it?
>
>
>
> --
> View this message in context: http://www.nabble.com/Could-not-start-slon-cluster-tp24566272p24566272.html
> Sent from the Slony-I -- General mailing list archive at Nabble.com.
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>