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.Solved11KViews1like9CommentsVMwareDisks 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" } )Solved6.1KViews1like8CommentsIDC's article on Veritas Cluster Server 6.0
If your company is building your own private cloud, you need all the necessary tools to ensure business continuity and reliability of the environment. There are many challenges and questions including how to leverage your existing infrastructure, choosing which applications to migrate, and how to fully deploy. In this IDC article, lea485Views0likes1Comment