Video Screencast Help

amf&had Failed

Created: 29 Dec 2013 • Updated: 04 Apr 2014 | 6 comments
This issue has been solved. See solution.

 

Hi

 

This message comes when i try to install veritas cluster on redhat 6.3

 

code :

 

Logs are being written to /var/tmp/installer-201312291451RGt while installer is in progress

    Starting VCS: 85%                                                                                     _______________

    Estimated time remaining: (mm:ss) 0:55                                                                         6 of 7

    Performing VCS configuration ................................................................................... Done
    Starting llt ................................................................................................... Done
    Starting gab ................................................................................................... Done
    Starting amf ................................................................................................. Failed
    Starting had ................................................................................................. Failed
    Starting CmdServer ............................................................................................. Done

 

Please help

 

Regards
 

Operating Systems:
Discussion Filed Under:

Comments 6 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

Hi,
From above screenshot, amf is started however 'had' and cmdserver are failing.

What version you are trying to install? Also can u attach the install logs or paste the exact log of failure if log is too big

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

solom's picture

The version is 6.0 and where i can find  that log.

 

 

Gaurav Sangamnerkar's picture

Log file is mentioned in your first comment under var/tmp/installer/ or logs would have been moved under opt/VRTS/install... Look for latest directory

I believe that your installation is finished however starting Of component is failing

Also var /log/messages file may tell why is 'had' failing

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

solom's picture

var/log/messages attached 

AttachmentSize
messages.tar.gz 26.09 KB
Gaurav Sangamnerkar's picture

Hi,

Seems like multiple issues you may need to address

a.   You are getting a license error from CmdServer, validate if you are using the correct license or opt for keyless now and enter the valid key once you get it. 

error message from log;

Dec 29 14:05:46 TCSEC-CLU1 CmdServer[13472]: WARNING V-365-1-1 This host is not entitled to run Veritas Storage Foundation/Veritas Cluster Server.#012As set forth in the End User License Agreement (EULA) you must complete one of the two options set forth below. To comply with this condition of the EULA and stop logging of this message, you have 60 days to either:#012- make this host managed by a Management Server (see http://go.symantec.com/sfhakeyless for details and free download), or#012- add a valid license key matching the functionality in use on this host using the command 'vxlicinst' and validate using the command 'vxkeyless set NONE'

b. logs suggest that cluster is waiting for seed membership however cluster is also detecting that there is another copy of VCS already running;

Dec 29 14:05:46 TCSEC-CLU1 Had[13468]: VCS NOTICE V-16-1-11035 Waiting for cluster membership
Dec 29 14:05:46 TCSEC-CLU1 kernel: GAB INFO V-15-1-20005 Port h[GAB_USER_CLIENT (refcount 0)] registration waiting for seed port membership
Dec 29 14:06:00 TCSEC-CLU1 Had[13468]: VCS CRITICAL V-16-1-11306 Did not receive cluster membership, manual intervention may be needed for seeding
Dec 29 14:07:48 TCSEC-CLU1 Had[13670]: VCS ERROR V-16-1-11009 Exiting: Another copy of VCS may be running
 
also, GAB is not succesfully forming a membership .. I am assuming that /etc/gabtab is set to seed  two nodes however GAB on this server is still waiting for GAB from another server and hence GAB is forming port a. Either second node is not communicating or down , do you have second node running ? If yes, is the LLT working correctly, could be possible that you have a split brain situation where LLT links are broken and hence GAB is not able to see other node.
 
paste below output to confirm LLT
 
# lltstat -nvv | head -20
#gabconfig -a
 
 
Is this a fresh installation or some kind of upgrade ?
 
G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

SOLUTION