[Pgpool-general] stuck with a shmem_exit after the loading of "/usr/local/etc/pool_hba.conf"
Sandeep Thakkar
sandeeptt at yahoo.com
Thu Feb 3 11:42:48 UTC 2011
Can you please check if the right libpq is getting picked up when you started
the database server. If it is, then I have no idea. You need to debug it.
________________________________
From: Bharath Keshav <bharath.keshav at gmail.com>
To: Sandeep Thakkar <sandeeptt at yahoo.com>
Cc: pgpool-general at pgfoundry.org
Sent: Thu, February 3, 2011 4:44:53 PM
Subject: Re: [Pgpool-general] stuck with a shmem_exit after the loading of
"/usr/local/etc/pool_hba.conf"
Actually, I have used trust everywhere. Still, I seem to get this. I am not sure
from where this ssl is creeping up.
-Bharath
On Thu, Feb 3, 2011 at 4:27 PM, Sandeep Thakkar <sandeeptt at yahoo.com> wrote:
Do you use md5 for authentication? pgpool-II does not support MD5authentication.
Please use trust in pg_hba.conf. Also I think, this question has also been
posted on this forums before. Please browse for the question before you post it
again.
>
>
>
>
>
>
>
________________________________
From: Bharath Keshav <bharath.keshav at gmail.com>
>To: Sandeep Thakkar <sandeeptt at yahoo.com>
>Cc: pgpool-general at pgfoundry.org
>Sent: Thu, February 3, 2011 4:04:03 PM
>
>Subject: Re: [Pgpool-general] stuck with a shmem_exit after the loading of
>"/usr/local/etc/pool_hba.conf"
>
>
>Thanks for your quick response. I see that pgpool is running, but when i execute
>psql -p 999 -U postgres command, at that point it throws an error : SSL
>requested but SSL support is not available, as seen in the log below.
>
>
>
>
>2011-02-03 10:30:18 LOG: pid 14771: pgpool-II successfully started. version
>3.1.0-alpha1 (umiyameboshi)
>2011-02-03 10:30:18 DEBUG: pid 14797: I am 14797
>2011-02-03 10:30:18 DEBUG: pid 14798: I am 14798
>2011-02-03 10:30:18 DEBUG: pid 14801: I am 14801
>2011-02-03 10:30:18 DEBUG: pid 14771: find_primary_node: not in streaming
>replication mode
>2011-02-03 10:30:18 DEBUG: pid 14771: starting health checking
>2011-02-03 10:30:18 DEBUG: pid 14771: health_check: 0 th DB node status: 1
>2011-02-03 10:30:18 DEBUG: pid 14805: I am 14805
>2011-02-03 10:30:18 DEBUG: pid 14800: I am 14800
>2011-02-03 10:30:18 DEBUG: pid 14802: I am 14802
>2011-02-03 10:30:18 DEBUG: pid 14771: health_check: 1 th DB node status: 1
>2011-02-03 10:30:18 DEBUG: pid 14796: I am 14796
>2011-02-03 10:30:18 DEBUG: pid 14803: I am 14803
>2011-02-03 10:30:18 DEBUG: pid 14799: I am 14799
>2011-02-03 10:30:18 DEBUG: pid 14794: I am 14794
>2011-02-03 10:30:18 DEBUG: pid 14771: health_check: 2 th DB node status: 3
>2011-02-03 10:30:22 DEBUG: pid 14801: I am 14801 accept fd 6
>2011-02-03 10:30:22 DEBUG: pid 14801: Protocol Major: 3 Minor: 0 database:
>postgres user: postgres
>2011-02-03 10:30:22 DEBUG: pid 14801: new_connection: connecting 0 backend
>2011-02-03 10:30:22 DEBUG: pid 14801: new_connection: connecting 1 backend
>2011-02-03 10:30:22 DEBUG: pid 14801: new_connection: connecting 2 backend
>2011-02-03 10:30:22 DEBUG: pid 14801: new_connection: skipping slot 2 because
>backend_status = 3
>2011-02-03 10:30:22 DEBUG: pid 14801: pool_ssl: SSL requested but SSL support is
>not available
>2011-02-03 10:30:22 DEBUG: pid 14801: pool_ssl: SSL requested but SSL support is
>not available
>2011-02-03 10:30:22 LOG: pid 14801: pool_do_auth: maybe protocol version
>mismatch (current version 3)
>2011-02-03 10:30:22 DEBUG: pid 14801: pool_read_string: read all from pending
>data. po:1 len:146
>2011-02-03 10:30:22 DEBUG: pid 14801: pool_read_string: read all from pending
>data. po:1 len:146
>2011-02-03 10:30:28 DEBUG: pid 14771: starting health checking
>2011-02-03 10:30:28 DEBUG: pid 14771: health_check: 0 th DB node status: 2
>2011-02-03 10:30:28 DEBUG: pid 14771: health_check: 1 th DB node status: 2
>2011-02-03 10:30:28 DEBUG: pid 14771: health_check: 2 th DB node status: 3
>2011-02-03 10:30:38 DEBUG: pid 14771: starting health checking
>
>
>
>On Thu, Feb 3, 2011 at 3:37 PM, Sandeep Thakkar <sandeeptt at yahoo.com> wrote:
>
>Is your PG server running? Can you please change your logdir in pgpool.conf to
>"logdir = '/tmp" and restart the pgpool and redirect it's output to
>/tmp/pgpool.log ? and see what this log says.
>>
>>
>>
>>
>>
>>
>>
________________________________
From: Bharath Keshav <bharath.keshav at gmail.com>
>>To: Sandeep Thakkar <sandeeptt at yahoo.com>
>>Cc: pgpool-general at pgfoundry.org
>>Sent: Thu, February 3, 2011 3:21:12 PM
>>Subject: Re: [Pgpool-general] stuck with a shmem_exit after the loading of
>>"/usr/local/etc/pool_hba.conf"
>>
>>
>>You are right, it's running. However, I am not able to connect using the
>>cmmands psql -p 9999 -U postgres. I get the following error:
>>
>>
>>psql: server closed the connection unexpectedly
>>This probably means the server terminated abnormally
>>before or while processing the request.
>>
>>
>>
>>
>>Also, through the web interface which is working, I don't get anything when I
>>click the "node info" button..which means it's empty
>>
>>
>>The following is my configuration:
>>
>>
>>
>>
>>#
>># pgpool-II configuration file sample
>># $Header:
>>/cvsroot/pgpool/pgpool-web/contrib_docs/simple_sr_setting/pgpool.conf,v 1.1
>>2010/11/04 04:39:57 t-ishii Exp $
>>
>>
>># Host name or IP address to listen on: '*' for all, '' for no TCP/IP
>># connections
>>listen_addresses = '*'
>>
>>
>># Port number for pgpool
>>port = 9999
>>
>>
>># Port number for pgpool communication manager
>>pcp_port = 9898
>>
>>
>># Unix domain socket path. (The Debian package defaults to
>># /var/run/postgresql.)
>>socket_dir = '/var/run/postgresql'
>>
>>
>># Unix domain socket path for pgpool communication manager.
>># (Debian package defaults to /var/run/postgresql)
>>pcp_socket_dir = '/tmp'
>>
>>
>># Unix domain socket path for the backend. Debian package defaults to
>>/var/run/postgresql!
>>backend_socket_dir = '/var/run/postgresql'
>>
>>
>># pgpool communication manager timeout. 0 means no timeout, but strongly not
>>recommended!
>>pcp_timeout = 10
>>
>>
>># number of pre-forked child process
>>num_init_children = 32
>>
>>
>># Number of connection pools allowed for a child process
>>max_pool = 4
>>
>>
>># If idle for this many seconds, child exits. 0 means no timeout.
>>child_life_time = 0
>>
>>
>># If idle for this many seconds, connection to PostgreSQL closes.
>># 0 means no timeout.
>>connection_life_time = 0
>>
>>
>># If child_max_connections connections were received, child exits.
>># 0 means no exit.
>>child_max_connections = 0
>>
>>
>># If client_idle_limit is n (n > 0), the client is forced to be
>># disconnected whenever after n seconds idle (even inside an explicit
>># transactions!)
>># 0 means no disconnect.
>>client_idle_limit = 0
>>
>>
>># Maximum time in seconds to complete client authentication.
>># 0 means no timeout.
>>authentication_timeout = 60
>>
>>
>># Logging directory
>>logdir = '/var/log/pgpool'
>>
>>
>># pid file name
>>pid_file_name = '/var/run/pgpool/pgpool.pid'
>>
>>
>># Replication mode
>>replication_mode = true
>>
>>
>># Load balancing mode, i.e., all SELECTs are load balanced.
>># This is ignored if replication_mode is false.
>>load_balance_mode = true
>>
>>
>># If there's a disagreement with the packet kind sent from backend,
>># then degenrate the node which is most likely "minority". If false,
>># just force to exit this session.
>>replication_stop_on_mismatch = false
>>
>>
>># If there's a disagreement with the number of affected tuples in
>># UPDATE/DELETE, then degenrate the node which is most likely
>># "minority".
>># If false, just abort the transaction to keep the consistency.
>>failover_if_affected_tuples_mismatch = true
>>
>>
>># If true, replicate SELECT statement when load balancing is disabled.
>># If false, it is only sent to the master node.
>>replicate_select = false
>>
>>
>># Semicolon separated list of queries to be issued at the end of a session
>>reset_query_list = 'ABORT;DISCARD ALL'
>>
>>
>># white_function_list is a comma separated list of function names
>># those do not write to database. Any functions not listed here
>># are regarded to write to database and SELECTs including such
>># writer-functions will be executed on master(primary) in master/slave
>># mode, or executed on all DB nodes in replication mode.
>>#
>># black_function_list is a comma separated list of function names
>># those write to database. Any functions not listed here
>># are regarded not to write to database and SELECTs including such
>># read-only-functions will be executed on any DB nodes.
>>#
>># You cannot make full both white_function_list and
>># black_function_list at the same time. If you specify something in
>># one of them, you should make empty other.
>>#
>># Pre 3.0 pgpool-II recognizes nextval and setval in hard coded
>># way. Following setting will do the same as the previous version.
>># white_function_list = ''
>># black_function_list = 'nextval,setval'
>>white_function_list = ''
>>#black_function_list = ''
>>black_function_list = 'nextval,setval,foo'
>>
>>
>># If true print timestamp on each log line.
>>print_timestamp = true
>>
>>
>># If true, operate in master/slave mode.
>>master_slave_mode = false
>>
>>
>># Master/slave sub mode. either 'slony' or 'stream'. Default is 'slony'.
>># master_slave_sub_mode = 'stream'
>>master_slave_sub_mode = 'stream'
>>
>>
>># If the standby server delays more than delay_threshold,
>># any query goes to the primary only. The unit is in bytes.
>># 0 disables the check. Default is 0.
>># Note that health_check_period required to be greater than 0
>># to enable the functionality.
>>delay_threshold = 100
>>
>>
>># 'always' logs the standby delay whenever health check runs.
>># 'if_over_threshold' logs only if the delay exceeds delay_threshold.
>># 'none' disables the delay log.
>>log_standby_delay = 'if_over_threshold'
>>#log_standby_delay = 'always'
>>
>>
>># If true, cache connection pool.
>>connection_cache = true
>>
>>
>># Health check timeout. 0 means no timeout.
>>health_check_timeout = 10
>>
>>
>># Health check period. 0 means no health check.
>>health_check_period = 10
>>
>>
>># Health check user
>>health_check_user = 'www-data'
>>
>>
>># Execute command by failover.
>># special values: %d = node id
>># %h = host name
>># %p = port number
>># %D = database cluster path
>># %m = new master node id
>># %M = old master node id
>># %H = new master node host name
>># %P = old primary node id
>># %% = '%' character
>>#
>>failover_command = '/usr/local/etc/failover.sh %d "%h" %p %D %m %M "%H" %P'
>>
>>
>># Execute command by failback.
>># special values: %d = node id
>># %h = host name
>># %p = port number
>># %D = database cluster path
>># %m = new master node id
>># %M = old master node id
>># %% = '%' character
>>#
>>failback_command = '/bin/rm -f /tmp/trigger_file1'
>>
>>
>># If true, trigger fail over when writing to the backend communication
>># socket fails. This is the same behavior of pgpool-II 2.2.x or
>># earlier. If set to false, pgpool will report an error and disconnect
>># the session.
>>fail_over_on_backend_error = false
>>
>>
>># If true, automatically lock table with INSERT statements to keep SERIAL
>># data consistency. An /*INSERT LOCK*/ comment has the same effect. A
>># /NO INSERT LOCK*/ comment disables the effect.
>>insert_lock = true
>>
>>
>># If true, ignore leading white spaces of each query while pgpool judges
>># whether the query is a SELECT so that it can be load balanced. This
>># is useful for certain APIs such as DBI/DBD which is known to adding an
>># extra leading white space.
>>ignore_leading_white_space = false
>>
>>
>># If true, print all statements to the log. Like the log_statement option
>># to PostgreSQL, this allows for observing queries without engaging in full
>># debugging.
>>log_statement = true
>>
>>
>># If true, print all statements to the log. Similar to log_statement except
>># that prints DB node id and backend process id info.
>>log_per_node_statement = true
>>
>>
>># If true, incoming connections will be printed to the log.
>>log_connections = false
>>
>>
>># If true, hostname will be shown in ps status. Also shown in
>># connection log if log_connections = true.
>># Be warned that this feature will add overhead to look up hostname.
>>log_hostname = false
>>
>>
>># if non 0, run in parallel query mode
>>parallel_mode = false
>>
>>
>># if non 0, use query cache
>>enable_query_cache = false
>>
>>
>>#set pgpool2 hostname
>>pgpool2_hostname = 'localhost'
>>
>>
>># system DB info
>>system_db_hostname = 'localhost'
>>system_db_port = 5432
>>system_db_dbname = 'pgpool'
>>system_db_schema = 'pgpool_catalog'
>>system_db_user = 'pgpool'
>>system_db_password = ''
>>
>>
>># backend_hostname, backend_port, backend_weight
>># here are examples
>>
>>
>>
>>
>># - HBA -
>>
>>
>># If true, use pool_hba.conf for client authentication. In pgpool-II
>># 1.1, the default value is false. The default value will be true in
>># 1.2.
>>enable_pool_hba = false
>>
>>
>># md5 authentication file name. '' disables md5 authentication.
>># To enable md5 auth, enable_pool_hba to true.
>># Default is 'pool_passwd'.
>>pool_passwd = not_revealed
>>
>>
>># - online recovery -
>># online recovery user
>>recovery_user = 'postgres'
>>
>>
>># online recovery password
>>recovery_password = not_revealed
>>
>>
>># execute a command in first stage.
>>recovery_1st_stage_command = 'basebackup.sh'
>>
>>
>># execute a command in second stage.
>>recovery_2nd_stage_command = ''
>>
>>
>># maximum time in seconds to wait for remote start-up. 0 means no wait
>>recovery_timeout = 60
>>
>>
>># If client_idle_limit_in_recovery is n (n > 0), the client is forced
>># to be disconnected whenever after n seconds idle (even inside an
>># explicit transactions!) 0 means no disconnect. This parameter only
>># takes effect in recovery 2nd stage.
>>client_idle_limit_in_recovery = 0
>>
>>
>># Specify table name to lock. This is used when rewriting lo_creat
>># command in replication mode. The table must exist and has writable
>># permission to public. If the table name is '', no rewriting occurs.
>>lobj_lock_table = 'pgpool_lobj_lock'
>>
>>
>># If true, enable SSL support for both frontend and backend connections.
>># note that you must also set ssl_key and ssl_cert for SSL to work in
>># the frontend connections.
>>ssl = true
>># path to the SSL private key file
>>ssl_key = '/usr/local/etc/server.key'
>># path to the SSL public certificate file
>>ssl_cert = '/usr/local/etc/server.crt'
>>
>>
>># Debug message verbosity level. 0: no message, 1 <= : more verbose
>>debug_level = 0
>>
>>
>>replication_timeout = 5000
>>log_statement = true
>>ssl_ca_cert = ''
>>ssl_ca_cert_dir = ''
>>backend_hostname0 = '67.23.26.182'
>>backend_port0 = 5432
>>backend_weight0 = 1
>>backend_data_directory0 = '/var/lib/postgresql/9.0/main/'
>>backend_hostname1 = '67.23.29.53'
>>backend_port1 = 5432
>>backend_weight1 = 1
>>backend_data_directory1 = '/var/lib/postgresql/9.0/main/'
>>backend_hostname2 = '67.23.27.95'
>>backend_port2 = 5432
>>backend_weight2 = 1
>>backend_data_directory2 = '/var/lib/postgresql/9.0/main/'
>>
>>
>>
>>On Thu, Feb 3, 2011 at 2:40 PM, Sandeep Thakkar <sandeeptt at yahoo.com> wrote:
>>
>>
>>>That is the correct output. I think, pgpool must be running fine. Did you check
>>>your processes after this? What options do you give while starting pgpool? Use
>>>"pgpool -d -D -f pgpool.conf".
>>>
>>>
>>>
>>>
________________________________
From: Bharath Keshav <bharath.keshav at gmail.com>
>>>To: pgpool-general at pgfoundry.org
>>>Sent: Thu, February 3, 2011 2:32:21 PM
>>>Subject: [Pgpool-general] stuck with a shmem_exit after the loading of
>>>"/usr/local/etc/pool_hba.conf"
>>>
>>>
>>>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
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: replication_mode
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: load_balance_mode
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: replication_stop_on_mismatch
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: replication_stop_on_mismatch: 0
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key:
>failover_if_affected_tuples_mismatch
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: failover_if_affected_tuples_mismatch: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: replicate_select
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: replicate_select: 0
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: reset_query_list
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'ABORT;DISCARD ALL' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: extract_string_tokens: token: ABORT
>>>2011-02-03 08:53:20 DEBUG: pid 12138: extract_string_tokens: token: DISCARD
>ALL
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: white_function_list
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: black_function_list
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'nextval,setval,foo' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: extract_string_tokens: token: nextval
>>>2011-02-03 08:53:20 DEBUG: pid 12138: extract_string_tokens: token: setval
>>>2011-02-03 08:53:20 DEBUG: pid 12138: extract_string_tokens: token: foo
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: print_timestamp
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: master_slave_mode
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: master_slave_sub_mode
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'stream' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: delay_threshold
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 100 kind: 2
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: log_standby_delay
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'if_over_threshold' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: connection_cache
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: health_check_timeout
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 10 kind: 2
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: health_check_period
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 10 kind: 2
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: health_check_user
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'www-data' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: failover_command
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '/usr/local/etc/failover.sh %d "%h"
>>>%p %D %m %M "%H" %P' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: failback_command
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '/bin/rm -f /tmp/trigger_file1'
>>>kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: fail_over_on_backend_error
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: insert_lock
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: ignore_leading_white_space
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: log_statement
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: log_per_node_statement
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: log_connections
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: log_hostname
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: parallel_mode
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: enable_query_cache
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: false kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: pgpool2_hostname
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '67.23.26.182' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: system_db_hostname
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '67.23.26.182' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: system_db_port
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 5432 kind: 2
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: system_db_dbname
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'pgpool' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: system_db_schema
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'pgpool_catalog' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: system_db_user
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'pgpool' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: system_db_password
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: enable_pool_hba
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: pool_passwd
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'pool_passwd' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: recovery_user
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'postgres' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: recovery_password
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'pgpoolAdmin' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: recovery_1st_stage_command
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'basebackup.sh' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: recovery_2nd_stage_command
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: recovery_timeout
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 60 kind: 2
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: client_idle_limit_in_recovery
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 0 kind: 2
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: lobj_lock_table
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 'pgpool_lobj_lock' kind: 4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: ssl
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: true kind: 1
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: ssl_key
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '/usr/local/etc/server.key' kind:
>>4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: ssl_cert
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: '/usr/local/etc/server.crt' kind:
>>4
>>>2011-02-03 08:53:20 DEBUG: pid 12138: key: debug_level
>>>2011-02-03 08:53:20 DEBUG: pid 12138: value: 0 kind: 2
>>>2011-02-03 08:53:20 DEBUG: pid 12138: loading "/usr/local/etc/pool_hba.conf" for
>>>client authentication configuration file
>>>2011-02-03 08:53:20 DEBUG: pid 12138: shmem_exit(0)
>>>
>>>
>>>
>>>
>>>thanks,
>>>Bharath
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20110203/b1ddf3bb/attachment-0001.html>
More information about the Pgpool-general
mailing list