Professional Documents
Culture Documents
http://support.veritas.com/docs/250515
Details:
The vxsvc process or server process for VERITAS Enterprise Administrator (VEA) is
restarted with the following sequence:
If, by doing the above command, you encounter errors such as the following:
# ./vxsvc -k
Request is in process..
Server was not running
This means that the kill script did not find the PID of vxsvc. The vxsvc process
should be killed:
# ps -ef | grep vxsvc
root 520 1 0 13:09:28 ? 1:50 /opt/VRTSob/bin/vxsvc -r
/opt/VRTSob/config/Registry
# kill 520
If the following error occurs, kill the vxsvc process and remove the
/var/vx/isis/vxisis.lock file, then proceed to Step #2.
vxsvc: Another instance of vxsvc seems to be running.
Please verify with the command ps(1m).
If no other instance is running, remove the file:
/var/vx/isis/vxisis.lock
And restart vxsvc
Note: Stopping and restarting isisd or vxsvc will not affect a live running
system.
Products Applied:
ServPoint NAS 1.2.1, 1.2.2
Subjects:
ServPoint NAS
Application: Client Support, Device Management, How To
Languages:
English (US)
Operating Systems:
Solaris
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS
IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES,
EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE
LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC
SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.