Re: [Postgres-xc-general] coordinator deaths

[Shavais Z. <sh...@gm...>]

Hello,

This looks like it has a lot of helpful stuff in it, it can dissipate a
fair amount of fogginess by providing an example.

One of the things I'll want to do is create a script in /etc/init.d that I
can use with chkconfig, so that things shutdown and start up cleanly on
server reboot.  It seems like it would be nice to have a configuration file
under /etc/config.d, or in /etc/postgresql-xc or something, that the init.d
script would read in order to know everything it needed to know, like
whether or not a gtm is present, and what coordinators and datanodes are
present and where their data directories are, and what their names and
ports are and such.


Shavais

On Tue, Sep 18, 2012 at 6:28 PM, Koichi Suzuki <ko...@in...>wrote:

> Hi,
>
> Maybe coordinator or datanode is trying to register itself doubly to gtm.
>
> To solve this problem, please try the following:
>
> 1. Stop gtm, coordinator and datanode,
> 2. Visit gtm's work directory (you should have specified by -D option with
> gtm_ctl)
> 3. Rename the file register.node to something else
> 4. Restart everything.
>
> BTW, I've posted bash script pgxclocal which takes care of XC
> installation, start and stop for local installation just for test.
>
> This is available from https://github.com/koichi-szk/PGXC-Tools.git
> Current version is attached.
>
> This will help to configure XC in local environment.   The script consists
> of two coordinators and two datanodes.   You can rewrite this section as
> you like.   Also, this comes with  a set of functions which shows what you
> should do to run your XC cluster.
>
> Good luck;
> ---
> Koichi Suzuki
> # I'm rewriting this into general Postgres-XC operating utility called
> pgxc_ctl.
>
> On Tue, 18 Sep 2012 12:51:57 -0700
> Roger Mayes <rog...@gm...> wrote:
>
> > Hello,
> >
> > I'm new to pg-xc, I'm just working on getting off the ground using pg-xc
> > 1.0.1 as the back end for a new project.  I would've searched prior posts
> > for similar ones before posting, but I don't see any way to do that?
> >
> > I'm using CentOS 6.3, I've used the "short version" installation to set
> up
> > a gtm, a single coordinator, and a single data node on my local host.
>  Here
> > are the contents of my pgxc_node table:
> >
> > -bash-4.1$ psql -U postgres
> > psql (PGXC 1.0.1, based on PG 9.1.5)
> > Type "help" for help.
> > postgres=# select * from pgxc_node;
> >  node_name | node_type | node_port | node_host | nodeis_primary |
> > nodeis_preferred |  node_id
> >
> -----------+-----------+-----------+-----------+----------------+------------------+------------
> >  coord1    | C         |      5432 | localhost | f              | f
> >        | 1885696643
> >  datanode1 | D         |     15432 | localhost | t              | t
> >        |  888802358
> >
> >
> > The problem I'm having is that after maybe 60 to 90 seconds or so after
> > starting, the coordinator dies with a log message like
> >
> > FATAL:  Can not register Coordinator on GTM
> >
> > The gtm is definitely running, I can see it in the process list.  The
> only
> > changes to the default postgresql.conf's I've made is to specify the port
> > of 15432 for datanode1, and (as part of an effort to fix this problem)
> > uncomment the host ('localhost') and port (6666) of the gtm in all 3
> > postgresql.conf files.
> >
> > Another thing I did to try to fix this was:
> >
> > alter node datanode1 with (primary = true, preferred = true);
> >
> > As you can see, that has affected the pgxc_node contents.  But that
> didn't
> > have any impact on this crashing behavior.
> >
> > I tried starting using the method presented in the short version install
> to
> > start everything, and I also tried starting up like this:
> >
> > gtm_ctl -Z gtm -D data_gtm -l gtm.log start
> > sleep 1
> > pg_ctl -Z coordinator -D data_coord1 -l coord1.log start
> > sleep 1
> > pg_ctl -Z datanode -D data_datanode1 -l datanode1.log start
> >
> > ..from the /usr/local/pgsql directory.  (I also tried specifying absolute
> > paths.)
> >
> > I've tried using kill to clear everything out of the process table, I've
> > tried making sure the last shutdown was clean for everything, using
> pg_ctl
> > and gtm_ctl to shutdown, and then starting up fresh from having shutdown
> > cleanly.
> >
> > SELinux is disabled, the local firewall is disabled.
> >
> > Everything works for about 60 to 90 seconds, then the coordinator dies
> with
> > the message above.  Any help would be greatly appreciated,
> >
> > Shavais
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>