Starting and stopping the TrueSight Operations Management components
Use the following sections to understand services and scripts used for starting and stopping the TrueSight Operations Management components.
Additionally, find out how these services or scripts are integrated in the operating system.
Starting and stopping the Presentation Server
Starting and stopping the Presentation Server on Windows
The following service can be used to start and stop the core server, Index server, and the database server from services.msc .
Service name | Display name |
---|---|
BMCTSPSSvc | BMC TrueSight Presentation Server |
You can also start and stop this service by running the following commands:
tssh server start
tssh server stop
For more information, see Presentation Server tssh commands.
Note
If you are working on a non-English Windows 2016 OS (for example, a Chinese Windows 2016 OS), restarting the OS does not result in automatic restart of the service. After the OS restart, you need to manually start the service.
Starting and stopping Presentation Server on Linux
The BMCTSPSSvc.service
service located at /etc/systemd/system starts and stops the Presentation Server on Linux.
IMPORTANT:
BMCTSPSSvc.service
in /etc/systemd is supported only from version 11.3.04.- Alternatively, if /etc/systemd is not supported on your machine, this service is created or can be located under /etc/init.d folder. Only on those machines, you can continue to use /etc/init.d to start or stop the service.
Open a command prompt and run the
ps -ef
command to find a process entry with PID=1. If the entry with PID=1 is for systemd, then the machine supports systemd.
Sample command output:UID PID PPID C STIME TTY TIME CMD root 1 0 0 Apr22 ? 01:42:33 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
If systemd has started the
BMCTSPSSvc.service
on your machine, running thesystemctl status BMCTSPSSvc.service
shows the /etc/systemd/system/BMCTSPSSvc.service.d/limits.conf file in the output. The output also lists the command to start the service and all processes started as part of the Presentation Server start.For the systemd machines, the user can delete the /etc/init.d/BMCTSPSSvc service and all the links for this service in the /etc/rc.d/rc3.d file.
TrueSight Presentation Server can be installed by a non-root user only. Therefore, the installer does not have sufficient permissions to automatically create the BMCTSPSSvc.service
service used for starting the Presentation Server.
You need to run the tssh service register <non-root User>
command to register the service which in turn creates the BMCTSPSSvc.service
service in the /etc/systemd/system directory.
You can start or stop the Presentation Server by running the following commands:
Task | Type of user | Command |
---|---|---|
Start the service | root |
|
non-root | Run one of the following:
Note: If prompted for a password, specify the root user password. | |
Stop the service | root |
|
non-root | Run one of the following:
Note: If prompted for a password, specify the root user password. | |
For more information about the tssh commands, see Presentation Server tssh commands . |
Information about limits.conf
The systemd limits.conf
file is located at /etc/systemd/system/BMCTSPSSvc.service.d/
directory on Linux. This is different from the /etc/security/limits.conf
file. All the limits related to the systemd subsystem are stored in the /etc/systemd/system/BMCTSPSSvc.service.d/limits.conf
file for BMCTSPSSvc.service.
The limits set in this file are used only when the processes defined in the systemd
are restarted after a system reboot.
Starting and stopping Infrastructure Management components
- Starting and stopping Infrastructure Management on Windows
- Starting and stopping Infrastructure Management on Linux
- Stopping and starting the Oracle database
- Starting and stopping the Integration Service on Windows
- Starting and stopping Integration Service on Linux
- Verifying that the Integration Service is running
- Starting and stopping the remote cell on Windows
- Starting and stopping the remote cell on Linux
- Notes regarding starting and stopping a remote cell
Starting and stopping Infrastructure Management on Windows
You can start and stop the Infrastructure Management server in the following ways:
Method | Description |
---|---|
services.msc | Start or stop the BMC TrueSight Infrastructure Management service. This service starts and stops all the Infrastructure Management server processes (for example, jserver process, rate process, httpd process, and so on. |
Start menu | Search for one the following names:
|
pw sys or the pw system command | Access the pw CLI and run one of the following commands:
|
Service name | Display name |
---|---|
ProNetServer | BMC TrueSight Infrastructure Management |
ProactiveNetApache | BMC TrueSight Infrastructure Management Apache |
SQLANYe_ProactiveNetDB | BMC TrueSight Infrastructure Management Database Engine |
mcxa | BMC TrueSight Infrastructure Management Event Adapters |
IBRSD | BMC TrueSight Infrastructure Management IBRSD |
mcell_<CellName> | BMC TrueSight Infrastructure Management Impact Manager <CellName> |
ProNetAgent | BMC TrueSight Infrastructure Management Integration Service |
SDIG | Service Desk Integration Gateway |
Starting and stopping Infrastructure Management on Linux
The BMCTrueSight.service
service located at /etc/systemd/system can be used to start and stop Infrastructure Management on Linux.
If you have installed Infrastructure Management as a root user, the installer automatically creates the BMCTrueSight.service
service in the /etc/systemd/system directory.
IMPORTANT:
BMCTrueSight.service
in /etc/systemd is supported only from version 11.3.04.- Alternatively, if /etc/systemd is not supported on your machine, this service is created or can be located under /etc/init.d folder. Only on those machines, you can continue to use /etc/init.d to start or stop the service.
Open a command prompt and run the
ps -ef
command to find a process entry with PID=1. If the entry with PID=1 is for systemd, then the machine supports systemd.
Sample command output:UID PID PPID C STIME TTY TIME CMD root 1 0 0 Apr22 ? 01:42:33 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
If systemd has started the
BMCTrueSight.service
on your machine, running thesystemctl status
BMCTrueSight.service
shows the /etc/systemd/system/BMCTrueSight.service.d/limits.conf file in the output. The output also lists the command to start the service and all processes started as part of the Infrastructure Management server start.For the systemd machines, the user can delete the /etc/init.d/BMCTrueSight.service service and all the links for this service in the /etc/rc.d/rc3.d file.
The BMCTrueSight.service
service automatically starts the Infrastructure Management server on machine restart.
Information about limits.conf
The systemd limits.conf file is located at /etc/systemd/system/BMCTrueSight.service.d/ directory on Linux. This is different from the /etc/security/limits.conf file. All the limits related to the systemd subsystem are stored in the
/etc/systemd/system/BMCTrueSight.service.d/limits.conf file for BMCTrueSight.service.
The limits set in this file are used only when the processes defined in the systemd are restarted after a system reboot.
If you installed Infrastructure Management as a non-root user, you need to enable the creation of the BMCTrueSight.service
service To do this, run the create_startup_script script located at pw/scripts with root user permissions.
You can also start or stop Infrastructure Management by running the pw sys
command. To do this, access the pw CLI and run the pw sys start
command or the pw sys stop
command.
Note for starting or stopping Infrastructure Management as a non-root user
To avoid problems related to starting or stopping Infrastructure Management by using the pw sys
command, ensure that you log on to a new session as a non-root user (without using the su
command).
After running pw/scripts/create_startup_script, If PATROL Agent is unable to connect to Integration service or Remote Cell, restart the server. ( When using 11.3.06 version on RHEL 9.x )
Stopping and starting the Oracle database
The following procedures explain how to stop and start an Oracle database in the following environments:
- Oracle RAC
- Single Oracle database instance
To stop an Oracle database server on Oracle RAC
- Log in to the database server as the Oracle DBA Admin user.
- From a command line, navigate to the path where the .oraenv script is located.
- Source the .oraenv script:
$ ../.oraenv
- Stop the database by entering the following command:
$ srvctl stop database -d RAC_ORACLE_SERVICE_NAME
- Confirm that all nodes are stopped by entering the following command:
$ srvctl status database -d RAC_ORACLE_SERVICE_NAME
The status of all nodes must be stopped .
To start an Oracle database server on Oracle RAC
- Log in to the database server as the Oracle DBA Admin user.
- From a command line, navigate to the path where the .oraenv script is located.
- Source the .oraenv script:
$ ../.oraenv
- Start the database by entering the following command:
$ srvctl start database -d RAC_ORACLE_SERVICE_NAME
- Confirm that all nodes are started by entering the following command:
$ srvctl status database -d RAC_ORACLE_SERVICE_NAME
The status of all nodes must be running .
To restart an Oracle RAC
- Open a SQLPlus prompt and run the following command to set Oracle_SID on RAC
$ . oraenv ORACLE_SID = [oracle] ? <
ORACLE_SERVICE_NAME>
- Run the following command to stop the RAC system
srvctl stop database -d <
RAC_ORACLE_SERVICE_NAME>
- Run the following command to see the status of the nodes. All the nodes must be in the "not running" status.
srvctl status database -d <
RAC_ORACLE_SERVICE_NAME>
- Run the following command to restart the RAC system
srvctl start database -d <
RAC_ORACLE_SERVICE_NAME>
- Ensure that all the nodes are up and running.
Run the following command, and when prompted specify the following values, to see the status of the nodes.
srvctl status database -d <
RAC_ORACLE_SERVICE_NAME>
Username:
sys
password: <
syspassword
>SID:
<RAC_ORACLE_SERVICE_NAME>
To restart a single Oracle database instance on Microsoft Windows
- From a command line, enter the following command:
set ORACLE_SID= Oracle_SID
- Enter
sqlplus sys/
sys_password assysdba
. - Enter
shutdown immediate
.
The database shuts down. Enter
startup
.
The database starts.Note
Ensure that you restart the TrueSight Infrastructure Management Server after you restart the Oracle database instance.
To restart a single Oracle database instance on a UNIX-based operating system
- Log in to the database server as the Oracle DBA Admin user.
- Ensure ORACLE_HOME and ORACLE_SID are correctly defined for the Infrastructure Management instance:
$ ORACLE_HOME=<oracle_installation_location>; export ORACLE_HOME
$ ORACLE_SID=<tsim_instance_name>; export ORACLE_SID
- Connect to the database instance:
$ sqlplus /
assysdba
- Shutdown the database instance:
SQL> shutdown immediate
Start the database instance:
SQL> startup
Note
Ensure that you restart the TrueSight Infrastructure Management Server after you restart the Oracle database instance.
Starting and stopping the Integration Service on Windows
The following service can be used to start and stop the Integration Service from services.msc .
Service name | Display name |
---|---|
ProNetAgent | BMC TrueSight Infrastructure Management Integration Service |
Starting and stopping Integration Service on Linux
The S81pronto.0.<instance number>
script located at /etc/rc2.d/ can be used to start and stop the Integration Service on Linux.
The installer creates the following scripts that start and stop the pronet_agent process corresponding to the Integration Service. These scripts are located at <IntegrationService-InstallationDirectory>/pw/pronto/bin.
Script name | Description |
---|---|
startremotepw
| Starts the pronet_agent process. |
stopremotepw
| Stops the pronet_agent process. |
startremotepw
script to start the Integration Service.The S81pronto.0.<instance number> script is created if you install the Integration Service as a root user.
As a non-root user:
You need to ask your administrator (or super user) to manually copy the S81pronto.<User_ID>.<Agent_Instances> file from <installationDirectory>/pw/pronto/bin to the /etc/rc.d/rc<Runlevel_Directory>.d folder.
- Open the /etc/rc.d/rc.local file, comment the pre-existing S81pronto file entries, and add a fresh entry of S81pronto.<User_ID>.<Agent_Instances> in the /etc/rc.d/rc.local file as shown in the following example:
#/etc/rc2.d/S81pronto.0.2
#/etc/rc2.d/S81pronto.0.2
#/etc/rc2.d/S81pronto.0.2
/etc/rc2.d/S81pronto.1004.1
Verifying that the Integration Service is running
To verify that the Integration Service is running:
(Windows) Check if the Integration Service(portNumber) service status is Started.
(Linux) Navigate to the installationDirectory/pw/pronto/bin/ directory and run the
pw agent status
command. Verify that the pronet_agent process is listed.If the pronet_agent process is not listed, run the
pw agent start
command. This command restarts all the Integration Service processes.
Starting and stopping the remote cell on Windows
The following service can be used to start and stop the remote cell from services.msc.
Method | Description |
---|---|
services.msc | Start or stop the BMC TrueSight Event Manager <HostName> service. The service name is mcell_<CellName>. |
net start and net stop command | From the command prompt, run the following commands to start of stop the service:
Note: When used without the |
mkill command | From the command prompt, run the following command:
Note: If you do not use the |
Starting and stopping the remote cell on Linux
The mc_<CellName>
script located at etc/init.d can be used to start and stop the remote cell process on Linux.
The installer creates the following soft links located at /etc/<RunLevel>.
Soft link | Description |
---|---|
S99mc_<CellName> | Runs the command to start the remote cell. |
K99mc_<CellName> | Runs the command to stop the remote cell. |
The following commands can help you start, stop, and view the status of the remote cell process:
Command | Description |
---|---|
mcell -n <CellName>
| Starts the remote cell process. It is possible to start a cell without specifying a cell name. If you start a cell without any options, the command attempts to start a cell with the same name as the host. You must set the installationDirectory/pw/server environment variable to point to the directory in which the cell is installed. The home directory also can be indicated using the option Note: You can change all the configurable cell parameters by making changes in the configuration file, mcell.conf. When you start the cell, the cell looks for the configuration file in the default location, installationDirectory\pw\server\etc\cellName\mcell.conf. Use the |
mkill -n <CellName>
| Stops the remote cell process. Note: If no cell name is provided, |
mcstat -n <CellName>
| Displays the status of the remote cell process. |
Notes regarding starting and stopping a remote cell
- By default, a cell runs as a daemon. You can override this behavior with the command line option,
-d
, by running themcell -n <CellName> -d
command. A cell can be installed or owned by any user. Only users with run permission on the mcell binary can start the cell. All users with run permission on the
mkill
ormcontrol
CLIs can stop the cell. However, if a user without root permissions attempts to start the process, the following issues must be considered:- External actions run as the user ID that started the process. Those actions are defined in the following locations:
- (Windows): installationDirectory\pw\server\etc\cellName\kb\bin
- (UNIX and Linux): $installationDirectory/pw/server/etc/cellName/kb/bin
- The user who starts the cell must be able to write to log and trace files in the directories specified through configuration parameters
SystemLogDirName
,SystemTmpDirName
, andSystemVarDirName
. Default values for these are thelog
andtmp
subdirectories of installationDirectory/pw/server.
- External actions run as the user ID that started the process. Those actions are defined in the following locations:
Forcefully starting the Presentation Server and Infrastructure Management services
Unless the computer hosting the Presentation Server (or Infrastructure Management) meets the following system requirements, you cannot start the Presentation Server (or Infrastructure Management).
- Total RAM (in MB): 32,000
- Available RAM (in MB): 25,000
- Total swap space / page file (in MB): 8,000
- Available swap space / page file (in MB): 8,000
- Available disk space (in MB): 2,000
You can verify whether you are unable to start the service because of the system requirements validation by looking at the following log files:
Product | Log file names | Path |
---|---|---|
TrueSight Presentation Server | ||
Windows | TrueSight_svc.log and TrueSight.log | <Presentation Server installation directory>\truesightpserver\logs |
Linux | tssh.log and TrueSight.log | <Presentation Server installation directory>/truesightpserver/logs |
TrueSight Infrastructure Management | ||
Windows | tsim_validation_config.log | pw\pronoto\logs |
Linux | pw/pronoto/logs |
To skip validation of the system requirements and forcefully start the service
Navigate to the following location based on the product service that you want to start forcefully:
Product Path TrueSight Presentation Server Windows <installationDirectory>\truesightpserver\conf\custom
Linux <installationDirectory>/truesightpserver/conf/custom TrueSight Infrastructure Management Windows <installationDirectory>\pw\custom\conf Linux <installationDirectory>/pw/custom/conf Proceed in one of the following ways, based on the product for which you want to enable starting the service forcefully:
Presentation Server: Edit the csr.conf file, add the following property, and save the file.
skipResourceCheck=true
Infrastructure Management: Edit the pronet.conf file, add the following property, and save the file.
skipResourceCheck=true
- Restart the product service.
These steps ensure that the service automatically starts even if you restart the Presentation Server or the Infrastructure Management host.
Alternatively, you can forcefully start the Presentation Server (or Infrastructure Management) service in the following way.
However, doing so does not ensure an automatic restart of the service in a scenario where the Presentation Server (or Infrastructure Management) host is restarted.
- Presentation Server: Run the
tssh server start force
command. - Infrastructure Management: Run the
pw sys start force
command
Starting and stopping the App Visibility server
To start and stop the App Visibility server services in Windows
To start and stop the App Visibility server services in Linux
Starting and stopping a synthetic TEA Agent as a process
To start the synthetic TEA Agent as a process
To stop the synthetic TEA Agent process
Starting and stopping the Real User Analyzer or Collector
To start the Real User Analyzer or Collector service
To stop the Real User Analyzer or Collector service
Starting and stopping the Real User Cloud Probe
To start or stop the Cloud Probe in Linux
To start or stop the Cloud Probe in Windows
Comments
Log in or register to comment.