[pgpool-general: 3174] Re: Cannot run 'show pool_nodes'

[John Scalia]

I'll check the configuration again, but as that particular system (the one serving as the primary) was misbehaving in several other ways, I'm rebooting it to get a clean slate, and 
now, of course, I keep getting an ssh: connection refused from that system. It's a royal pain when you're some 500 miles away from server connecting via a VPN connection.

On 9/17/2014 2:29 PM, Ryan DeShone wrote:
> In that case, something is likely misconfigured in your pgpool setup. You should check your pgpool logs for clues as to what is happening. You could also turn on verbose mode for psql to get more information about why it is not connecting by setting the VERBOSITY environment variable to 'verbose'
>
> On 09/17/2014 02:01 PM, jayknowsunix at gmail.com wrote:
>> The commands I've attempted are:
>>
>> /usr/pgsql-9.3/bin/psql -h 10.10.1.140 -p 9999 csg_db
>>
>> Where 10.10.1.140 is the VIP and csg_db is the database. That command returns immediately to a shell prompt and does not invoke any interpreter for SQL commands. If I do not use the -p flag, then I do receive an SQL interpreter, but of course, pgpool is not intercepting.
>>
>> Sent from my iPad
>>
>>> On Sep 17, 2014, at 1:41 PM, Ryan DeShone <rdeshone at liquidweb.com> wrote:
>>>
>>> The IP you're connecting to isn't the issue. It's the port you're connecting to. Assuming postgresql and pgpool are both running on the default port, if you do not explicitly tell psql to connect to the pgpool port (default: 9999) then you will end up connecting directly to postgresql.
>>>
>>> So, once again assuming that you did not change the default port numbers, you would need to add '-p 9999' when you execute psql to connect to pgpool.
>>>
>>>> On 09/17/2014 11:13 AM, jayknowsunix at gmail.com wrote:
>>>> I am connecting to the VIP which was brought up by pgpool. I have even restarted pgpool on each machine in the cluster and verified that the VIP was being managed by pgpool (the VIP disappeared while pgpool was off and came back when it was restarted.) i have also verified that connection pooling is on for each system. Is there something else I can check?
>>>>
>>>> Sent from my iPad
>>>>
>>>>> On Sep 17, 2014, at 10:51 AM, Tatsuo Ishii <ishii at postgresql.org> wrote:
>>>>>
>>>>> You need to connect pgpool-II, not connect directry to PostgreSQL
>>>>> because "show pool_nodes" is a pgpool-II specific SQL command.
>>>>> Here is an example session.
>>>>>
>>>>> test=# show pool_nodes;
>>>>> node_id | hostname | port  | status | lb_weight |  role
>>>>> ---------+----------+-------+--------+-----------+---------
>>>>> 0       | /tmp     | 11000 | 2      | 0.500000  | primary
>>>>> 1       | /tmp     | 11001 | 2      | 0.500000  | standby
>>>>> (2 rows)
>>>>>
>>>>> Best regards,
>>>>> --
>>>>> Tatsuo Ishii
>>>>> SRA OSS, Inc. Japan
>>>>> English: http://www.sraoss.co.jp/index_en.php
>>>>> Japanese:http://www.sraoss.co.jp
>>>>>
>>>>>> In response to my question yesterday, Ishii-san suggested running 'show pool_nodes;' I tried running this command this morning in a psql session, but was unsuccessful. The error was a simple not found one. Apparently, I've missed a step during setup, and I've been going back through the online tutorial, but I'm not seeing what I need. Also, looking online at what this command does, it doesn't appear to give more information than pcp_node_info does. That utility does work for me, btw. Am I mistaken? I'm just trying to determine which pgpool instance is the master in a master-slave configuration after a failover attempt.
>>>>>> --
>>>>>> Jay
>>>>>>
>>>>>> Sent from my iPad
>>>>>> _______________________________________________
>>>>>> pgpool-general mailing list
>>>>>> pgpool-general at pgpool.net
>>>>>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>>>> _______________________________________________
>>>> pgpool-general mailing list
>>>> pgpool-general at pgpool.net
>>>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>>> --
>>> Ryan DeShone
>>>