TIBCO LogLogic LMI "Warning: One or more components of the TIBCO LogLogic appliance have become disabled due to internal errors."
book
Article ID: KB0077900
calendar_today
Updated On:
Products
Versions
TIBCO LogLogic Enterprise Virtual Appliance
all versions
Description
You may see the following message when logging into the LogLogic LMI GUI:
This warning occurs as a result of one or more specific LMI-related engines that are in disabled status. Not every LMI engine will trigger this warning though but this warning is specifically triggered by LMI engines. In other words, standard Linux processes will not trigger this warning. Only the engines in the "BACKEND" group will trigger this warning. The engine definition in /loglogic/conf/node_config.xml dictates whether an engine is in the BACKEND group or another group.
If you want to see which specific engine(s) triggered this you can login as toor using ssh and execute the watchqueue command. The default first page of information shows each engine status. You should see one or more that are in disabled status. The command syntax is simply: $ watchqueue
Here is the list of engines that are part of the BACKEND group. The appliance model dictates which engines appear in your watchqueue output so only a subset of these engines will be running on a given appliance. engine_collector engine_filecollector engine_highpri_reader engine_http_collector engine_led engine_llaggregation engine_llcorrelation engine_lldaemon engine_lldatanode engine_llquerynode engine_llzookeeper engine_llzookeeper_sync engine_llwebapp engine_lx_parser engine_lx_scheduler engine_rcollector engine_rsender engine_rtserver engine_st_reporter engine_stunnel engine_tcp_scheduler engine_tcpcollector engine_tcpforwarder engine_trapcollector engine_uldpcollector ll_opsec_manager
Environment
Physical and virtual appliances
Resolution
Typically if an engine is in disabled status it is for good reason and was put into that status by mtask itself as a safety mechanism. You can try to remove this GUI warning by starting the engine(s) that are disabled. Do not be surprised though if the engine immediately (within a couple seconds) goes back to disabled status. This indicates more troubleshooting and analysis is required to determine what the problem is and resolve it so the engine can remain healthy. If the engine reverts back to disabled status again the best practice is to not attempt manually starting it again otherwise engine escalations can be triggered which can lead to other engine restarts and possibly hardware reboots.
$ mtask -s <engine_name> start
For example: $ mtask -s engine_filecollector start
If the engine(s) will not stay in running status then, as the message suggests, contact TIBCO LogLogic LMI Technical Support so we can assist with getting the appliance back to a healthy state.
Issue/Introduction
This article explains the cause for this warning and methods for resolving it.