View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000331 | Pgpool-II | General | public | 2017-08-23 15:59 | 2017-08-23 18:01 |
| Reporter | vishnuduttpv | Assigned To | Muhammad Usama | ||
| Priority | high | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.6.5 | ||||
| Summary | 0000331: The socket location is not changing while running pcp commands | ||||
| Description | I have installed the pgpool 3.6.5 and pgpool admin 3.6.1. After configuration I have changed the pcp and pgpool socket locations to /var/run/postgresql/. Works fine while starting the pgpool using 'pgpool' command.But when Iam using pcp_stop_pgpool its taking the socket location from /tmp. Its showing error as follows, ERROR: connection to socket "/tmp/.s.PGSQL.9898" failed with error "No such file or directory" But I am having the socket directory as /var/run/postgresql. | ||||
| Additional Information | From , /et/pgpool/pgpool.conf listen_addresses = '*' # Host name or IP address to listen on: # '*' for all, '' for no TCP/IP connections # (change requires restart) port = 9999 # Port number # (change requires restart) socket_dir = '/var/run/postgresql' # Unix domain socket path # The Debian package defaults to # /var/run/postgresql # (change requires restart) listen_backlog_multiplier = 2 # Set the backlog parameter of listen(2) to # num_init_children * listen_backlog_multiplier. # (change requires restart) serialize_accept = off # whether to serialize accept() call to avoid thundering herd problem # (change requires restart) # - pgpool Communication Manager Connection Settings - pcp_listen_addresses = '*' # Host name or IP address for pcp process to listen on: # '*' for all, '' for no TCP/IP connections # (change requires restart) pcp_port = 9898 # Port number for pcp # (change requires restart) pcp_socket_dir = '/var/run/postgresql' | ||||
| Tags | No tags attached. | ||||
|
|
This is expected behaviour, All PCP client side tools are independent of Pgpool-II server side settings and have no visibility and access to the pgpool.conf file, Since the utility can be used to connect to any local or remote Pgpool-II, So PCP utilities always try to connect on the default socket directory and default port unless explicitly specified in the command's argument. If you are using a different pcp_socket_dir and/or different pcp_port then you would be required to specify the socket file location and port in the pcp command argument, For example to make PCP utilities use /var/run/postgresql as socket directory you should specify the directory in the host argument. # with pcp_port = 9898 and pcp_socket_dir = '/var/run/postgresql' pcp_stop_pgpool -h /var/run/postgresql -p 9898 -U <user> Thanks Kind Regards |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-08-23 15:59 | vishnuduttpv | New Issue | |
| 2017-08-23 18:01 | Muhammad Usama | Assigned To | => Muhammad Usama |
| 2017-08-23 18:01 | Muhammad Usama | Status | new => closed |
| 2017-08-23 18:01 | Muhammad Usama | Resolution | open => no change required |
| 2017-08-23 18:01 | Muhammad Usama | Note Added: 0001680 |
