Hello Hideo - I'm a bit lost with this info. If I understand you correct your postgresql.conf isn't in /var/lib/pgsql directory and pgsql RA script can't find it if $OCF_RESKEY_config isn't set. Then why not to just simply set $OCF_RESKEY_config and point it to correct place instead of introducing new parameter to disable parsing of configuration file?
The other option would be to change pgsql RA in a way that it won't parse config file if $OCF_RESKEY_config isn't set and in this case assume that $OCF_RESKEY_socketdir isn't set as well. That could potentially create problems for Ubuntu users for whom that functionality was created. On Wed, Aug 18, 2010 at 8:46 PM, <renayama19661...@ybb.ne.jp> wrote: > Hi All, > > We confirmed that an error of pgsql occurred by the setting that we did not > use logd for. > When we use a syslog, this occurs. > And when $OCF_RESKEY_config is handled by default, an error occurs when > meta-data processing is > performed. > * OCF_RESKEY_config of the user will not be /var/lib/pgsql/data in many > cases. > > (snip) > Aug 19 11:34:09 srv01 crmd: [9317]: info: match_graph_event: Action > prmIpPostgreSQLDB2_monitor_10000 > (10) confirmed on srv01 (rc=0) > Aug 19 11:34:09 srv01 pgsql[9870]: INFO: could not change directory to > "/var/lib/heartbeat/cores/root" > server starting > Aug 19 11:34:09 srv01 pgsql[9870]: INFO: PostgreSQL start command sent. > Aug 19 11:34:09 srv01 pgsql[9870]: INFO: PostgreSQL is down > Aug 19 11:34:10 srv01 pgsql[9870]: INFO: PostgreSQL is started. > Aug 19 11:34:10 srv01 pgsql[9975]: ERROR: Cannot find configuration file > /var/lib/pgsql/data/postgresql.conf ----> ***** An error of the meta-data > processing after the start > processing > (snip) > Aug 19 11:35:09 srv01 pgsql[10526]: ERROR: Cannot find configuration file > /var/lib/pgsql/data/postgresql.conf ----> ***** An error of the lrmadmin -M > ocf pgsql heartbeat > processing > (snip) > > Even if pgsql treats OCF_RESKEY_config by meta-data processing, there is not > a meaning. > Because OCF_RESKEY_config is because it is not set. > > * ha.cf > > pacemaker on > #use_logd on > debug 0 > udpport 694 > keepalive 2 > warntime 20 > deadtime 24 > initdead 48 > logfacility local1 > > The pgsql analyze a config file by get_pgsql_param processing. > There is the problem in this analysis. > > Two revisions think me to be thought. > > Pattern 1) A method to choose analysis of config file in an ocf parameter. > * For example, add a parameter of parse_config to pgsql. > * Because many users do not need analysis of config file. > > Pattern 2) By a call except start,monitor,status,stop, pgsql do not do > get_pgsql_param processing. > > It is the problem that I limited when cluster do not use logd, but please > please tell an opinion of > all of you. > > Best Regards, > Hideo Yamauchi. > > _______________________________________________________ > Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev > Home Page: http://linux-ha.org/ > -- Serge Dubrouski. _______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
