Resolving problem: Starting or running the daemon

Consult the IBM® WebSphere® MQ Telemetry daemon for devices console log, turn on tracing, or use the symptom table in this topic to troubleshoot problems with the daemon.

1. Check the console log.

   If the daemon is running in the foreground, the console messages are written to the terminal window. If the daemon has been started in the background, the console is where you have redirected stdout to.

2. Restart the daemon.

   Changes to the configuration file are not activated until the daemon is restarted.

3. Consult Table 1:

   Table 1. Symptom table

   Problem	Suggested solution
   The following message is displayed when you start the daemon on Windows: The system cannot execute the specified program or The application has failed to start because its side-by-side configuration is incorrect.	Install Microsoft Visual C++ 2008 Redistributable Package.
   Two or more daemons or MQTT-capable servers are inter-connected by a bridge or bridges, and the processor is showing excessive load.	There is possibly a message loop, with one or more messages being repeatedly passed from one server to another. Examine the topic parameters in the configuration files. Use more specific topics where possible. Broad wildcard characters in both directions are the most common cause of connection loops.
   The bridge is unable to connect to a remote MQTT-capable server that other MQTT clients can connect to.	The remote server might be incompatible with attempts to determine if the remote server is also WebSphere MQ Telemetry daemon for devices. Try setting try_private to off to disable special processing to eliminate message loops.
   This message is printed when a bridge is configured: Warning: Connect was not first packet on socket 1888, got CONNACK.	You have probably configured a bridge to loop back to the local daemon. Loopback is not supported.