Re: [Postgres-xc-general] Add new coordinator error!

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

I supporte the error was encountered in pg_resgtore and pgxc is the owner
of postgres-XC in your pgxc_ctl.conf file.   The issue looks some (not
necessarily just one) bugs.  Can I have log files at the new coordinator?
 This may have some more information on the issue.

Regards;

---
Koichi Suzuki

2013/10/4 Julian <jul...@gm...>

> Dear Sir,
>
> My cluster has configured by pg_ctl now, but till filed.
>
> Error message
>
> --------------------------------------------------------------------------------
> PGXC add coordinator master coord4 node4  20004 20010 /opt/pgxc/nodes/coord
> …...
> Actual Command: ssh pgxc@node4 "( pg_ctl start -Z restoremode -D
> /opt/pgxc/nodes/coord -o -i ) > /tmp/squeeze-10-200_STDOUT_2618_16 2>&1" <
> /dev/null > /dev/null 2>&1
> Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_16
> /tmp/STDOUT_2618_17 > /dev/null 2>&1
> SET
> SET
> psql:/tmp/GENERAL_2618_15:12: ERROR:  role "pgxc" already exists
> ALTER ROLE
> REVOKE
> REVOKE
> GRANT
> GRANT
> CREATE NODE
> CREATE NODE
> CREATE NODE
> CREATE NODE
> CREATE NODE
> CREATE NODE
> You are now connected to database "postgres" as user "pgxc".
> SET
> SET
> SET
> SET
> SET
> COMMENT
> CREATE EXTENSION
> COMMENT
> SET
> SET
> SET
> psql:/tmp/GENERAL_2618_15:92: connection to server was lost
> Actual Command: ssh pgxc@node4 "( pg_ctl stop -Z restoremode -D
> /opt/pgxc/nodes/coord ) > /tmp/squeeze-10-200_STDOUT_2618_18 2>&1" <
> /dev/null > /dev/null 2>&1
> Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_18
> /tmp/STDOUT_2618_19 > /dev/null 2>&1
> Starting coordinator master coord4
> Done.
> CREATE NODE
> CREATE NODE
> CREATE NODE
> ALTER NODE
> ----------------------------------------------------------------
>
> Error log
> --------------------------------------------------------------------
> ERROR:  role "pgxc" already exists
> STATEMENT:  CREATE ROLE pgxc;
> LOG:  *server process (PID 3013) was terminated by signal 11:
> Segmentation fault*
> DETAIL:  Failed process was running: CREATE TABLE user_info_hash (
>             id integer NOT NULL,
>             firstname text,
>             lastname text,
>             info text
>         )
>         DISTRIBUTE BY HASH (id)
>         TO NODE (datanode1,datanode2,datanode3);
> LOG:  terminating any other active server processes
> WARNING:  terminating connection because of crash of another server process
> DETAIL:  The postmaster has commanded this server process to roll back the
> current transaction and exit, because another server process exited
> abnormally and possibly co
> rrupted shared memory.
> HINT:  In a moment you should be able to reconnect to the database and
> repeat your command.
> ---------------------------------------------------------------------------
>
> Any comments are appreciated
>
>
> Best Regards,
>
> --
> Julian
> 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信
>
> On 2013年10月3日Thursday at 上午9:31, Koichi Suzuki wrote:
>
> You cannot add a coordinator in such a way.    There're many issued to be
> resolved internally.   You can configure and operate whole cluster with
> pgxc_ctl to get handy way to add coordinator/datanode.
>
> I understand you have your cluster configured without pgxc_ctl.   In this
> case, adding coordinator manually could be a bit complicated work.   Sorry,
> I've not uploaded the detailed step to do it.
>
> Whole steps will be found in add_coordinatorMaster() function defined in
> coord_cmd.c of pgxc_ctl source code.   It will be found at contrib/pgxc_ctl
> in the release material.
>
> Please allow a bit of time to find my time to upload this information to
> XC wiki.
>
> Or, you can backup whole database with pg_dumpall, then reconfigure new xc
> cluster with additional coordinator, and then restore the backup.
>
> Regards;
>
> ---
> Koichi Suzuki
>
>
> 2013/10/3 Julian <jul...@gm...>
>
> Dear Sir,
>
> I have a cluster with 3 coordinators and 3 datanodes on 3 VM, today i
> was try to added a new coordinator to the cluster, when i using command
> "psql postgres -f coordinator.sql -p 5455" to restore the backup file to
> the new coordinator.
>
> Then i got this message :
>
> psql:coordinator-dump.sql:105: connection to server was lost
>
> In the log file:
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
> 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,2,,2013-10-02
> 22:59:42 CST,,0,LOG,00000,"server process (PID 29094) was terminated by
> signal 11: Segmentation fault","Failed process was r
> unning: CREATE TABLE user_info_hash (
>      id integer NOT NULL,
>      firstname text,
>      lastname text,
>      info text
> )
> DISTRIBUTE BY HASH (id)
> TO NODE (dn2,dn1,dn3);",,,,,,,,""
> 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,3,,2013-10-02
> 22:59:42 CST,,0,LOG,00000,"terminating any other active server
> processes",,,,,,,,,""
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
> refer to
> http://postgres-xc.sourceforge.net/docs/1_1/add-node-coordinator.html
>
> Is there something i doing worng?
>
>
> Thanks for your kindly reply.
>
>   And sorry for my poor english.
>
>
> Best regards.
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>
>
>