How to restart an application engine in TIBCO LogLogic LMI
Article ID: KB0077509
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Log Management Intelligence | all versions |
Description
The processes that run in the background that constitute the LogLogic LMI application are known as engines. These sometimes must be manually restarted to resolve an issue, as part of troubleshooting or to make a configuration change take effect. To restart any engine involves using the same command and same syntax.
Example:
$ mtask -s engine_http_collector restart
The engine name must be exactly correct. You can obtain the full list of engine names by executing the watchqueue command:
$ watchqueue
Note the engine name to restart (pay special attention to where underscore characters appear in the name) then exit that command using the 'q' key and return to executing the mtask command listed above. if you are performing this operation on an HA cluster we recommend contacting TIBCO LogLogic Support so that we can assist to ensure a failover event does not occur.
1. SSH to the appliance and login as ”toor”
2. Execute the following command:
$ mtask -s <full engine name> restartExample:
$ mtask -s engine_http_collector restart
The engine name must be exactly correct. You can obtain the full list of engine names by executing the watchqueue command:
$ watchqueue
Note the engine name to restart (pay special attention to where underscore characters appear in the name) then exit that command using the 'q' key and return to executing the mtask command listed above. if you are performing this operation on an HA cluster we recommend contacting TIBCO LogLogic Support so that we can assist to ensure a failover event does not occur.
Issue/Introduction
This article explains how to restart an application engine in LogLogic LMI.
Feedback
Yes
No
Powered by
