[pgpool-general: 3615] Re: Fwd: Strange error

[Mephysto]

Hi Yugo,
I checked my nodes, but the primary node is node 0, node 1 and 2 are in
standby and effectively I can see receiver postgresql processes. Moreover
this error occurs only in a pgpool instance and I notice also a warning:

2015-04-10 15:18:22: pid 7997: WARNING:  failed to lock semaphore
error:"Invalid argument"
2015-04-10 15:18:22: pid 7997: WARNING:  failed to unlock semaphore
error:"Invalid argument"
2015-04-10 15:18:22: pid 7997: WARNING:  failed to lock semaphore
error:"Invalid argument"
2015-04-10 15:18:22: pid 7997: WARNING:  failed to unlock semaphore
error:"Invalid argument"


So, I don't understand the cause of error.

Best regards.

Mephysto

On 10 April 2015 at 00:45, Tatsuo Ishii <ishii at postgresql.org> wrote:

> That indicates that pgpool-II fails to get result from
> pg_last_xlog_replay_location() on node 2.  Usual cause of the problem
> is that node 2 is not a standby while pgpool-II believes the node is a
> standby. You accidentaly promoted node 2 to primary?
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
> > Hi there,
> > I have two pgpool instance working together with watchdog and everything
> > seems to work with no problems.
> >
> > But in log file of one of the instance I found an error that occur
> > continuously:
> >
> >
> > 2015-04-09 22:48:42: pid 5330: ERROR:  Failed to check replication time
> lag
> > 2015-04-09 22:48:42: pid 5330: DETAIL:  Query to node (2) returned no
> data
> > 2015-04-09 22:48:42: pid 5330: CONTEXT:  while checking replication time
> lag
> >
> >
> >
> >
> >>From what this message can depend?
> >
> > Thanks in advance.
> >
> > Cheers.
> >
> > Mephysto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20150410/e150521d/attachment.html>