SUNW.gds

rgm_rt_SUNW.gds

GDS is a template only, used to create other data services. To facilitate this, a framework common to all data services is provided. The GDS type has all the standard resource type properties, in order for the Resource Group Manager to deal with it.



Property Name

Explanation

Value

ccr_gennum

Generation number of the file so we always use the latest

integer (usually 1)

ccr_checksum

A checksum value to validate file integrity

hex # (meaningless except to cluster)

RT_basedir

The base directory to find all the cluster-related executables in

/opt/SUNWscgds/bin

RT_description

A description of the resource type

Generic Data Service for Sun Cluster

START

The name of the start script/program

gds_svc_start

STOP

The name of the stop script/program

gds_svc_stop

VALIDATE

The name of the validate script/program

gds_validate

UPDATE

The name of the update script/program

gds_update

MONITOR_START

The name of the monitor start script/program

gds_monitor_start

MONITOR_STOP

The name of the monitor stop script/program

gds_monitor_stop

MONITOR_CHECK

The name of the monitor check program

gds_monitor_check

Single_instance

True if only a single instance can run at a time on the cluster

FALSE

Init_nodes

Where the data service can be started

RG_PRIMARIES

Installed_nodes

A comma delimited list of nodes where the RT is installed \* means all nodes

\*

Failover

True if a failover only service, false otherwise

FALSE

API_version

Version of the API (Application Programming Interface)

2

RT_version

Version of the resource type

1.0 or 3.1

Pkglist

A list of the packages installed to get this RT

SUNWscgds





GDS uses the following properties, which will be displayed in the rgm_rt file, as well as in the comma delimited list of properties for the gds based resource in a resource group



Property

Common/Extension

Description

START_TIMEOUT

Common

Time in seconds for the start script/program to finish. Default=300 Min=60 Tunable: Anytime

STOP_TIMEOUT

Common

Time in seconds for the stop script/program to finish. Default=300 Min=60 Tunable: Anytime

VALIDATE_TIMEOUT

Common

Time in seconds for the validate script/program to finish. Validate is called at resource creation and during updates of the resource or its resource group. Default=300 Min=60 Tunable: Anytime

UPDATE_TIMEOUT

Common

Time in seconds for the update script/program to finish. Update is called when the administrator updates properties of the resource or its resource group. Default=300 Min=60 Tunable: Anytime

MONITOR_START_TIMEOUT

Common

Time in seconds for the monitor_start script/program to finish. Monitor_start is called just after a resource has started. Default=300 Min=1 Tunable: Anytime

MONITOR_STOP_TIMEOUT

Common

Time in seconds for the monitor_stop script/program to finish. Monitor_stop is called just before a resource is stopped. Default=300 Min=60 Tunable: Anytime

MONITOR_CHECK_TIMEOUT

Common

Time in seconds for the monitor_check script/program to finish. Monitor_check is called when the probe script/program attempts to fail the RG to a new node. Default=300 Min=60 Tunable: Anytime

Failover_mode

Common

A property that indicates what to do if start or stop fails for the resource. HARD means relocate the resource to another node if start fails, and abort the node if stop fails. SOFT means relocate the resource to another node in the cluster if start fails, do nothing if stop fails. NONE means do nothing on either a start failure or stop failure. Default: SOFT Tunable: Anytime

Network_resources_used

Common

A comma-separated list of logical host name or shared address network resources used by the resource. For scalable services, this property must refer to shared address resources that exist in a separate resource group. For failover services, this property refers to logical host name or shared address resources that exist in the same resource group. Default: No default Tunable: When Disabled

Port_list

Common

A comma-separated list of port numbers on which the server is listening. Appended to each port number is the protocol being used by that port, for example, Port_list=80/tcp. Default: (No Default) Tunable: At creation

Load_balancing_policy

Common

This property is used only for scalable services. Values are: Lb_weighted (the default). The load is distributed according to the weights set in the Load_balancing_weights property. Lb_sticky. The set of ports is known at the time the application resources are configured. A given client/IP address is always sent to the same node Lb_sticky_wild. The port numbers are not known in advance but are dynamically assigned. A given client/IP address is always sent to the same node regardless of the port number it is coming to. Tunable: At creation

Load_balancing_weights

Common

The format is weight @ node,weight @ node, where weight is an integer that reflects the relative portion of load distributed to the specified node. The fraction of load distributed to a node is the weight for this node divided by the sum of all weights. The empty string, the default, sets a uniform distribution. Any node that is not assigned an explicit weight, receives a default weight of 1. You can specify weight 0 to assign no load to a node. Changing this property revises the distribution for new connections only. Range: 0 - 10000 Tunable: Any time

Affinity_timeout (Version 3.1 Only)

Common

Length of time in seconds during which connections from a given client IP address for any service in the resource will be sent to the same server node. 

This property is relevant only when Load_balancing_policy is either Lb_sticky or Lb_sticky_wild. In addition, Weak_affinity must be set to false (the default value).

This property is only used for scalable services.

Default: 0 Tunable: Anytime Max: -1 (infinite)

UDP_Affinity (Version 3.1 Only)

Common

If TRUE, UDP packets from a given client are forwarded to the same cluster server node the same way TCP connections are forwarded. If a client's TCP connections are "stuck" with a server node, its UDP packets are sent to that node as well. If FALSE, this behavior is not maintained, and UDP packets from a given client could end up on a different node than TCP connections from that client. 

This property only applies to resources with Load_balancing_policy=LB_STICKY or LB_STICKYWILD.

Default: False Tunable: When Disabled

Weak_Affinity (Version 3.1 Only)

Common

Provides IP affinity for sticky scalable services, except it is subject to disruptions under the following cases: (1) When a server listener starts up, for example, due to a fault monitor restart, resource failover and switchover, or when a node rejoins the cluster after failover. (2) When load_balancing_weights for the scalable resource changes due to an administrative action. Provides a low overhead alternative to the default form of IP affinity in terms of memory consumption and processor cycles. Does not use the affinity timeout value. Weak_affinity lasts for as long as none of the above listed disruptions occurs.

This property only applies to resources with Load_balancing_policy=LB_STICKY or LB_STICKYWILD.

Default: False Tunable: When Disabled

Thorough_probe_interval

Common

The number of seconds between probes of the resource using the gds_probe program. Default: 60 Tunable: Any time

Retry_count

Common

The number of times a monitor attempts to restart a resource if it fails. Default: 2 Tunable: Any time

Retry_interval

Common

The number of seconds over which to count attempts to restart a resource. Default: 300 Tunable: Any time

Monitor_retry_count

Extension

Number of PMF restarts allowed for the fault monitor. A value of -1 indicates infinite retries are allowed. Default: 4 Tunable: Anytime

Monitor_retry_interval

Extension

Time window (minutes) for fault monitor restarts. A value of -1 indicates infinite. Default: 2

Probe_timeout

Extension

Time out value for the probe (seconds) Default: 30 Min: 2 Tunable: Anytime

Child_mon_level (Only functions in 3.0u3 and after)

Extension

Child monitoring level for PMF Tunable: At creation Default: -1

Start_command

Extension

Command to start application Tunable: At creation

Stop_command

Extension

Command to stop application Tunable: At creation

Probe_command

Extension

Command to probe application Tunable: At creation

Network_aware

Extension

Determines whether the application uses network Tunable: At creation Default: True

Stop_signal

Extension

The signal sent to the application being stopped Tunable: When disabled Default: 15 Min: 1 Max: 37

Failover_enabled

Extension

Determines whether to failover when retry_count is exceeded during retry_interval Tunable: When disabled Default: TRUE






This is an example of the resource type as it exists in the rgm_rt_SUNW.gds file in the CCR:

# cat rgm_rt_SUNW.gds:6
ccr_gennum      1
ccr_checksum    A986753FB627DE86795925858F4040DE
RT_basedir      /opt/SUNWscgds/bin
RT_description  Generic Data Service for Sun Cluster
START   gds_svc_start
STOP    gds_svc_stop
VALIDATE        gds_validate
UPDATE  gds_update
MONITOR_START   gds_monitor_start
MONITOR_STOP    gds_monitor_stop
MONITOR_CHECK   gds_monitor_check
Single_instance FALSE
Init_nodes      RG_PRIMARIES
Installed_nodes \*
Failover        FALSE
Proxy   FALSE
Global_zone     FALSE
RT_system       FALSE
API_version     2
RT_version      6
Upgrade
Upgrade_from.5  ANYTIME
Upgrade_from.4  ANYTIME
Upgrade_from.3.1        ANYTIME
Upgrade_from.1.0        ANYTIME
p.Scalable      Tunable=AT_CREATION;Type=BOOLEAN;Default=FALSE;
p.START_TIMEOUT Tunable=ANYTIME;Type=INT;Default=300;Min=60;
p.STOP_TIMEOUT  Tunable=ANYTIME;Type=INT;Default=300;Min=60;
p.VALIDATE_TIMEOUT      Tunable=ANYTIME;Type=INT;Default=300;Min=60;
p.UPDATE_TIMEOUT        Tunable=ANYTIME;Type=INT;Default=300;Min=60;
p.MONITOR_START_TIMEOUT Tunable=ANYTIME;Type=INT;Default=300;Min=60;
p.MONITOR_STOP_TIMEOUT  Tunable=ANYTIME;Type=INT;Default=300;Min=60;
p.MONITOR_CHECK_TIMEOUT Tunable=ANYTIME;Type=INT;Default=300;Min=60;
p.Failover_mode Tunable=ANYTIME;Type=ENUM;Default=SOFT;Enumlist=NONE,HARD,SOFT,RESTART_ONLY,LOG_ONLY;
p.Network_resources_used        Tunable=ANYTIME;Type=STRINGARRAY;Default=;Min=0;Max=4194303;
p.Port_list     Tunable=ANYTIME;Type=STRINGARRAY;Default=;
p.Load_balancing_policy Tunable=AT_CREATION;Type=STRING;Default=LB_WEIGHTED;
p.Load_balancing_weights        Tunable=ANYTIME;Type=STRINGARRAY;Default=;
p.Affinity_timeout      Tunable=ANYTIME;Type=INT;Default=0;Min=-1;
p.UDP_Affinity  Tunable=WHEN_DISABLED;Type=BOOLEAN;Default=FALSE;
p.Weak_Affinity Tunable=WHEN_DISABLED;Type=BOOLEAN;Default=FALSE;
p.Generic_Affinity      Tunable=WHEN_DISABLED;Type=BOOLEAN;Default=FALSE;
p.Round_robin   Tunable=WHEN_DISABLED;Type=BOOLEAN;Default=FALSE;
p.Conn_threshold        Tunable=WHEN_DISABLED;Type=INT;Default=100;
p.Thorough_probe_interval       Tunable=ANYTIME;Type=INT;Default=60;Max=3600;
p.Retry_count   Tunable=ANYTIME;Type=INT;Default=2;Max=10;
p.Retry_interval        Tunable=ANYTIME;Type=INT;Default=370;Max=3600;
x.Monitor_retry_count   Tunable=ANYTIME;Type=INT;Default=4;Description="Number of PMF restarts allowed for the fault monitor";
x.Monitor_retry_interval        Tunable=ANYTIME;Type=INT;Default=2;Description="Time window (minutes) for fault monitor restarts";
x.Probe_timeout Tunable=ANYTIME;Type=INT;Default=30;Min=2;Description="Time out value for the probe (seconds)";
x.Child_mon_level       Tunable=AT_CREATION;Type=INT;Default=-1;Description="Child monitoring level for PMF";
x.Validate_command      Tunable=WHEN_DISABLED;Type=STRING;Default=;Max=4194303;Description="Command to validate the  application";
x.Start_command Tunable=WHEN_DISABLED;Type=STRINGARRAY;Min=1;Max=4194303;Description="Command to start application";
x.Stop_command  Tunable=WHEN_DISABLED;Type=STRING;Default=;Max=4194303;Description="Command to stop application";
x.Probe_command Tunable=WHEN_DISABLED;Type=STRING;Default=;Max=4194303;Description="Command to probe application";
x.Network_aware Tunable=AT_CREATION;Type=BOOLEAN;Default=TRUE;Description="Determines whether the application uses network";
x.Stop_signal   Tunable=WHEN_DISABLED;Type=INT;Default=15;Min=1;Max=37;Description="The signal sent to the application for being stopped";
x.Failover_enabled      Tunable=WHEN_DISABLED;Type=BOOLEAN;Default=TRUE;Description="Determines whether to failover when retry_count is exceeded during retry_interval";
x.Log_level     Tunable=ANYTIME;Type=ENUM;Default=INFO;Enumlist=NONE,INFO,ERR;Description="Determines the log level for event based traces";

Note: The source is distributed with gds (xfs.c)


The areas marked "User Added Code" are places in the source that are commented for


users/developers to enter their own code. Debugging user code is not covered by


normal support contracts. It is shown here to aid in debugging.

Starting the GDS Application outside of Cluster

Since GDS can be used with almost any application, only a general methodology can be given. 1. Disable the GDS resource with scswitch -n -j <resource name> 2. scswitch -D the disk group to bring it on line, if not already, or import/take the disks manually. 3. Plumb up a Logical IP address if needed for the resource. 4. Start the application (probably using the Start_command)

Troubleshooting Resources:

Always start with the messages on BOTH nodes! scstat -g <resource group> shows the status of the resource group scswitch -e -j <resource> enables a resource. scswitch -o -g <resource group> manages a resource group scswitch -z -h <node> -g <resource group> brings the resource group online GDS does not have a Debug_Level extension property, so the method for enabling debugging is:


How to enable debug mode for a gds resource :


-Configure syslog with new options:

add daemon.debug messages login, to /var/adm/debug for example.

in syslog.conf :

daemon.debug /var/adm/debug

# touch /var/adm/debug

Restart syslogd with:

# pkill -HUP syslogd

Test the addition to /etc/syslog.conf with:

# logger -p daemon.debug test

You should see output with "test" at the end of /var/adm/debug

The file that controls the debug level is called "loglevel"

To turn on debugging for a the sharedaddress type, you would do the following:


# mkdir -p /var/cluster/rgm/rt/SUNW.gds
# echo 9 > /var/cluster/rgm/rt/SUNW.gds/loglevel


restart the resource

Then GDS services have a loglevel extended property, that can be set to NONE,INFO,ERR.



Some 3.1 and 3.2:

Many of the GDS services have been written/rewritten to use a config file to enable debugging.

Check for the existence of an /etc/config file such as  SUNWsczone/sczbt/etc/config

In that file will be a line DEBUG=

set DEBUG= <your resource name> or ALL to debug all instances.

If no such file exists, use the previous method.


Restart the resource

Apr 21 19:53:24 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group gds-harg state on node v4u-4800e-doma-sin06 change to RG_PENDING_OFFLINE
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-doma-sin06 change to R_ONLINE_UNMON
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource gds-hars status on node v4u-4800e-doma-sin06 change to R_FM_UNKNOWN
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource gds-hars status msg on node v4u-4800e-doma-sin06 change to <Stopping>
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-doma-sin06 change to R_STOPPING
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-doma-sin06 change to R_ONLINE_UNMON
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-doma-sin06 change to R_OFFLINE
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource gds-hars status on node v4u-4800e-doma-sin06 change to R_FM_OFFLINE
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource gds-hars status msg on node v4u-4800e-doma-sin06 change to <>
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource apache-ip-1 status on node v4u-4800e-doma-sin06 change to R_FM_UNKNOWN
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource apache-ip-1 status msg on node v4u-4800e-doma-sin06 change to <Stopping>
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-doma-sin06 change to R_STOPPING
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource apache-ip-1 status on node v4u-4800e-doma-sin06 change to R_FM_OFFLINE
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource apache-ip-1 status msg on node v4u-4800e-doma-sin06 change to <LogicalHostname offline.>
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-doma-sin06 change to R_OFFLINE
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group gds-harg state on node v4u-4800e-doma-sin06 change to RG_OFFLINE
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group gds-harg state on node v4u-4800e-dombc-sin06 change to RG_PENDING_ONLINE
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-dombc-sin06 change to R_PRENET_STARTING
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hafoip_prenet_start> for resource <apache-ip-1>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, timeout <300> seconds
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource apache-ip-1 status on node v4u-4800e-dombc-sin06 change to R_FM_UNKNOWN
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource apache-ip-1 status msg on node v4u-4800e-dombc-sin06 change to <Starting>
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hafoip/hafoip_prenet_start>:tag=<gds-harg.apache-ip-1.10>: Calling security_clnt_connect(..., host=<v4u-4800e-dombc-sin06>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Apr 21 19:53:25 v4u-4800e-dombc-sin06 SC[,SUNW.LogicalHostname:3,gds-harg,apache-ip-1,hafoip_prenet_start]: [ID 211198 daemon.info] Completed successfully.
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hafoip_prenet_start> completed successfully for resource <apache-ip-1>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, time used: 0% of timeout <300 seconds>
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-dombc-sin06 change to R_PRENET_STARTED
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-dombc-sin06 change to R_STARTING
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hafoip_start> for resource <apache-ip-1>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, timeout <500> seconds
Apr 21 19:53:25 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hafoip/hafoip_start>:tag=<gds-harg.apache-ip-1.0>: Calling security_clnt_connect(..., host=<v4u-4800e-dombc-sin06>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.LogicalHostname:3,gds-harg,apache-ip-1,hafoip_start]: [ID 980477 daemon.info] LogicalHostname online.
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource apache-ip-1 status on node v4u-4800e-dombc-sin06 change to R_FM_ONLINE
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource apache-ip-1 status msg on node v4u-4800e-dombc-sin06 change to <LogicalHostname online.>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hafoip_start> completed successfully for resource <apache-ip-1>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, time used: 0% of timeout <500 seconds>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-dombc-sin06 change to R_JUST_STARTED
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-dombc-sin06 change to R_ONLINE_UNMON
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-dombc-sin06 change to R_STARTING
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-dombc-sin06 change to R_MON_STARTING
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hafoip_monitor_start> for resource <apache-ip-1>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, timeout <300> seconds
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <gds_svc_start> for resource <gds-hars>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, timeout <300> seconds
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource gds-hars status on node v4u-4800e-dombc-sin06 change to R_FM_UNKNOWN
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource gds-hars status msg on node v4u-4800e-dombc-sin06 change to <Starting>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 703477 daemon.notice] 38 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hafoip/hafoip_monitor_start>:tag=<gds-harg.apache-ip-1.7>: Calling security_clnt_connect(..., host=<v4u-4800e-dombc-sin06>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/SUNWscgds/bin/gds_svc_start>:tag=<gds-harg.gds-hars.0>: Calling security_clnt_connect(..., host=<v4u-4800e-dombc-sin06>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Apr 21 19:53:26 v4u-4800e-dombc-sin06 gds_svc_start[3769]: [ID 644130 user.debug] logfacility = 24
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 634592 daemon.debug] Debug Level is scds_syslog_debuglevel <9>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 525101 daemon.debug] Debug: OP 
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.LogicalHostname:3,gds-harg,apache-ip-1,hafoip_monitor_start]: [ID 579819 daemon.debug] client address: 0.0.0.0
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.LogicalHostname:3,gds-harg,apache-ip-1,hafoip_monitor_start]: [ID 574345 daemon.debug] server address: 127.0.0.1
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 551167 daemon.debug] Debug: port_cnt = 1
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 678419 daemon.debug] Debug: IP = NULL and port = 80
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 425699 daemon.debug] Debug: port_int(80), errno(0) endp()
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 338067 daemon.info] This resource does not depend on any SUNW.HAStoragePlus resources. Proceeding with normal checks.
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 665991 daemon.debug] Running User defined Validation 
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 268646 daemon.info] Extension property <network_aware> has a value of <1>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 849115 daemon.debug] Simple probe is ignored for port 80 configured on a non-tcp protocol.
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 667865 daemon.debug] Gathering network addresses from the resource list
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 248802 daemon.debug] Debug: RT open <SUNW.LogicalHostname:3>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 501374 daemon.debug] Debug: net RS TRUE
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 554679 daemon.debug] Resource <apache-ip-1> is a network resource
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.LogicalHostname:3,gds-harg,apache-ip-1,hafoip_monitor_start]: [ID 211198 daemon.info] Completed successfully.
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 236290 daemon.debug] Debug: rlist Returning 1 net res
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 517478 daemon.debug] Returning <0> from get ip address to use
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 887138 daemon.info] Extension property <Child_mon_level> has a value of <-1>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 833212 daemon.info] Attempting to start the data service under process monitor facility.
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hafoip_monitor_start> completed successfully for resource <apache-ip-1>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, time used: 0% of timeout <300 seconds>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource apache-ip-1 state on node v4u-4800e-dombc-sin06 change to R_ONLINE
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 569559 daemon.info] Start of /usr/apache/bin/apachectl start completed successfully.
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 268646 daemon.info] Extension property <network_aware> has a value of <1>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 667865 daemon.debug] Gathering network addresses from the resource list
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 248802 daemon.debug] Debug: RT open <SUNW.LogicalHostname:3>
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 501374 daemon.debug] Debug: net RS TRUE
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 554679 daemon.debug] Resource <apache-ip-1> is a network resource
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 236290 daemon.debug] Debug: rlist Returning 1 net res
Apr 21 19:53:26 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 517478 daemon.debug] Returning <0> from get ip address to use
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 218988 daemon.debug] Searching for an IPv4 mapping for apache-ip-1
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 848306 daemon.debug] Found an IPv4 mapping for apache-ip-1
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 550947 daemon.debug] Debug: Starting connect()
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 392019 daemon.debug] Starting poll
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 691392 daemon.debug] Debug: finished poll()
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_svc_start]: [ID 262966 daemon.debug] Returned from svc_wait
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <gds_svc_start> completed successfully for resource <gds-hars>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, time used: 3% of timeout <300 seconds>
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-dombc-sin06 change to R_JUST_STARTED
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-dombc-sin06 change to R_ONLINE_UNMON
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource gds-hars status on node v4u-4800e-dombc-sin06 change to R_FM_ONLINE
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource gds-hars status msg on node v4u-4800e-dombc-sin06 change to <>
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-dombc-sin06 change to R_MON_STARTING
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group gds-harg state on node v4u-4800e-dombc-sin06 change to RG_PENDING_ON_STARTED
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <gds_monitor_start> for resource <gds-hars>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, timeout <300> seconds
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/SUNWscgds/bin/gds_monitor_start>:tag=<gds-harg.gds-hars.7>: Calling security_clnt_connect(..., host=<v4u-4800e-dombc-sin06>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Apr 21 19:53:35 v4u-4800e-dombc-sin06 gds_monitor_sta[3785]: [ID 644130 user.debug] logfacility = 24
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 634592 daemon.debug] Debug Level is scds_syslog_debuglevel <9>
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 525101 daemon.debug] Debug: OP 
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 551167 daemon.debug] Debug: port_cnt = 1
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 678419 daemon.debug] Debug: IP = NULL and port = 80
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 425699 daemon.debug] Debug: port_int(80), errno(0) endp()
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 161520 daemon.debug] Calling MONITOR_START method for resource <gds-hars>.
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 354821 daemon.info] Attempting to start the fault monitor under process monitor facility.
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_monitor_start]: [ID 440530 daemon.info] Started the fault monitor.
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <gds_monitor_start> completed successfully for resource <gds-hars>, resource group <gds-harg>, node <v4u-4800e-dombc-sin06>, time used: 0% of timeout <300 seconds>
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource gds-hars state on node v4u-4800e-dombc-sin06 change to R_ONLINE
Apr 21 19:53:35 v4u-4800e-dombc-sin06 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group gds-harg state on node v4u-4800e-dombc-sin06 change to RG_ONLINE
Apr 21 19:53:35 v4u-4800e-dombc-sin06 gds_probe[3789]: [ID 644130 user.debug] logfacility = 24
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 634592 daemon.debug] Debug Level is scds_syslog_debuglevel <9>
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 525101 daemon.debug] Debug: OP 
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 551167 daemon.debug] Debug: port_cnt = 1
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 678419 daemon.debug] Debug: IP = NULL and port = 80
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 425699 daemon.debug] Debug: port_int(80), errno(0) endp()
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 268646 daemon.info] Extension property <network_aware> has a value of <1>
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 667865 daemon.debug] Gathering network addresses from the resource list
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 248802 daemon.debug] Debug: RT open <SUNW.LogicalHostname:3>
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 501374 daemon.debug] Debug: net RS TRUE
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 554679 daemon.debug] Resource <apache-ip-1> is a network resource
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 236290 daemon.debug] Debug: rlist Returning 1 net res
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 517478 daemon.debug] Returning <0> from get ip address to use
Apr 21 19:53:35 v4u-4800e-dombc-sin06 SC[,SUNW.gds:6,gds-harg,gds-hars,gds_probe]: [ID 603656 daemon.debug] unix_sock = 4





Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Jean-Christophe Lamoure

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today