business continuity

4549 Topics

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!
ohmartin
2 years ago Place Cluster Server
1.4KViews
1like
2Comments
Unable 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.
Solved
vcsguest
3 years ago Place Cluster Server
11KViews
1like
9Comments
VMwareDisks error
I installed SVS 6.0.1 on my server and update VRTSvcsag to version 6.0.2. Then i configured VMwareDisks resource in main.cf. VMwareDisks VMwareDisks1 ( ESXDetails = { "10.172.117.95" = "root=ISIuJWlWLwPOiWKuM" } DiskPaths = { "[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1", "[95_storage] rhel5104/rhel5104_2.vmdk" = "0:2", "[95_storage] rhel5104/rhel5104_3.vmdk" = "0:3" } ) But after had started, the VMwareDisks resource is not probed with the error message: Dec 28 01:19:42 rhel5104 AgentFramework[16962]: VCS ERROR V-16-10061-22521 VMwareDisks:VMwareDisks1:monitor:Incorrect configuration: The disk '[95_storage] rhel5104/rhel5104_3.vmdk' has incorrect RDM configuration. -------------------------------------------------------------------------------------------- The Disk UUID is automatically updated in main.cf when hastart: VMwareDisks VMwareDisks1 ( ESXDetails = { "10.172.117.95" = "root=ISIuJWlWLwPOiWKuM" } DiskPaths = { "6000C291-229e-4704-719c-2a66b8f21ad8:[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1", "6000C29a-82d7-d365-a09e-68d37698afd9:[95_storage] rhel5104/rhel5104_2.vmdk" = "0:2", "6000C29d-0bd2-901d-5b95-24934b43144e:[95_storage] rhel5104/rhel5104_3.vmdk" = "0:3" } )
Solved
Weny
4 years ago Place ApplicationHA
6.1KViews
1like
8Comments
shutdown and restart Cluster with VEA
Hi all, I have to shutdown our Hardware for a while. Now I'm looking for the best way to do that. I have two storage SAN's connected to two hardware micosoft clusternodes(Windows Server 2003) with VEA 3.2. I will shutdown the sytsems this way: 1. passive Cluster node 2. aktiv cluster node 3. first san controller 4. second san controller 5. both storage's 6. FB switche and the restart this way: 1. FB switche 2. both storage's 3. both storage san controller 4. both cluster node's Are there any things i have to regard? Do the VEA start the to resync after the restart for hours? or it will only reconnect. I hope you can help me. Thank you!
mghomer
5 years ago Place Storage Foundation for Windows
1.8KViews
0likes
3Comments
VCS 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?
Solved
mokkan
5 years ago Place Cluster Server
3.3KViews
0likes
2Comments
Maxuproc not get updated even after reboot
Hi, Got a update to change the "maxuproc for wt82369 by 1.5 times" , While verifying we make necessary modification on the Global (wt81958). Normally there is a relation between max_nprocs value and maxuproc value. FYI.. maxuprc = max_nprocs – reserved_procs (default is 5) In this case we modified the max_nprocs value from 30000 to 50000 FYI.. [root@wt81958 GLOBAL] /etc # cat /etc/system | grep max_nprocs set max_nprocs=50000 After the global zone reboot the value is not updated while we hit sysdef [root@wt81958 GLOBAL] /root # sysdef | grep processes 30000 maximum number of processes (v.v_proc) 29995 maximum processes per user id (v.v_maxup) Can anyone please assist us if any thing we missed in this to make the necessary changes to replicate. Awaiting for your valuable suggestions. Thanks, senthilsam
Solved
senthilsam
5 years ago Place Storage Foundation
3.2KViews
0likes
3Comments
VCS 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/hashadow
Solved
br1
5 years ago Place Cluster Server
18KViews
3likes
4Comments
vxlicrep ERROR V-21-3-1015 Failed to prepare report for key
Dear all, we got a INFOSCALE FOUNDATION LNX 1 CORE ONPREMISE STANDARD PERPETUAL LICENSE CORPORATE. I have installed key using the vxlicinst -k <key> command. But when I want to check it using vxlicrep I'm getting this error for the given key: vxlicrep ERROR V-21-3-1015 Failed to prepare report for key = <key> We have Veritas Volume Manager 5.1 (VRTSvxvm-5.1.100.000-SP1_RHEL5 and VRTSvlic-3.02.51.010-0) running on RHEL 5.7 on 64 bits. I've read that the next step is to run vxkeyless set NONE, but I'm afraid to run this until I cannot see the license reported correctly by vxlicrep. What can I do to fix it? Thank you in advance. Kind regards, Laszlo
Laszlo_Budai
7 years ago Place Storage Foundation
4.2KViews
0likes
7Comments
Unable to initialize disk using vxdisksetup
I'm in the middle of setting up Storage Foundation for Oracle RAC 5.0 on RHEL 4 Update 3. I have Sun StorEdge 6920 as the storage array. Here's wat happened: - SFORAC documentation asked me to create the minimum possible LUN on the array for coordinator disks - I created the smallest LUN (16 MB) on the array - When trying to initialize it (using vxdisksetup -i Disk_0 format=cdsdisk) I got the error about disk being too small - I extended the disk size on the array to 50 MB - The servers still saw the coordinator disks (/dev/sda to /dev/sdc) of size 16 MB. Since I'm not well versed in Linux I rebooted both servers so they can see the new LUN size Fdisk is able to view the new LUN size & manipulate it as well however vxdisksetup still would not allow me to initialize the disks. I've tried the following: # fdisk /dev/sda Chose o & then w # vxdisksetup -i Disk_0 format=cdsdisk VxVM vxdisk ERROR V-5-1-535 Device Disk_0: Invalid attributes # vxdisksetup -i Disk_0 format=cdsdisk VxVM vxdisksetup ERROR V-5-2-0 Disk is too small for supplied parameters Then I zero filled the LUN: # dd if=/dev/zero of=/dev/sda bs=1M Repeated the steps above to get the same errors. I've also tried to use simple format but it doesnt work either. Have I missed out something or is it just that VxVM does not like volumes expanded by the array? Please help.
Khurram_Tariq
7 years ago Place Storage Foundation
4.3KViews
0likes
6Comments
Video - Managing Evacuation Plan in Veritas Resiliency Platform
The following video covers how to evacuate your assets to Azure using Veritas Resiliency Platform. The following Evacuation Plan operations are shown: Generate an evacuation plan Rehearsal Cleanup rehearsal Evacuate to Azure data center The next video covers the following: How and when to regenerate an evacuation plan. How todeal with the errors which occur during the evacuation operation. Evacuation Plan Blog
PallaviA
7 years ago Place Veritas Resiliency Platform
1.8KViews
4likes
0Comments