Unable to configure VEA (VERITAS ENTERPRISE ADMINISTRATOR) after installing 5.0MP3
Article ID: 100006067
Updated On:
Description
Error Message
# /opt/VRTSobESC[K/bin/vxsvc -m
Current state of server : UNKNOWN STATE
In addition to the above state of vxsvc the following was seen in the /var/vx/isis/vxisis.log
Tue Apr 12 11:25:10 2011:3966798736:Agent may be down
Tue Apr 12 11:34:11 2011:4052814736:VxREG: Initiating the Registration with corbaloc:vxssiop:localhost:1556:StorageAgent_SecureSvc/LeafRegistration
Tue Apr 12 11:34:11 2011:4052814736:CORBA Exception in ManagerRegistrationImpl::handleTypeObjects: NO_PERMISSION, IDL:omg.org/CORBA/NO_PERMISSION:1.0
Tue Apr 12 11:34:11 2011:4052814736:CORBA Exception in ManagerRegistrationImpl::handleTypeObjects: NO_PERMISSION, IDL:omg.org/CORBA/NO_PERMISSION:1.0
Tue Apr 12 11:34:11 2011:4052814736:CORBA Exception in ManagerRegistrationImpl::handleTypeObjects: NO_PERMISSION, IDL:omg.org/CORBA/NO_PERMISSION:1.0
Tue Apr 12 11:34:11 2011:4052814736:CORBA Exception in ManagerRegistrationImpl::handleTypeObjects: NO_PERMISSION, IDL:omg.org/COR
Cause
The issue was an incorrect VRTSatlocal.conf configuration file. The VRTSatlocal.conf is used by authentication services to authenticate root. As par to the authentication process we read the VRTSatlocal.conf file. The file format was incorrect which lead to the vxsvc process reporting "UNKNOWN STATE" and also prevented the GUI (Graphical User Interface) providers from registering.
Some reasons for having an incorrect VRTSatlocal.conf file.
Resolution
The solution was to backup the current VRTSatlocal.conf file and reinstall VRTSatServer RPM that came with Storage Foundation 5.0MP3 so that the default VRTSatlocal.conf would be put in place.
Once the default VRTSatlocal.conf was in place we did the following.
1. Stop vxsvc, pbx and vxpal processes.
Note: Because of the state of vxsvc it maybe neccessary to kill ( kill -9
ps -ef |egrep "vxpal|vxsvc|pbx"
root 5185 1 0 Apr13 ? 00:00:00 /opt/VRTSpbx/bin/pbx_exchange
root 13089 1 0 Apr13 ? 00:00:04 /opt/VRTSob/bin/vxsvc -r /etc/vx/isis/Registry -e
root 17864 1 0 Apr13 ? 00:00:00 /opt/VRTSobc/pal33/bin/vxpal -a gridnode -x
root 18191 1 0 Apr13 ? 00:00:00 /opt/VRTSobc/pal33/bin/vxpal -a actionagent -x
root 21255 1 0 Apr13 ? 00:00:03 /opt/VRTSobc/pal33/bin/vxpal -a StorageAgent -x
root 22163 2506 0 10:16 pts/1 00:00:00 egrep vxpal|vxsvc|pbx
root 23079 1 0 Apr13 ? 00:00:01 /opt/VRTSobc/pal33/bin/vxpal -a DBEDAgent -x
/etc/init.d/vxpal.DBEDAgent stop
/etc/init.d/vxpal.StorageAgent stop
/etc/init.d/vxpal.gridnode stop
/etc/init.d/vxpal.actionagent stop
/etc/init.d/vxpbx_exchanged stop
/opt/VRTS/bin/vxsvc -k
2. Startup up the pbx_exchange process. This process is required before starting vxsvc.
/etc/init.d/vxpbx_exchanged start
ps -ef |grep "pbx"
root 5185 1 0 Apr13 ? 00:00:00 /opt/VRTSpbx/bin/pbx_exchange
3. Start vxsvc process and verify the state of the process is running.
/opt/VRTSob/bin/vxsvc -r /etc/vx/isis/Registry -e
/opt/VRTSob/bin/vxsvc –m
RUNNING
4. Once the above processes are running you can then configure VEA using `/opt/VRTS/install/installvm –configure`
Once the configuration is complete the following processes will be seen.
ps -ef |egrep "vxpal|vxsvc|pbx"
root 5185 1 0 Apr13 ? 00:00:00 /opt/VRTSpbx/bin/pbx_exchange
root 13089 1 0 Apr13 ? 00:00:04 /opt/VRTSob/bin/vxsvc -r /etc/vx/isis/Registry -e
root 17864 1 0 Apr13 ? 00:00:00 /opt/VRTSobc/pal33/bin/vxpal -a gridnode -x
root 18191 1 0 Apr13 ? 00:00:00 /opt/VRTSobc/pal33/bin/vxpal -a actionagent -x
root 21255 1 0 Apr13 ? 00:00:03 /opt/VRTSobc/pal33/bin/vxpal -a StorageAgent -x
root 22163 2506 0 10:16 pts/1 00:00:00 egrep vxpal|vxsvc|pbx
root 23079 1 0 Apr13 ? 00:00:01 /opt/VRTSobc/pal33/bin/vxpal -a DBEDAgent -x
Applies To
RHEL5
Storage Foundation 5.0MP3 and 5.0MP3RP3
Issue/Introduction
