[Pgpool-general] stuck with a shmem_exit after the loading of "/usr/local/etc/pool_hba.conf"

[Guillaume Lelarge]

Le 03/02/2011 10:02, Bharath Keshav a écrit :
> I am getting the following error when I try to run Pgpool. I am trying to
> use postgresql 9.0 hot streaming and then load balancing capability of
> Pgpool. However, I am stuck with a shmem_exit after the loading
> of "/usr/local/etc/pool_hba.conf", as attached below. Please let me know
> what could be wrong.
> 
> 
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: listen_addresses
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: '*' kind: 4
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: port
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 9999 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: pcp_port
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 9898 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: socket_dir
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: '/var/run/postgresql' kind: 4
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: pcp_socket_dir
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: '/tmp' kind: 4
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: backend_socket_dir
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: '/var/run/postgresql' kind: 4
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: pcp_timeout
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 10 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: num_init_children
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 32 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: max_pool
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 4 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: child_life_time
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 0 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: connection_life_time
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 0 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: child_max_connections
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 0 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: client_idle_limit
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 0 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: authentication_timeout
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: 60 kind: 2
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: logdir
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: '/var/log/pgpool' kind: 4
> 2011-02-03 08:53:20 DEBUG: pid 12138: key: pid_file_name
> 2011-02-03 08:53:20 DEBUG: pid 12138: value: '/var/run/pgpool/pgpool.pid'
> kind: 4

The usual issue you could have is that your process can't write its pid
file or its socket file. Are you sure that the user who launches pgpool
has right to write into /var/run/pgpool? (pid_file_name parameter) if
not, try to change this with another directory.

The backend socket is created in /var/run/postgresql. Does the user have
the right to write in it?


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com