Apache doesn't start
Hi! I got a VCS configured with apache web server agent. I tried to put it online (from command line it works) in the cluster and I see the following in the Apache_A.log 2016/06/16 12:45:52 VCS ERROR V-16-10061-20318 Apache:ApacheDMZ:online:<Apache::Start> Could not determine Apache Version. 2016/06/16 12:45:52 VCS ERROR V-16-10061-20133 Apache:ApacheDMZ:online:Failed to online resource Anyone can tell me why is it? I run "httpd -v" from command line and I see apache version: 2.2.15 Thanks!1.4KViews1like2CommentsUnable to start VCS on one Node. Its two node cluster
I have recently installed VCS on two blade 1500. I am unable to start VCS on both machine at the same time. If I start systemA, I noticed VCS started and on systemB unable to start. It depends on which system I am starting first. 2010/10/22 22:16:40 VCS INFO V-16-1-10196 Cluster logger started 2010/10/22 22:16:40 VCS NOTICE V-16-1-11022 VCS engine (had) started 2010/10/22 22:16:40 VCS NOTICE V-16-1-11050 VCS engine version=5.1 2010/10/22 22:16:40 VCS NOTICE V-16-1-11051 VCS engine join version=5.1.00.0 2010/10/22 22:16:40 VCS NOTICE V-16-1-11052 VCS engine pstamp=Veritas-5.1-10/06/10-14:37:00 2010/10/22 22:16:41 VCS NOTICE V-16-1-10114 Opening GAB library 2010/10/22 22:16:50 VCS NOTICE V-16-1-10619 'HAD' starting on: systemA 2010/10/22 22:17:10 VCS INFO V-16-1-10125 GAB timeout set to 30000 ms 2010/10/22 22:17:10 VCS NOTICE V-16-1-11057 GAB registration monitoring timeout set to 200000 ms 2010/10/22 22:17:10 VCS NOTICE V-16-1-11059 GAB registration monitoring action set to log system message 2010/10/22 22:17:17 VCS INFO V-16-1-10077 Received new cluster membership 2010/10/22 22:17:18 VCS NOTICE V-16-1-10112 System (systemA) - Membership: 0x3, DDNA: 0x0 2010/10/22 22:17:18 VCS NOTICE V-16-1-10322 System (Node '0') changed state from UNKNOWN to INITING 2010/10/22 22:17:18 VCS NOTICE V-16-1-10086 System (Node '0') is in Regular Membership - Membership: 0x3 2010/10/22 22:17:18 VCS NOTICE V-16-1-10086 System systemA (Node '1') is in Regular Membership - Membership: 0x3 2010/10/22 22:17:18 VCS WARNING V-16-1-50129 Operation 'haclus -modify' rejected as the node is in CURRENT_DISCOVER_WAIT state 2010/10/22 22:17:18 VCS WARNING V-16-1-50129 Operation 'haclus -modify' rejected as the node is in CURRENT_DISCOVER_WAIT state 2010/10/22 22:17:18 VCS NOTICE V-16-1-10453 Node: 0 changed name from: '' to: 'systemB' 2010/10/22 22:17:18 VCS NOTICE V-16-1-10322 System systemB (Node '0') changed state from INITING to RUNNING 2010/10/22 22:17:18 VCS NOTICE V-16-1-10322 System systemA (Node '1') changed state from CURRENT_DISCOVER_WAIT to REMOTE_BUILD 2010/10/22 22:17:19 VCS NOTICE V-16-1-10464 Requesting snapshot from node: 0 2010/10/22 22:17:19 VCS NOTICE V-16-1-10465 Getting snapshot. snapped_membership: 0x3 current_membership: 0x3 current_jeopardy_membership: 0x0 2010/10/22 22:17:27 VCS NOTICE V-16-1-10181 Group VCShmg AutoRestart set to 1 2010/10/22 22:17:27 VCS INFO V-16-1-10466 End of snapshot received from node: 0. snapped_membership: 0x3 current_membership: 0x3 current_jeopardy_membership: 0x0 2010/10/22 22:17:27 VCS WARNING V-16-1-10030 UseFence=NONE. Hence do not need fencing 2010/10/22 22:17:27 VCS ERROR V-16-1-10651 Cluster UUID received from snapshot is not matching with one existing on systemA. VCS Stopping. Manually restart VCS after configuring correct CID in the cluster. Please help me.Solved11KViews1like9CommentsVCS stop and service group offline quesiton
I have a quick question regarding service group offline. We only want to bring up/down services when we execute hagrp -online/-offline manually. When VCS shutdown, we don't want to bring up the service offline. I know if we freeze it won't go to offline entry. Do we have any other option? For an exmaple, for only we can disable the autostart. Do we have any thing for offline?Solved3.5KViews0likes2CommentsVCS Cluster not starting.
Hello All, I am having difficulties trying to get VCS started on this system. I have attached what I have got so far. I apperciate any comments or suggestions as to go from here. Thank you The hostnames in the main.cf corrosponds to that of the servers. hastatus -sum VCS ERROR V-16-1-10600 Cannot connect to VCS engine VCS WARNING V-16-1-11046 Local system not available hasys -state VCS ERROR V-16-1-10600 Cannot connect to VCS engine hastop -all -force VCS ERROR V-16-1-10600 Cannot connect to VCS engine hastart / hastart -onenode dmesg: Exiting: Another copy of VCS may be running engine_A.log 2013/10/22 15:16:43 VCS NOTICE V-16-1-11051 VCS engine join version=4.1000 2013/10/22 15:16:43 VCS NOTICE V-16-1-11052 VCS engine pstamp=4.1 03/03/05-14:58:00 2013/10/22 15:16:43 VCS NOTICE V-16-1-10114 Opening GAB library 2013/10/22 15:16:43 VCS NOTICE V-16-1-10619 'HAD' starting on: db1 2013/10/22 15:16:45 VCS INFO V-16-1-10125 GAB timeout set to 15000 ms 2013/10/22 15:17:00 VCS CRITICAL V-16-1-11306 Did not receive cluster membership, manual intervention may be needed for seeding #gabconfig -a GAB Port Memberships =============================================================== #lltstat -nvv LLT node information: Node State Link Status Address * 0 db1 OPEN bge1 UP 00:03:BA:15 bge2 UP 00:03:BA:15 1 db2 CONNWAIT bge1 DOWN bge2 DOWN bash-2.05$ lltconfig LLT is running ps -ef | grep had root 826 1 0 15:16:43 ? 0:00 /opt/VRTSvcs/bin/had root 836 1 0 15:16:45 ? 0:00 /opt/VRTSvcs/bin/hashadowSolved18KViews3likes4CommentsVCS Cluster not starting.
Hi I am facing problem while trying to start VCS . From LOG : ============================================================== tail /var/VRTSvcs/log/engine_A.log 2014/01/13 21:39:14 VCS NOTICE V-16-1-11050 VCS engine version=5.1 2014/01/13 21:39:14 VCS NOTICE V-16-1-11051 VCS engine join version=5.1.00.0 2014/01/13 21:39:14 VCS NOTICE V-16-1-11052 VCS engine pstamp=Veritas-5.1-10/06/09-14:37:00 2014/01/13 21:39:14 VCS INFO V-16-1-10196 Cluster logger started 2014/01/13 21:39:14 VCS NOTICE V-16-1-10114 Opening GAB library 2014/01/13 21:39:14 VCS NOTICE V-16-1-10619 ‘HAD’ starting on: nsscls01 2014/01/13 21:39:16 VCS INFO V-16-1-10125 GAB timeout set to 30000 ms 2014/01/13 21:39:16 VCS NOTICE V-16-1-11057 GAB registration monitoring timeout set to 200000 ms 2014/01/13 21:39:16 VCS NOTICE V-16-1-11059 GAB registration monitoring action set to log system message 2014/01/13 21:39:31 VCS CRITICAL V-16-1-11306 Did not receive cluster membership, manual intervention may be needed for seeding ============================================================================================= root@nsscls01# hastatus -sum VCS ERROR V-16-1-10600 Cannot connect to VCS engine VCS WARNING V-16-1-11046 Local system not available Please advice how can I start the VCS.Solved16KViews2likes11CommentsQuestion about fencing and co-ordinator disks
We're running VCS 4.1 MP2 on Solaris. We have 4 nodes connected via a fibre fabric to 3 arrays. Each one of these arrays has a small LUN and we've put all three of these LUNs in to a fencedg disk group. This is the diskgroup we have in /etc/vxfendg. This all works well when there are no failures. Today one of our arrays failed so we were down to only 2 disks in our fencing DG. When one of our nodes was rebooted it couldn't start it's fencing driver, which I believe was because only 2 disks were found in the fencing DG. So I'm wondering how best to solve this. We'll shortly be adding another array so we could then have 4 disks in the DG, but 4 isn't an odd number, so that's out. If we put 5 disks in the fencing DG (so put 2 on one array, and 1 on the other three), that'd seem to work. Unless an array fails and we get a split brain at the same time, at which point we only have 4 disks and the fight over the co-ordinator disks could tie. So I'm not really sure what the best course of action is. Any advice? Thanks guys. Tim.1.9KViews0likes6CommentsSFHA 6.1 / MirrorView Agent supported over Windows 2012 R2?
Hi, I see on SORT that the MirrorView agent is supported on Windows 2102 with SFHA 6.1 or 6.0.2, but i don't see an official support with Windows 2012R2. I installed a NetBackup cluster (7604) with SFHA 6.1 on Windows 2012R2 and the MirrorView agent does not retrieve the good status of my MV Group. If i copy/paste the same command on cmd, all is OK. VCS Logs: 2015/05/18 13:51:44 VCS WARNING V-16-20048-52 (POLO01) MirrorView:SG-NBU-POLOPOLO-MirrorView:online:Cmd being fired is: D:\EMC\NaviCLI\naviseccli.exe -h ww.xx.yy.zz. -secfilepath "D:\cluster" mirror -sync -listgroups -name MVGRP_POLOPOLO -role -state -condition 2>&1 2015/05/18 13:51:45 VCS ERROR V-16-20048-1113 (POLO01) MirrorView:SG-NBU-POLOPOLO-MirrorView:online:#failover_required# devices are in an invalid mix of states; administrative intervention required CMD result: D:\EMC\NaviCLI>D:\EMC\NaviCLI\naviseccli.exe -h ww.xx.yy.zz. -secfilepath "D:\cluster" mirror -sync -listgroups -name MVGRP_POLOPOLO -role -state -condition Group Name: MVGRP_POLOPOLO Role: Primary State: Consistent Condition: Active I found another post for Windows 2012, and I applied the same solution (VNX login/password configuration with VCS agent action), same problem. https://www-secure.symantec.com/connect/forums/mirror-view-agent-supported-over-windows-2012 Any idea ?Solved1.5KViews0likes2CommentsGrow a CVM_CFS on Linux 6.5 VCS 6.2
Hello I'm some newe whit Veritas Cluster, so i'll apreciate your valious help !! I have this scenario 1 ) 3 node Cluster whit CVM_CFS sharing same FS at same time 2 ) a Resource group whit NFS Sharing the CFS of the cluster to a couple o Clients Requirement : 1) grow one of the CFS ( they are VxFS aswell ) from 1 Tb to 2 Tb So i have made a lab and work but i wanna now if i'm missing some important step that i obviusly don't know ==================================== ==================================== Grow CFS Lab ==================================== ==================================== 1) Recognice New luns to Linux more /proc/scsi/scsi echo "- - -" > /sys/class/scsi_host/host3/scan echo "1" > /sys/class/fc_host/host3/issue_lip more /proc/scsi/scsi 2) Show the new Disks [root@cen-tlg-bil-01 ~]# vxdisk list DEVICE TYPE DISK GROUP STATUS ams_21000_23 auto:cdsdisk DGWORK_CRI_DSK01 DG_WORK_CRI online shared ams_21000_24 auto:cdsdisk DGWORK_CRI_DSK02 DG_WORK_CRI online shared ams_21000_26 auto:cdsdisk DGWORK_CRI_DSK03 DG_WORK_CRI online shared ams_21000_27 auto:cdsdisk DGWORK_CRI_DSK06 DG_WORK_CRI online shared ams_21000_28 auto:cdsdisk DGWORK_CRI_DSK07 DG_WORK_CRI online shared ams_21000_29 auto:cdsdisk DGWORK_CRI_DSK08 DG_WORK_CRI online shared ams_21000_30 auto:cdsdisk DGWORK_CRI_DSK09 DG_WORK_CRI online shared ams_21000_31 auto:cdsdisk DGWORK_CRI_DSK10 DG_WORK_CRI online shared ams_21000_42 auto:cdsdisk DGWORK_CRI_DSK04 DG_WORK_CRI online shared ams_21000_43 auto:cdsdisk DGWORK_CRI_DSK05 DG_WORK_CRI online shared ams_21000_44 auto:cdsdisk DGDATA_CRI_DSK01 DG_DATA_CRI online shared ams_21000_45 auto:cdsdisk DGDATA_CRI_DSK02 DG_DATA_CRI online shared ams_21000_46 auto:cdsdisk DGDATA_CRI_DSK03 DG_DATA_CRI online shared ams_21000_52 auto:cdsdisk - - online ams_21000_53 auto:cdsdisk - - online ams_21000_54 auto:cdsdisk - - online sda auto:LVM - - online invalid 3) initialize new disks vxdisksetup -i ams_21000_52 <------- New Disks vxdisksetup -i ams_21000_53 vxdisksetup -i ams_21000_54 4) Verify actual size on DG previously to add disks : [root@cen-tlg-bil-01 ~]# vxassist -g DG_DATA_CRI maxsize VxVM vxassist ERROR V-5-1-15809 No free space remaining in diskgroup DG_DATA_CRI with given constraints 5) Adding disks to the DG : [root@cen-tlg-bil-01 ~]# vxdg -g DG_DATA_CRI adddisk DGDATA_CRI_DSK04=ams_21000_52 DGDATA_CRI_DSK05=ams_21000_53 DGDATA_CRI_DSK06=ams_21000_54 6) Verify the new Maxsize of the DG : [root@cen-tlg-bil-01 ~]# vxassist -g DG_DATA_CRI maxsize Maximum volume size: 125626368 (61341Mb) 7) Verify FS size PreviouslyGrow: df -h /DATA_CRI /dev/vx/dsk/DG_DATA_CRI/VOL_DATA_CRI 60G 221M 56G 1% /DATA_CRI <---- Its 60Gb original size 9) Grow the FS : [root@cen-tlg-bil-01 ~]# vxassist -g DG_DATA_CRI maxsize Maximum volume size: 125626368 (61341Mb) < ------ Doing the grow with Mb Size it fail :( ([root@cen-tlg-bil-01 ~]# vxresize -b -F vxfs -g DG_DATA_CRI VOL_DATA_CRI +61341M [root@cen-tlg-bil-01 ~]# VxVM vxassist ERROR V-5-1-436 Cannot allocate space to grow volume to 313573376 blocks VxVM vxresize ERROR V-5-1-4703 Problem running vxassist command for volume VOL_DATA_CRI, in diskgroup DG_DATA_CRI [root@cen-tlg-bil-01 ~]# vxresize -b -F vxfs -g DG_DATA_CRI VOL_DATA_CRI +125626368 <----- So i made it with the other value 10) Verifying Cluster and FS status : df -h /dev/vx/dsk/DG_DATA_CRI/VOL_DATA_CRI 120G 236M 113G 1% /DATA_CRI <----- Grow OK to 120 Gb [root@cen-tlg-bil-01 ~]# hastatus -sum -- SYSTEM STATE -- System State Frozen A cen-tlg-bil-01 RUNNING 0 A cen-tlg-bil-02 RUNNING 0 A cen-tlg-rtg-01 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B ClusterService cen-tlg-bil-01 Y N ONLINE B ClusterService cen-tlg-bil-02 Y N OFFLINE B ClusterService cen-tlg-rtg-01 Y N OFFLINE B DATA_CRI-sg cen-tlg-bil-01 Y N ONLINE B DATA_CRI-sg cen-tlg-bil-02 Y N ONLINE B DATA_CRI-sg cen-tlg-rtg-01 Y N ONLINE B WORK_CRI-sg cen-tlg-bil-01 Y N ONLINE <------ Resource Group is OK B WORK_CRI-sg cen-tlg-bil-02 Y N ONLINE B WORK_CRI-sg cen-tlg-rtg-01 Y N ONLINE B cvm cen-tlg-bil-01 Y N ONLINE B cvm cen-tlg-bil-02 Y N ONLINE B cvm cen-tlg-rtg-01 Y N ONLINE [root@cen-tlg-bil-01 ~]# Could you please helpme to check if my steps are fine and solve my question why the grow fails if i give the value in Mb thank you in advanceSolved1.2KViews0likes1Comment