Re: [Postgres-xc-general] GTM Proxy error...

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

You did not share the contents of gtm_proxy.conf. Also double-check the
values of gtm_host and gtm_port parameters in the coordinator's
postgresql.conf.

If this is on a Linux platform, check if iptables/firewall is blocking
connection to port 6666 or something as well.

HTH,
Nikhils

On Tue, Apr 23, 2013 at 1:24 AM, Anson Abraham <ans...@gm...>wrote:

> Also when I started up coodinator I get error also:
>
> LOG:  database system was interrupted; last known up at 2013-04-22
> 15:14:08 EDT
> LOG:  database system was not properly shut down; automatic recovery in
> progress
> LOG:  record with zero length at 0/16E4EA0
> LOG:  redo is not required
> LOG:  database system is ready to accept connections
> LOG:  autovacuum launcher started
> WARNING:  can not connect to GTM: Success
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  Xid is invalid.
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  Xid is invalid.
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  can not connect to GTM: Bad file descriptor
> ERROR:  GTM error, could not obtain snapshot
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  Xid is invalid.
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  Xid is invalid.
> WARNING:  can not connect to GTM: Bad file descriptor
> WARNING:  can not connect to GTM: Bad file descriptor
> ERROR:  GTM error, could not obtain snapshot
>
>
> I started the GTM initially as such:
> /usr/local/pgsql/bin/gtm_ctl -Z gtm -D /var/lib/postgresql/pgxc/data_gtm
> -l /var/log/postgresql/gtm.log start
>
> But then I opted for:
> /usr/local/pgsql/bin/gtm -D /var/lib/postgresql/pgxc/data_gtm >
> /var/log/postgresql/gtm.log 2>&1 &
>
> And still no errors in the log.
>
>
> On Mon, Apr 22, 2013 at 1:57 PM, Anson Abraham <ans...@gm...>wrote:
>
>> # specified by -D command line option of gtm or gtm_ctl.  The
>> # configuration file name must be "gtm.conf"
>> #
>> #
>> # This file consists of lines of the form
>> #
>> #  name = value
>> #
>> # (The "=" is optional.) Whitespace may be used.   Comments are
>> # introduced with "#" anywhere on a line.  The complete list of
>> # parameter names and allowed values can be found in the
>> # Postgres-XC documentation.
>> #
>> # The commented-out settings shown in this file represent the default
>> # values.
>> #
>> # Re-commenting a setting is NOT sufficient to revert it to the default
>> # value.
>> #
>> # You need to restart the server.
>>
>>
>> #------------------------------------------------------------------------------
>> # GENERAL PARAMETERS
>>
>> #------------------------------------------------------------------------------
>> nodename = 'one' # Specifies the node name.
>>  # (changes requires restart)
>> #listen_addresses = '*' # Listen addresses of this GTM.
>> # (changes requires restart)
>> port = 6666 # Port number of this GTM.
>> # (changes requires restart)
>>
>> #startup = ACT # Start mode. ACT/STANDBY.
>>
>>
>> #------------------------------------------------------------------------------
>> # GTM STANDBY PARAMETERS
>>
>> #------------------------------------------------------------------------------
>> #Those parameters are effective when GTM is activated as a standby server
>> #active_host = '' # Listen address of active GTM.
>> # (changes requires restart)
>> #active_port = # Port number of active GTM.
>> # (changes requires restart)
>>
>> #---------------------------------------
>> # OTHER OPTIONS
>> #---------------------------------------
>> #keepalives_idle = 0 # Keepalives_idle parameter.
>> #keepalives_interval = 0 # Keepalives_interval parameter.
>> #keepalives_count = 0 # Keepalives_count internal parameter.
>> #log_file = 'gtm.log' # Log file name
>> #log_min_messages = WARNING # log_min_messages.  Default WARNING.
>>    # Valid value: DEBUG, DEBUG5, DEBUG4, DEBUG3,
>>  # DEBUG2, DEBUG1, INFO, NOTICE, WARNING,
>> # ERROR, LOG, FATAL, PANIC
>> #synchronous_backup = off # If backup to standby is synchronous
>>
>>
>> On Mon, Apr 22, 2013 at 12:42 PM, Nikhil Sontakke <ni...@st...>wrote:
>>
>>> Can you please share the contents of the gtm's gtm.conf
>>>
>>> And also the gtm proxy's gtm_proxy.conf?
>>>
>>> Regards,
>>> Nikhils
>>>
>>>
>>> On Mon, Apr 22, 2013 at 9:34 PM, Anson Abraham <ans...@gm...>wrote:
>>>
>>>>  I was doing a test install of PGXC version 1.0.2.
>>>>
>>>> I basically did as such for GTM and GTM_Proxy on same server:
>>>>
>>>> /usr/local/pgsql/bin/initgtm -Z gtm -D /var/lib/postgresql/pgxc/data_gtm
>>>>
>>>> /usr/local/pgsql/bin/gtm_ctl -Z gtm -D
>>>> /var/lib/postgresql/pgxc/data_gtm -l /var/log/postgresql/pgxc/gtm.log start
>>>>
>>>> which starts.  I left the config file as is for now.
>>>>
>>>> Then
>>>>
>>>> /usr/local/pgsql/bin/initgtm -Z gtm_proxy -D
>>>> /var/lib/postgresql/pgxc/data_gtm_proxy
>>>>
>>>> and i left the config file alone as well and ran:
>>>>
>>>> /usr/local/pgsql/bin/gtm_ctl -Z gtm_proxy -D
>>>> /var/lib/postgresql/pgxc/data_gtm_proxy -l
>>>> /var/log/postgresql/pgxc/gtm_proxy.log start
>>>>
>>>> And I get an error of
>>>>
>>>> server starting
>>>> postgres@drupalgtm:/var/lib/postgresql/pgxc/data_gtm_proxy$
>>>> 1:139986171815680:2013-04-22 12:02:43.098 EDT -FATAL:  can not connect to
>>>> GTM
>>>> LOCATION:  ConnectGTM, proxy_main.c:3356
>>>>
>>>> and it's stuck. Doing a ps -ef i see the gtm running but not the proxy.
>>>>  Am i missing something?
>>>>
>>>> I followed the instructions from the wiki and still nothing.
>>>> Any help here would be really appreciated.
>>>> -Anson
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Precog is a next-generation analytics platform capable of advanced
>>>> analytics on semi-structured data. The platform includes APIs for
>>>> building
>>>> apps and a phenomenal toolset for data science. Developers can use
>>>> our toolset for easy data analysis & visualization. Get a free account!
>>>> http://www2.precog.com/precogplatform/slashdotnewsletter
>>>> _______________________________________________
>>>> Postgres-xc-general mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>>>
>>>>
>>>
>>>
>>> --
>>> StormDB - http://www.stormdb.com
>>> The Database Cloud
>>>
>>
>>
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>

-- 
StormDB - http://www.stormdb.com
The Database Cloud