Troubleshooting status issues of BMC Discovery services
If you encounter issues with the status of BMC Discovery services, use the steps described in this section to either resolve the problem or create a BMC Support case.
Issue symptoms
Some BMC Discovery services do not display the Running status though they are running.
Scope
This issue can affect all versions of BMC Discovery.
Resolution
Perform the steps in the following two stages to troubleshoot an issue where BMC Discovery services do not correctly display their Running status.
Stage 1–Identify the operating system and appliance version
To identify the operating system (OS) and appliance version, see Which-OS-and-version-is-my-appliance-using.
Stage 2–Confirm the status of BMC Discovery services
After you identify the version, perform the following steps to check the services:
- Access the SSH session of the BMC Discovery appliance. To do so, use the SSH client PuTTY. For more information, see https://www.putty.org/
- Log in as the tideway user.
Run the following commands to confirm that all the BMC Discovery services are in the Running state, and no service is in the Stopped state:
CentOS 6 or RHEL 6:
sudo /sbin/service tideway status
sudo /sbin/service cluster status
sudo /sbin/service omniNames status
sudo /sbin/service appliance statusCentOS 7:
tw_service_control --status
sudo systemctl status cluster
sudo systemctl status omniNames
sudo systemctl status appliance
Confirm that the httpd service is in a running state by using the following command:
sudo /sbin/service httpd statusIf the service is stopped, then run the following command to start the service:
sudo /sbin/service httpd start- Occasionally, it may happen that not all services are up, even though the running status shows that the services are up. In such cases, run the start command to start the services.
- To restart the application services, first execute the following stop commands:
CentOS 6 or RHEL 6:
sudo /sbin/service tideway stop
sudo /sbin/service cluster stop
sudo /sbin/service omniNames stop
sudo /sbin/service appliance stopCentOS 7:
tw_service_control --stop
sudo systemctl stop cluster
sudo systemctl stop omniNames
sudo systemctl stop applianceIn rare cases, a process may be stuck and not end cleanly. To check for this, run the command:
ps -ef | grep pythonIf some processes are stuck, kill the python processes with the command:
kill -9 <pid>There are two privileged processes owned by root, for example:
root 7490 1 0 Sep21 ? 00:00:00 python /usr/tideway/python/privileged/main.pyc --daemon start
root 7495 7490 0 Sep21 ? 01:02:43 python /usr/tideway/python/privileged/main.pyc --daemon startIt is not necessary to kill these privileged processes. However, killing these processes will cause no harm.
- Run the following commands to restart the services:
CentOS 6 or RHEL 6:
sudo /sbin/service appliance start
sudo /sbin/service omniNames start
sudo /sbin/service cluster start
sudo /sbin/service tideway startCentOS 7:
sudo systemctl start appliance
sudo systemctl start omniNames
sudo systemctl start cluster
tw_service_control --start