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.

Related topics

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 nameDisplay name
BMCTSPSSvcBMC 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 the systemctl 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:

TaskType of userCommand
Start the serviceroot

systemctl start BMCTSPSSvc.service

non-root

Run one of the following:

  • tssh server start
  • systemctl start BMCTSPSSvc.service

Note: If prompted for a password, specify the root user password.

Stop the serviceroot

systemctl stop BMCTSPSSvc.service

non-root

Run one of the following:

  • tssh server stop
  • systemctl start BMCTSPSSvc.service

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.

For troubleshooting startup issues in a high-availability deployment of the Presentation Server, see Troubleshooting a high-availability deployment.

Starting and stopping Infrastructure Management components

Starting and stopping Infrastructure Management on Windows

You can start and stop the Infrastructure Management server in the following ways:

MethodDescription
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 menuSearch for one the following names:
  • Start BMC TrueSight Infrastructure Management Server
  • Stop BMC TrueSight Infrastructure Management Server
pw sys or the pw system command

Access the pw CLI and run one of the following commands:

  • pw sys start  or pw system start command
  • pw sys stop or pw system stop command
The following table lists the services available for the various Infrastructure Management components. These services can be started or stopped from services.msc.
Service nameDisplay name
ProNetServer

BMC TrueSight Infrastructure Management

ProactiveNetApacheBMC TrueSight Infrastructure Management Apache
SQLANYe_ProactiveNetDBBMC TrueSight Infrastructure Management Database Engine
mcxaBMC TrueSight Infrastructure Management Event Adapters
IBRSDBMC TrueSight Infrastructure Management IBRSD
mcell_<CellName>BMC TrueSight Infrastructure Management Impact Manager <CellName>
ProNetAgentBMC TrueSight Infrastructure Management Integration Service
SDIGService 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 the systemctl 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).

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

  1. Log in to the database server as the Oracle DBA Admin user.
  2. From a command line, navigate to the path where the .oraenv script is located.
  3. Source the .oraenv script:
    ../.oraenv
  4. Stop the database by entering the following command:
    $ srvctl stop database -d RAC_ORACLE_SERVICE_NAME
  5. 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

  1. Log in to the database server as the Oracle DBA Admin user.
  2. From a command line, navigate to the path where the .oraenv script is located.
  3. Source the .oraenv script:
    ../.oraenv
  4. Start the database by entering the following command:
    $ srvctl start database -d RAC_ORACLE_SERVICE_NAME
  5. 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

  1. Open a SQLPlus prompt and run the following command to set Oracle_SID on RAC
    $ . oraenv ORACLE_SID = [oracle] ? <ORACLE_SERVICE_NAME>
  2. Run the following command to stop the RAC system
    srvctl stop database -d <RAC_ORACLE_SERVICE_NAME> 
  3. 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> 
  4. Run the following command to restart the RAC system
    srvctl start database -d <RAC_ORACLE_SERVICE_NAME>
  5. Ensure that all the nodes are up and running.
  6. 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

  1. From a command line, enter the following command:
    set ORACLE_SID= Oracle_SID
  2. Enter sqlplus sys/ sys_password as sysdba.
  3. Enter shutdown immediate.
    The database shuts down.
  4. 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

  1. Log in to the database server as the Oracle DBA Admin user.
  2. 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 
  3. Connect to the database instance:
    $ sqlplus / as sysdba
  4. Shutdown the database instance:
    SQL> shutdown immediate
  5. 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 nameDisplay name
ProNetAgentBMC 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 nameDescription
startremotepw Starts the pronet_agent process.
stopremotepw Stops the pronet_agent process.
When you restart the computer hosting an Integration Service, the S81pronto.0.<instance number> script runs the 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.

MethodDescription
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:

  • net start mcell_<CellName>
  • net stop mcell_<CellName>

Note: When used without the -d option, mcell contacts the Service Control Manager to start itself as a service. It uses mcell_%N as a service name. %N is the cell name as specified by the -n option. Without the -n option, the default cell name is the host name.

mkill command

From the command prompt, run the following command:

mkill -n <CellName>

Note: If you do not use the -n option when stopping a cell, the default cell, named hostName, is stopped.

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 linkDescription
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:

CommandDescription
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 -l followed by the path to the home directory, instead of defining it in the environment. For more information, see mcell command.

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 -c option with the mcell command to have the cell look for the configuration file in a specified location.

mkill -n <CellName>

Stops the remote cell process.

Note: If no cell name is provided, mkill attempts to stop a local cell whose name is the same as the local host name. For more information, see mkill command.

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 the mcell -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 or mcontrol 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
      Actions are defined in .mrl files located in the kb/bin directory and listed in .load in that directory. The action programs or scripts can be located in the kb/bin/A or kb/bin/Arch directory. They can also be located anywhere else on the system. 
    • The user who starts the cell must be able to write to log and trace files in the directories specified through configuration parameters SystemLogDirNameSystemTmpDirName, and SystemVarDirName. Default values for these are the log and tmp subdirectories of installationDirectory/pw/server.

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:

ProductLog file namesPath
TrueSight Presentation Server
Windows

TrueSight_svc.log and TrueSight.log

<Presentation Server installation directory>\truesightpserver\logs
Linuxtssh.log and TrueSight.log<Presentation Server installation directory>/truesightpserver/logs
TrueSight Infrastructure Management
Windowstsim_validation_config.log pw\pronoto\logs
Linuxpw/pronoto/logs
For experimentation purposes, you can skip validation of the system requirements and forcefully start the service.

To skip validation of the system requirements and forcefully start the service

  1. Navigate to the following location based on the product service that you want to start forcefully:

    ProductPath
    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

  2. 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

  3. 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

On the computers where the App Visibility server components are installed, use the Windows services manager (services.msc) to stop and start the App Visibility server components.

The following services are listed for their respective installed components:

  • BMC App Visibility Collector
  • BMC App Visibility Portal
  • BMC App Visibility PostgreSQL
  • BMC App Visibility Proxy
  • BMC App Visibility Elasticsearch

Note

If you need to restart the PostgreSQL service, use the following order:

  1. Stop the BMC App Visibility PostgreSQL service after you stop the portal and collector services.
  2. Start the BMC App Visibility PostgreSQL service before you start the portal and collector services.

To start and stop the App Visibility server services in Linux

On the computers where the App Visibility server components are installed, run the required command to start or stop a service:

ComponentStart commandStop command
App Visibility portalservice adop_portal startservice adop_portal stop
App Visibility collector

service adop_collector start

service adop_collector stop
App Visibility databaseservice av_pgsql startservice av_pgsql stop
App Visibility proxy

service adop_apm_proxy start

service adop_apm_proxy stop
App Visibility storage engineservice apm_elasticsearch startservice apm_elasticsearch stop

Starting and stopping a synthetic TEA Agent as a process

To start the synthetic TEA Agent as a process

  1. On the TEA Agent computer, navigate to the installationDirectory\TEAAgent directory.
    The default installation directory is one of the following, according to your system:
    • C:\Program Files (x86)\BMC Software\BMCTEAAgent

    • C:\Program Files\BMC Software\BMCTEAAgent

  2. Right-click the start_agent.bat file, and select Run as administrator.

A command prompt opens and displays the status of the TEA Agent.

To stop the synthetic TEA Agent process

To stop the TEA Agent process, press Ctrl+C to terminate the batch file in the command window.

Starting and stopping the Real User Analyzer or Collector

To start the Real User Analyzer or Collector service

  1. Log in to the virtual machine with the Real User Analyzer or Collector installation as root.
  2. Run the required command in a command prompt:
    • service euem_analyzer start
    • service euem_collector start

If the Real User Analyzer or Collector component service is working after the start command, you will see the Real User Analyzer or Collector Console in a supported browser.

To stop the Real User Analyzer or Collector service

  1. Log in to the virtual machine with the Real User Analyzer or Collector installation as root.
  2. Run the required command in a command prompt:
    • service euem_analyzer stop
    • service euem_collector stop

Warning

If you use a kill command to stop the Real User Analyzer or Collector component, the component service continues to operate. The component and the database stops working but the operating system maintains the component as a continuing service.

Starting and stopping the Real User Cloud Probe

To start or stop the Cloud Probe in Linux

  1. Log in to the virtual machine with the Real User Cloud Probe installation as root.

  2. Run the required command in a command prompt:

    • service cloud-probe start

    • service cloud-probe stop

To start or stop the Cloud Probe in Windows

  1. Run the services.msc command.
  2. In the list of services, right-click on the BMC Real User Cloud Probe service and use the following options accordingly:
    • Start
    • Stop
    • Restart


Was this page helpful? Yes No Submitting... Thank you

Comments