免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 3889 | 回复: 4
打印 上一主题 下一主题

MCSG:Reason: A crucial package failed [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2003-12-09 06:09 |只看该作者 |倒序浏览
都是按照标准做的,有这个错误,不知道有没有人碰到过:
Dec  9 04:20:58 sis01 cmcld: 1 nodes have formed a new cluster, sequence #2
Dec  9 04:20:58 sis01 cmcld: The new active cluster membership is: sis01(id=1)
Dec  9 04:20:58 sis01 cmcld: Request from node sis01 to start package pkg1 on node sis01.
Dec  9 04:20:58 sis01 cmcld: Executing '/etc/cmcluster/pkg1/pkg1.sh  start' for package pkg1, as service PKG*25346.
Dec  9 04:20:58 sis01 LVM[3169]: vgchange -a e vg02
Dec  9 04:20:59 sis01 LVM[3166]: vgchange -a e vg01
Dec  9 04:21:00 sis01 CM-pkg1[3224]: cmmodnet -a -i 10.128.64.7 10.128.64.0
Dec  9 04:21:00 sis01 CM-pkg1[3229]: cmrunserv service1 >;>; /etc/cmcluster/pkg1/pkg1.sh.log 2>;&1 /usr/bin/cd /oracle_data
Dec  9 04:21:00 sis01 cmcld: Service service1 terminated due to an exit(0).
Dec  9 04:21:00 sis01 cmcld: Service PKG*25346 terminated due to an exit(0).
Dec  9 04:21:00 sis01 cmcld: Started package pkg1 on node sis01.
Dec  9 04:21:00 sis01 cmcld: Service service1 in package pkg1 has gone down.
Dec  9 04:21:00 sis01 cmsrvassistd[3146]: The cluster daemon aborted our connection.
Dec  9 04:21:00 sis01 cmcld: Service fail fast is set. Node will be failed.
Dec  9 04:21:00 sis01 cmcld: Failed node in response to failure of package pkg1.
Dec  9 04:21:00 sis01 cmcld: Halting sis01 to preserve data integrity
Dec  9 04:21:00 sis01 cmcld: Reason: A crucial package failed
Dec  9 04:21:00 sis01 cmsrvassistd[3146]: Lost connection with ServiceGuard cluster daemon (cmcld): Software caused connection abort
Dec  9 04:21:00 sis01 cmlvmd: Could not read messages from /usr/lbin/cmcld: Software caused connection abort
Dec  9 04:21:00 sis01 cmlvmd: CLVMD exiting
Dec  9 04:21:00 sis01 cmtaped[3150]: The cluster daemon aborted our connection.
Dec  9 04:21:00 sis01 cmtaped[3150]: cmtaped terminating. (ATS 1.14)

论坛徽章:
0
2 [报告]
发表于 2003-12-09 17:55 |只看该作者

MCSG:Reason: A crucial package failed

service1的脚本有问题

论坛徽章:
0
3 [报告]
发表于 2003-12-09 23:35 |只看该作者

MCSG:Reason: A crucial package failed

service 的脚本如下:



PACKAGE_NAME        pkg1               



PACKAGE_TYPE                        FAILOVER



FAILOVER_POLICY                        CONFIGURED_NODE




FAILBACK_POLICY                        MANUAL



NODE_NAME   sis02
NODE_NAME   sis01       
       




AUTO_RUN                        YES




LOCAL_LAN_FAILOVER_ALLOWED     NO       



NODE_FAIL_FAST_ENABLED                NO




RUN_SCRIPT        /etc/cmcluster/pkg1/pkg1.sh               
RUN_SCRIPT_TIMEOUT                NO_TIMEOUT
HALT_SCRIPT                /etc/cmcluster/pkg1/pkg1.sh       
HALT_SCRIPT_TIMEOUT                NO_TIMEOUT


# Enter the names of the storage groups configured for this package.
# Repeat this line as necessary for additional storage groups.
#
# Storage groups are only used with CVM disk groups. Neither
# VxVM disk groups or LVM volume groups should be listed here.
# By specifying a CVM disk group with the STORAGE_GROUP keyword
# this package will not run until the VxVM-CVM-pkg package is
# running and thus the CVM shared disk groups are ready for
# activation.
#
# NOTE: Should only be used by applications provided by
#       Hewlett-Packard.
#
# Example : STORAGE_GROUP  dg01
#           STORAGE_GROUP  dg02
#           STORAGE_GROUP  dg03
#           STORAGE_GROUP  dg04
#


SERVICE_NAME                   service1                  
SERVICE_FAIL_FAST_ENABLED      YES                       
SERVICE_HALT_TIMEOUT           300            


# Enter the network subnet name that is to be monitored for this package.
# Repeat this line as necessary for additional subnet names.  If any of
# the subnets defined goes down, the package will be switched to another
# node that is configured for this package and has all the defined subnets
# available.
# The subnet names could be IPv4 or IPv6. The network subnet
# names that are to be monitored for this package could be a mix
# of IPv4 or IPv6 subnet names

SUBNET        10.128.64.0               
SUBNET  192.168.0.0

# The keywords RESOURCE_NAME, RESOURCE_POLLING_INTERVAL,               
# RESOURCE_START, and RESOURCE_UP_VALUE are used to specify Package   
# Resource Dependencies.  To define a package Resource Dependency, a   
# RESOURCE_NAME line with a fully qualified resource path name, and   
# one or more RESOURCE_UP_VALUE lines are required.  The               
# RESOURCE_POLLING_INTERVAL and the RESOURCE_START are optional.      
#
# The RESOURCE_POLLING_INTERVAL indicates how often, in seconds, the   
# resource is to be monitored.  It will be defaulted to 60 seconds if  
# RESOURCE_POLLING_INTERVAL is not specified.                          
#
# The RESOURCE_START option can be set to either AUTOMATIC or DEFERRED.
# The default setting for RESOURCE_START is AUTOMATIC.  If AUTOMATIC   
# is specified, ServiceGuard will start up resource monitoring for     
# these AUTOMATIC resources automatically when the node starts up.     
# If DEFERRED is selected, ServiceGuard will not attempt to start      
# resource monitoring for these resources during node start up.  User  
# should specify all the DEFERRED resources in the package run script  
# so that these DEFERRED resources will be started up from the package
# run script during package run time.                                 
#                                                                     
# RESOURCE_UP_VALUE requires an operator and a value.  This defines   
# the resource 'UP' condition.  The operators are =, !=, >;, <, >;=,     
# and <=, depending on the type of value.  Values can be string or     
# numeric.  If the type is string, then only = and != are valid        
# operators.  If the string contains whitespace, it must be enclosed   
# in quotes.  String values are case sensitive.  For example,         
#
#                                         Resource is up when its value is
#                                         --------------------------------
#         RESOURCE_UP_VALUE        = UP                        "UP"
#         RESOURCE_UP_VALUE        != DOWN                        Any value except "DOWN"
#         RESOURCE_UP_VALUE        = "On Course"                "On Course"
#
# If the type is numeric, then it can specify a threshold, or a range to
# define a resource up condition.  If it is a threshold, then any operator
# may be used.  If a range is to be specified, then only >; or >;= may be used
# for the first operator, and only < or <= may be used for the second operator.
# For example,
#                                         Resource is up when its value is
#                                         --------------------------------
#         RESOURCE_UP_VALUE     = 5                5                    (threshold)
#         RESOURCE_UP_VALUE     >; 5.1                greater than 5.1    (threshold)
#         RESOURCE_UP_VALUE     >; -5 and < 10        between -5 and 10   (range)
#
# Note that "and" is required between the lower limit and upper limit
# when specifying a range.  The upper limit must be greater than the lower
# limit.  If RESOURCE_UP_VALUE is repeated within a RESOURCE_NAME block, then
# they are inclusively OR'd together.  Package Resource Dependencies may be
# defined by repeating the entire RESOURCE_NAME block.
#
# Example : RESOURCE_NAME               /net/interfaces/lan/status/lan0
#             RESOURCE_POLLING_INTERVAL        120
#             RESOURCE_START                AUTOMATIC
#             RESOURCE_UP_VALUE                = RUNNING
#             RESOURCE_UP_VALUE                = ONLINE
#
#           Means that the value of resource /net/interfaces/lan/status/lan0
#           will be checked every 120 seconds, and is considered to
#           be 'up' when its value is "RUNNING" or "ONLINE".
#
# Uncomment the following lines to specify Package Resource Dependencies.
#
#RESOURCE_NAME                    <Full_path_name>;
#RESOURCE_POLLING_INTERVAL  <numeric_seconds>;
#RESOURCE_START             <AUTOMATIC/DEFERRED>;
#RESOURCE_UP_VALUE            <op>; <string_or_numeric>; [and <op>; <numeric>;]

论坛徽章:
0
4 [报告]
发表于 2003-12-09 23:59 |只看该作者

MCSG:Reason: A crucial package failed

应是几个超时设置不对,我再试,不知william还能给出其它建议否?

论坛徽章:
0
5 [报告]
发表于 2003-12-12 15:46 |只看该作者

MCSG:Reason: A crucial package failed

你贴出的这个不是service脚本.

应该是pkg1所在子目录下后缀为.cntl的文件,其中有一段是关于service的:
比如:
SERVICE_NAME[0]=service1
SERVICE_CMD[0]="/etc/cmcluster/pkg1/testmon.sh"
SERVICE_RESTART[0]=""

这里的testmon.sh就是service脚本
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP