OpenSolaris

Printable Version Enter a New Search
Bug ID 6691099
Synopsis ha-ids agent not validating settings in ids_config file when configuring in failover zones
State 10-Fix Delivered (Fix available in build)
Category:Subcategory suncluster:ha-informix
Keywords scqa
Responsible Engineer Neil Garthwaite
Reported Against
Duplicate Of
Introduced In
Commit to Fix osc_22
Fixed In osc_22
Release Fixed osc(osc_22) , 3.2u2_fcs(3.2u2_05) (Bug ID:2162260)
Related Bugs
Submit Date 18-April-2008
Last Update Date 7-May-2008
Description
Running:
 
  s10u4_b12b + patches
  sc32_ga + patches
  vxvm 5.0 + patches
  ha-informix from /workspace/neilga/ohacds+5.10+sparc
  IDS from dv5.sfbay:/swlib/ibm/released/informix/11/11.10/sparc-sunos

Problem:

As far as I can tell this problem exists only when running ha-ids in failover zones.  As shown below, what I am seeing is that values given in ids_config are not getting validated and thus allowing an invalid configuration to get registered and later start of the rs fails.  Below I show rs registration succeeding when ONCONFIG is not defined and when INFORMIXSQLHOSTS is not fully qualified which lead to rs not able to start and also showns that when these are defined correctly rs is able to start fine as expected.

#  grep -v ^# ids_config
RS=informixdb
RG=ids-rg
LH_RS=obsidian-1
HAS_RS=hasp4fozone
USERID=informix
ONCONFIG=
INFORMIXDIR=/informix/db
INFORMIXSERVER=infdb
INFORMIXSQLHOSTS=sqlhosts.infdb

RS_ZONE=fozone
PROJECT=default
START_TIMEOUT=150
STOP_TIMEOUT=150
# ./ids_register
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully created
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully validated
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully imported
sourcing /var/tmp/informixdb_smf_config
Registration of resource informixdb succeeded.
Validation of resource informixdb succeeded.
Registration of informixdb succeeded
# 
# clrs enable informixdb
Apr 18 16:35:10 pobsidian2 SC[SUNWsczone.start_sczsmf]:ids-rg:informixdb: start_sczsmf rc<3> - svcadm: Instance "svc:/application/sczone-agents:informixdb" is in maintenance state.
Apr 18 16:37:48 pobsidian2 SC[SUNW.gds:6,ids-rg,informixdb,gds_svc_start]: Application failed to stay up. Start method Failure.
Apr 18 16:37:48 pobsidian2 Cluster.RGM.rgmd: Method <gds_svc_start> failed on resource <informixdb> in resource group <ids-rg> [exit code <1>, time used: 100% of timeout <300 seconds>] 
resource group failed to start on chosen node; it may end up failing over to other node(s)
# 
# clrs status informixdb

=== Cluster Resources ===

Resource Name     Node Name     State           Status Message
-------------     ---------     -----           --------------
informixdb        pobsidian1    Offline         Offline
                  pobsidian2    Start failed    Faulted

# clrs disable informixdb
# clrs delete informixdb
# grep -v ^# ids_config
RS=informixdb
RG=ids-rg
LH_RS=obsidian-1
HAS_RS=hasp4fozone
USERID=informix
ONCONFIG=onconfig.infdb
INFORMIXDIR=/informix/db
INFORMIXSERVER=infdb
INFORMIXSQLHOSTS=sqlhosts.infdb

RS_ZONE=fozone
PROJECT=default
START_TIMEOUT=150
STOP_TIMEOUT=150
# 
# ./ids_register
svc:/application/sczone-agents:informixdb found in obsidian-1
svc:/application/sczone-agents:informixdb disabled in obsidian-1
svc:/application/sczone-agents:informixdb deleted in obsidian-1
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully created
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully validated
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully imported
sourcing /var/tmp/informixdb_smf_config
Registration of resource informixdb succeeded.
Validation of resource informixdb succeeded.
Registration of informixdb succeeded
#
# clrs enable informixdb
Apr 18 16:54:55 pobsidian2 SC[SUNWsczone.start_sczsmf]:ids-rg:informixdb: start_sczsmf rc<3> - svcadm: Instance "svc:/application/sczone-agents:informixdb" is in maintenance state.
Apr 18 16:57:33 pobsidian2 SC[SUNW.gds:6,ids-rg,informixdb,gds_svc_start]: Application failed to stay up. Start method Failure.
Apr 18 16:57:33 pobsidian2 Cluster.RGM.rgmd: Method <gds_svc_start> failed on resource <informixdb> in resource group <ids-rg> [exit code <1>, time used: 100% of timeout <300 seconds>] 
resource group failed to start on chosen node; it may end up failing over to other node(s)
# 
# clrs status informixdb

=== Cluster Resources ===

Resource Name     Node Name     State           Status Message
-------------     ---------     -----           --------------
informixdb        pobsidian1    Offline         Offline
                  pobsidian2    Start failed    Faulted

# clrs disable informixdb
# 
# clrs delete informixdb
# 
# grep -v ^# ids_config
RS=informixdb
RG=ids-rg
LH_RS=obsidian-1
HAS_RS=hasp4fozone
USERID=informix
ONCONFIG=onconfig.infdb
INFORMIXDIR=/informix/db
INFORMIXSERVER=infdb
INFORMIXSQLHOSTS=/informix/db/etc/sqlhosts.infdb

RS_ZONE=fozone
PROJECT=default
START_TIMEOUT=150
STOP_TIMEOUT=150
# 
# ./ids_register
svc:/application/sczone-agents:informixdb found in obsidian-1
svc:/application/sczone-agents:informixdb disabled in obsidian-1
svc:/application/sczone-agents:informixdb deleted in obsidian-1
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully created
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully validated
/var/svc/manifest/application/sczone-agents/informixdb.xml successfully imported
sourcing /var/tmp/informixdb_smf_config
Registration of resource informixdb succeeded.
Validation of resource informixdb succeeded.
Registration of informixdb succeeded
# 
# clrs enable informixdb
# clrs status informixdb

=== Cluster Resources ===

Resource Name      Node Name       State        Status Message
-------------      ---------       -----        --------------
informixdb         pobsidian1      Offline      Offline
                   pobsidian2      Online       Online

# ps -efZ | grep oninit
obsidian    root 24773 24755   0 17:03:10 ?           0:00 /informix/db/bin/oninit -y
obsidian    root 24782 24755   0 17:03:11 ?           0:00 /informix/db/bin/oninit -y
  global    root 24945  4607   0 17:03:40 console     0:00 grep oninit
obsidian    root 24755 24745   0 17:03:06 ?           0:00 /informix/db/bin/oninit -y
obsidian    root 24784 24755   0 17:03:11 ?           0:00 /informix/db/bin/oninit -y
obsidian    root 24757 24755   0 17:03:07 ?           0:00 /informix/db/bin/oninit -y
obsidian    root 24783 24755   0 17:03:11 ?           0:00 /informix/db/bin/oninit -y
obsidian    root 24756 24755   0 17:03:06 ?           0:00 /informix/db/bin/oninit -y
obsidian    root 24770 24755   0 17:03:09 ?           0:00 /informix/db/bin/oninit -y
obsidian    root 24769 24755   0 17:03:08 ?           0:00 /informix/db/bin/oninit -y
obsidian 0000200 24745     1   1 17:03:06 ?           0:03 /informix/db/bin/oninit -y
obsidian    root 24781 24755   0 17:03:11 ?           0:00 /informix/db/bin/oninit -y
#
Work Around
Ensure that the required parameter values within /opt/SUNWscids/util/ids_config correctly reflect the IDS environemnt.
Comments
N/A