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

Installing

UpgradingTo start and stop the Publishing Server

Starting and stopping the Remedy Single Sign-On server

Starting and stopping the Remedy Single Sign-On server on Windows

You can start or stop the service on Windows by navigating to services.msc or by running commands on the command line.

To start or stop the service from services.msc

  1. Navigate to the computer where Remedy Single Sign-On is installed.
  2. Click Start > Run > services.msc.
  3. Start or stop the BMC Remedy Single Sign-On Server service.

To start or stop the process from the command line

  1. Navigate to the <Remedy SSO Installation Directory>\rsso\bin directory.

  2. On the command line, run one of the following commands:

    • To start the process: rsso.bat server start
    • To stop the process: rsso.bat server stop

    Note

    Running the start command results in first stopping the Remedy Single Sign-On service and then starting it.

Starting and stopping the Remedy Single Sign-On server on Linux

  1. Navigate to the <Remedy SSO Installation Directory>\rsso\bin directory.

  2. On the command line, run one of the following commands as a non-root user:

    • To start the service: ./rsso server start
    • To stop the service: ./rsso server stop

    Note

    Running the start command results in first stopping the Remedy Single Sign-On service and then starting it.


Verifying the status of Remedy SSO

  1. Navigate to the <Remedy SSO Installation Directory>\rsso\bin directory.
  2. On the command line, run one of the following commands:
    • (Windows): rsso.bat server status

    • (Linux): ./rsso server status

      Note

      On a Linux server, you need to run the command as a non-root user.

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 .

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 script located at /etc/init.d starts and stops the Presentation Server on Linux.

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 script 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 performs the following actions:

  • Creates the BMCTSPSSvc script in the /etc/init.d directory.

  • Creates the following soft links located at /etc/<RunLevel>.

You can start or stop the Presentation Server by running the following commands:

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:

The following table lists the services available for the various Infrastructure Management components. These services can be started or stopped from services.msc.

Starting and stopping Infrastructure Management on Linux

The BMCTrueSight script located at /etc/init.d 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 script in the /etc/init.d directory and also creates the following soft links located at /etc/<RunLevel>:

The BMCTrueSight script automatically starts the Infrastructure Management server on machine restart.

If you installed Infrastructure Management as a non-root user, you need to enable the creation of the BMCTrueSight script. To do this, run the create_startup_script script located at pw/scripts with root user permissions.

Applicable if you applied the 11.3.02 and 11.3.03 service packs in HA mode

After applying the 11.3.03 service pack as a non-root user, perform the following additional steps on the primary and secondary servers. These steps are required to enable the BMCTrueSight script to start the Infrastructure Management service. 

  1. Log on as a root user.
  2. Go to /etc/init.d/.
  3. Edit the BMCTrueSight file and replace the contents of the file with the following line and save the file:
    /usr/pw/pronto/bin/pwstartup with /usr/pw/pronto/bin/pwstartupWrapperHA

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 .

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.

When you restart the computer hosting an Integration Service, the S81pronto.0.<instance number> script runs the startremotepw script to start the Integration Service.

Note: 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 adminstrator (or super user) to manually copy the s81pronto.xxxx file from <installationDirectory>/pw/pronto/bin to all the etc/rc.d/rc<runLevel>/.d files.

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.

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

The following commands can help you start, stop, and view 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 SystemLogDirName, SystemTmpDirName, 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). 

Excerpt named installupgradereq was not found in document xwiki:IT-Operations-Management.Operations-Management.BMC-TrueSight-Operations-Management.TSOMD113.Planning.Planning-the-Presentation-Server-deployment.System-requirements-for-Presentation-Server.WebHome.

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

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:

  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:

Component

Start command

Stop command

App Visibility portal

service adop_portal start
service adop_portal stop

App Visibility collector

service adop_collector start
service adop_collector stop

App Visibility database

service av_pgsql start

service av_pgsql stop

App Visibility proxy

service adop_apm_proxy start

service adop_apm_proxy stop

App Visibility storage engine

service apm_elasticsearch start

service 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


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*