Thread: Pgpool starting problem

Hi all,

If I turn use_watchdog = off in the pgpool.conf file, then in spite of the
system being configured as master-slave, a socket file is created in /tmp,
and everything starts normally with no errors. If, however, I set
use_watchdog = on, pgpool will abort on startup with the following errors:

2014-05-08 14:40:22 ERROR: pid 32893: watchdog: wd_init failed
2014-05-08 14:40:22 ERROR: pid 32893: wd_main error
2014-05-08 14:40:22 ERROR: pid 32893: unlink(/tmp/.s.PGSQL.9898) failed: No
such file or directory

It seems pretty consistent doing this, and I can flip use_watchdog on and
off and the same behavior repeating. Any ideas?
--
Jay



--
View this message in context: http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Jay at Verizon wrote
> Hi all,
>
> If I turn use_watchdog = off in the pgpool.conf file, then in spite of the
> system being configured as master-slave, a socket file is created in /tmp,
> and everything starts normally with no errors. If, however, I set
> use_watchdog = on, pgpool will abort on startup with the following errors:
>
> 2014-05-08 14:40:22 ERROR: pid 32893: watchdog: wd_init failed
> 2014-05-08 14:40:22 ERROR: pid 32893: wd_main error
> 2014-05-08 14:40:22 ERROR: pid 32893: unlink(/tmp/.s.PGSQL.9898) failed:
> No such file or directory
>
> It seems pretty consistent doing this, and I can flip use_watchdog on and
> off and the same behavior repeating. Any ideas?
> --
> Jay

I'm doubting you are providing enough information for someone to actually
provide useful help.

Beyond that this is not the correct list for this question.  pgPoolII is a
standalone product - i.e., not part of PostgreSQL core which is what this
list to dedicated to.  The proper links, as well as documentation, can be
found at:

http://www.pgpool.net/mediawiki/index.php/Main_Page

I suggest posting the actual configuration file along with detailing exactly
how (and on what platform) you are running the various applications.

It is possible that O/S user permissions prevent pgPool from seeing or
interacting with the socket file.

David J.





--
View this message in context: http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276p5803279.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

> Hi all,
>
> If I turn use_watchdog = off in the pgpool.conf file, then in spite of the
> system being configured as master-slave, a socket file is created in /tmp,
> and everything starts normally with no errors. If, however, I set
> use_watchdog = on, pgpool will abort on startup with the following errors:
>
> 2014-05-08 14:40:22 ERROR: pid 32893: watchdog: wd_init failed
> 2014-05-08 14:40:22 ERROR: pid 32893: wd_main error
> 2014-05-08 14:40:22 ERROR: pid 32893: unlink(/tmp/.s.PGSQL.9898) failed: No
> such file or directory
>
> It seems pretty consistent doing this, and I can flip use_watchdog on and
> off and the same behavior repeating. Any ideas?

You didn't give any pgpool version, configuration file info, I cannot
guess what's going on. There's a detailed installation document here:

http://www.pgpool.net/pgpool-web/contrib_docs/watchdog_master_slave_3.3/en.html

Despite you follow the instruction you still have problems, you should ask pgpool ML.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

Hi Jay,
Can you pls tell me how you resolved this issue.
We are running pgpool-II version 3.3.3
Thanks.
Ellen



--
View this message in context: http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276p5818354.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Hi Jay,
Can you pls tell me how you resolved this issue.
We are running pgpool-II version 3.3.3
Thanks.
Ellen

---

If you reply to this email, your message will be added to the discussion below:

http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276p5818354.html

To unsubscribe from Pgpool starting problem, click here.
NAML

---

View this message in context: Re: Pgpool starting problem
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Problem has been solved utilizing tcpdump which revealed that the standbys were not trying to contact the primary server, although they each were contacting the other standby. From this, we determined that a minor typographical error was present in the pgpool.conf file. The setting under the watchdog section for other_hostname0 was correct, and other required settings for that entry were also correct, but had somehow been commented out. The log file was not very revealing, and finding one badly inserted "#" in a 647 line file was problematic to say the least.

Hi Jay,
Can you pls tell me how you resolved this issue.
We are running pgpool-II version 3.3.3
Thanks.
Ellen

---

If you reply to this email, your message will be added to the discussion below:

http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276p5818354.html

To unsubscribe from Pgpool starting problem, click here.
NAML

---

View this message in context: Re: Pgpool starting problem
Sent from the PostgreSQL - general mailing list archive at Nabble.com.