After a user logs off of an OpsCenter server some of the OpsCenter services stop.
| Article:TECH124639 | | | Created: 2010-01-11 | | | Updated: 2011-10-15 | | | Article URL http://www.symantec.com/docs/TECH124639 |
Problem
After a user logs off of an OpsCenter server some of the OpsCenter services stop.
Solution
Overview:
After a user logs off of an OpsCenter server some of the OpsCenter services stop.
Scenario A:
OpsCenter Server is installed but the OpsCenter Agent is not installed.
The Symantec OpsCenter Server Service and the Symantec OpsCenter WebServer Service will not be running after logging out of Windows.
See Image 1 below.
Image 1:
Scenario B:
Both OpsCenter Server and the OpsCenter Agent are installed.
The Symantec OpsCenter Server Service, the Symantec OpsCenter WebServer Service, and the Symantec OpsCenter Agent Service will not be running after logging out of Windows.
See Image 2 below.
Image 2:
Scenario C:
Only the OpsCenter Agent is installed.
The Symantec OpsCenter Agent Service will be not running after logging out of Windows.
Workaround:
Scenario A:
OpsCenter Server is installed but the OpsCenter Agent is not installed.
1.) Open the <install_path>\Symantec\OpsCenter\Server\bin\OpsCenterServerService.xml file with a text editor.
2.) Locate the <CmdArg value=" -Xms512M -Xmx1024M -XX:PermSize=64M -XX:MaxPermSize=128M com.symantec.nbu.nom.NomServerManager "/> line in this file.
3.) Add the value -Xrs to this line so it reads as follows:
<CmdArg value=" -Xrs -Xms512M -Xmx1024M -XX:PermSize=64M -XX:MaxPermSize=128M com.symantec.nbu.nom.NomServerManager "/>
Note: Do not add the -Xrs value to the end of the line.
See Image 3 and Image 4 below.
Image 3:
Image4:
4.) Open the <install_path>\Symantec\OpsCenter\gui\bin\OpsCenterGUIService.xml file with a text editor.
5.) Locate the <EnvVar name="JAVA_OPTS" value =" -Xms512m -Xmx1024m -XX:MaxPermSize=128m -Dvrtsat.home="C:\PROGRA~1\Symantec\OPSCEN~1\server\eat" -Dvrtsat.libpath="C:\PROGRA~1\Symantec\OPSCEN~1\server\eat\bin" -DEAT_HOME_DIR="C:\PROGRA~1\Symantec\OPSCEN~1\server\eat" -DEAT_DATA_DIR="C:\PROGRA~1\VERITAS\Security\AUTHEN~1"" /> lines in this file.
Note: There are two of these lines in the OpsCenterGuiService.xml file.
6.) Add the value -Xrs to both of these lines so they read as follows:
<EnvVar name="JAVA_OPTS" value =" -Xrs -Xms512m -Xmx1024m -XX:MaxPermSize=128m -Dvrtsat.home="E:\PROGRA~1\Symantec\OPSCEN~1\server\eat"-Dvrtsat.libpath="E:\PROGRA~1\Symantec\OPSCEN~1\server\eat\bin"-DEAT_HOME_DIR="E:\PROGRA~1\Symantec\OPSCEN~1\server\eat"-DEAT_DATA_DIR="C:\PROGRA~1\VERITAS\Security\AUTHEN~1"" />
Note: Do not add the -Xrs value to the end of the line.
7.) Stop the OpsCenter services if they are running and restart them to read in the changes.
See Image 5 and Image 6 below.
Image 5:
Image 6:
Scenario B:
Both OpsCenter Server and the OpsCenter Agent are installed.
1.) Follow steps 1 - 7 in Scenario A above.
2.) Open the <install_path>\Symantec\OpsCenter\Agent\bin\OpsCenterAgentService.xml file with a text editor.
3.) Locate the <CmdArg value=" -Xrs -Xms512M -Xmx1024M -XX:PermSize=64M -XX:MaxPermSize=128M com.symantec.nbu.nom.agent.core.Agent"/> line in this file.
4.) Add the value -Xrs to this line so it reads as follows:
<CmdArg value=" -Xrs -Xms512M -Xmx1024M -XX:PermSize=64M -XX:MaxPermSize=128M com.symantec.nbu.nom.agent.core.Agent"/>
Note: Do not add the -Xrs value to the end of the line.
5.) Stop the OpsCenter services if they are running and restart them to read in the changes.
See Image 7 and Image 8 below:
Image 7:
Image 8:
Scenario C:
Only the OpsCenter Agent is installed.
1.) Follow steps 2 - 5 in Scenario B above.
Resolution:
The issue described above has been corrected in the 7.0.1 release of OpsCenter.
|
|
| Value | 1988980 |
| Description | OpsCenter Services stop when logging off Windows |
Legacy ID
347157
Article URL http://www.symantec.com/docs/TECH124639
Terms of use for this information are found in Legal Notices
Thank you.