ST9990v: HORCM start fails with Raid Manager Configuration Error

Asset ID:	1-72-1341365.1
Update Date:	2011-10-25
Keywords:

Solution Type Problem Resolution Sure

Solution 1341365.1 : ST9990v: HORCM start fails with Raid Manager Configuration Error

Applies to:

Sun Storage 9990V System - Version: Not Applicable and later [Release: N/A and later ]
Sun Storage 9985V System - Version: Not Applicable and later [Release: N/A and later]
Information in this document applies to any platform.
HORCM.conf, HORCMINST, HORCM startup log

Symptoms

# /etc/init.d/HORCM.sh start

starting HORCM inst 1
HORCM inst 1 has failed to start.

You can check the cause of the HORCM start failure by looking at the HORCM Startup Log file in:

HORCM/log<$HORCMINST>/curlog

In this case $HORCMINST = 1

So in HRCOM/log1/curlog look for the HORCM startup log with a filename: horcm_.log

Look for a file with same time stamp as the error. If you can't find it in this directory, try looking at
the bklog and tmplog sub-directories.

In this case, I found the relevant file name in bklog:

bash-3.00$ more horcm_.log.110710065809
*****************************************************************************
- HORCM STARTUP LOG - Sun Jul 10 15:40:37 2011
*****************************************************************************
15:40:37-7d65e-08751- horcmgr started on Sun Jul 10 15:40:37 2011
15:40:37-80a76-08751- execvp() horcmd_01 using /etc/horcmgr [CWD=/]
15:40:37-8467c-08752- Fibre address conversion TBL has been set to '1'

P.P. : RAID Manager for Solaris
Model : RAID-Manager/Solaris
Ver&Rev: 01-20-03/06
Release: Production(GA)

ALL Rights Reserved, Copyright (c) 1998-2007, Hitachi, Ltd.

HORCM(jjs2h1acss0403a 8752) started by root (0) on Sun Jul 10 15:40:37 2011

15:40:37-9bb35-08752- horcmd_01 started on Sun Jul 10 15:40:37 2011
slmcmrhdr size = 40 bytes
rqry_test size = 208 bytes
rpprc_cmd size = 668 bytes
rread_cfg size = 152 bytes
rwait_evt size = 168 bytes
15:40:37-ad5a3-08752- [horcmcfgrdf] access(conf_file) OK.
15:40:37-b0352-08752- [horcmcfgrdf] access(check) OK.
15:40:37-b3238-08752- [horcmcfgrdf] open(conf_file) OK.
15:40:37-b64c6-08752- [horcmcfgetent] fseek(top) OK.
15:40:37-b9099-08752- ERROR: A bad devicename or groupname exists in HORCM_LDEV : JJPVSSH204030201 : JJPG4
461: line 29
15:40:37-bbef2-08752- JJPG4461 JJPVSSH204030201 18401 27:2A 0
15:40:37-bee9f-08752- ERROR: A bad devicename or groupname exists in HORCM_LDEV : JJPVSSH204030202 : JJPG4
462: line 47
15:40:37-c1cab-08752- JJPG4462 JJPVSSH204030202 18401 27:2A 1
15:40:37-c515e-08752- [horcmcfgetent] read(conf_file) OK.
15:40:37-c7a6a-08752- [horcmcfgrdf] close(conf_file) OK.
15:40:37-ca992-08752- ERROR:horcm_cfg_create
15:40:42-a5b1e-08751- horcmgr:Failed to connect to HORCM.

Cause

Duplicate device entry in HORCM.conf

Solution

Remove duplicate devicename entry in HORCM.conf

References

HDS CCI User and Reference Guide: Appendix A Maintenance Logs and Tracing Functions

Attachments

This solution has no attachment