Understanding RestartLimit for non critical ressource
Hello, we have some trouble with our oracle listener process. sometimes the listener is killed by vcs. We dont know why. xxx VCS ERROR V-16-2-13027 (node1) Resource(lsnr-ORADB1) - monitor procedure did not complete within the expected time. xxx VCS ERROR V-16-2-13210 (node1) Agent is calling clean for resource(lsnr-ORADB1) because 4 successive invocations of the monitor procedure did not complete within the expected time. xxx VCS NOTICE V-16-20002-42 (node1) Netlsnr:lsnr-ORADB1:clean:Listener(LISTENER) kill TERM 2342 xxx VCS INFO V-16-2-13068 (node1) Resource(lsnr-ORADB1) - clean completed successfully. xxx VCS INFO V-16-2-13026 (node1) Resource(lsnr-ORADB1) - monitor procedure finished successfully after failing to complete within the expected time for (4) consecutive times. xxx VCS INFO V-16-1-10307 Resource lsnr-ORADB1 (Owner: unknown, Group: ORADB1) is offline on node1 (Not initiated by VCS) However, Resource(lsnr-ORADB1) is set to non-critical, to prevent an failover. I'll now set an RestartLimit for Resource(lsnr-ORADB1) to let the cluster try to restart the listener, but what happen if this failed? Will the Ressouce still staying offline or initiate the cluster an failover for the whole ResourceGroup? thanks in advance for any help!
VCS clustered Enterprise vault migrate index service to new node
Hi, We have three node cluster for Enterprise vault in Veritas Cluster server, the node details are as follows: Node 1: EV server with all services Node 2: SQL server Node 3: Spare server for EV service failover and SQl service failover. Also GCO and VVR is configured for SQl server and EV server volumes are replicating using VVR but are not in VCS control. Now we want to remove index service from EV server (node 1) and add it to new server, also add new server to the cluster. Can anybody share the steps we should follow from VCS end to perform above changes.Volume is mounted on two split-brain nodes in VCS 6.0
I have built a three-node cluster using vcs 6.0 in sles 11 sp1. Here is the configuration: main.cf: include "OracleASMTypes.cf" include "types.cf" include "Db2udbTypes.cf" include "OracleTypes.cf" include "SybaseTypes.cf" cluster vcscluster ( ClusterAddress = "192.168.4.10" SecureClus = 1 UseFence = SCSI3 ) system vcs1 ( ) system vcs2 ( ) system vcs3 ( ) group ClusterService ( SystemList = { vcs1 = 0, vcs2 = 1, vcs3 = 2 } AutoStartList = { vcs1, vcs2, vcs3 } OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) IP webip ( Device = eth0 Address = "192.168.4.10" NetMask = "255.255.255.0" ) NIC csgnic ( Device = eth0 ) webip requires csgnic // resource dependency tree // // group ClusterService // { // IP webip // { // NIC csgnic // } // } group apache ( SystemList = { vcs1 = 0, vcs2 = 1, vcs3 = 2 } AutoStartList = { vcs1 } ) DiskGroup share_dg ( DiskGroup = share_dg ) Mount apache_fs ( MountPoint = "/srv/www/htdocs" BlockDevice = "/dev/vx/dsk/share_dg/apache" FSType = vxfs FsckOpt = "-y" ) apache_fs requires share_dg // resource dependency tree // // group apache // { // Mount apache_fs // { // DiskGroup share_dg // } // } # lltstat -l LLT link information: link 0 eth1 on ether hipri mtu 1500, sap 0xcafe, broadcast FF:FF:FF:FF:FF:FF, addrlen 6 txpkts 129728 txbytes 14155153 rxpkts 119866 rxbytes 7909769 latehb 0 badcksum 0 errors 0 link 1 eth2 on ether lowpri mtu 1500, sap 0xcafe, broadcast FF:FF:FF:FF:FF:FF, addrlen 6 txpkts 49369 txbytes 2400217 rxpkts 50476 rxbytes 2480391 latehb 0 badcksum 0 errors 0 # vxfenconfig -l I/O Fencing Configuration Information: ====================================== Single Disk Flag : 0 Count : 3 Disk List Disk Name Major Minor Serial Number Policy /dev/vx/rdmp/disk_2s3 201 67 7ae525da dmp /dev/vx/rdmp/disk_1s3 201 51 27cddc71 dmp /dev/vx/rdmp/disk_0s3 201 35 132a74e8 dmp # vxfenadm -d I/O Fencing Cluster Information: ================================ Fencing Protocol Version: 201 Fencing Mode: SCSI3 Fencing SCSI3 Disk Policy: dmp Cluster Members: * 0 (vcs1) 1 (vcs2) 2 (vcs3) RFSM State Information: node 0 in state 8 (running) node 1 in state 8 (running) node 2 in state 8 (running) # hastatus -summary -- SYSTEM STATE -- System State Frozen A vcs1 RUNNING 0 A vcs2 RUNNING 0 A vcs3 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B ClusterService vcs1 Y N ONLINE B ClusterService vcs2 Y N OFFLINE B ClusterService vcs3 Y N OFFLINE B apache vcs1 Y N OFFLINE B apache vcs2 Y N OFFLINE B apache vcs3 Y N ONLINE #df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 7218432 4356176 2495576 64% / devtmpfs 995788 212 995576 1% /dev tmpfs 995788 0 995788 0% /dev/shm tmpfs 4 0 4 0% /dev/vx /dev/vx/dsk/share_dg/apache 512000 3285 476928 1% /srv/www/htdocs When I disconnect the net link of eth1/eth2 in VCS3. Apache is brought up in vcs1. But when I check vcs3, the mount point still exists . And after several minutes, a kernel panic occur in vcs3. I think it is very dangerous that a volume is mounted on two split-brain nodes . How can I prevent this happens?