Log Messages
To assist you in understanding the error and warning messages that may appear, this section provides tables for these two types of operational log messages.
 |
If, after starting the eMessage Connector, you find the logs directory is in a sub-directory of the current working directory and not where you expect (at $EMESSAGE_CONNECTOR_HOME/logs), it is likely that you have not specified the location for the log files in the logback.xml file. The default logback.xml file writes the log output file to a logs sub-directory (<property name="LOGS_DIR" value="logs" />). This sub-directory is created from current working directory from which the user launches the eMessage startup script. When creating your own logback.xml file, make sure that you change this property to place the logs in the desired location.
|
|
Logger Name
|
Message
|
Probable Cause
|
Action to Take
|
|---|---|---|---|
|
com.Thingworx.connectionserver.metrics.MetricsReporterManager
|
Metrics are enabled but no reporters are configured.
|
The metrics are enabled in the configuration file, but no metrics reporters were configured. No metrics are reported.
|
Enable the metrics reporter in the configuration file and restart the Connection Server.
|
|
com.Thingworx.connectionserver.metrics.MetricsReporterManager
|
Graphite metrics reporter enabled without service discovery but no endpoints are configured.
|
No explicit endpoint has been defined in the configuration file. No metrics are reported to Graphite.
|
Define the endpoint in the configuration file and restart the Connection Server
|
|
com.Thingworx.fabric.impl.AbstractManyPlatformWebSocketFabric
|
Platform still alive, so not removing: endpoint={}
|
The Connection Server received a notification that ThingWorx platform is no longer available, but the Connection Server is still connected to that Platform.
|
Verify whether ThingWorx Platform specified is still available.
|
|
Logger Name
|
Message
|
Probable Cause
|
Action to Take
|
|---|---|---|---|
|
com.Thingworx.connectionserver.ConnectionServer
|
Unable to start Connection Server
|
The Connection Server encountered an error that prevented it from starting up. The exception appears after the log message.
|
Resolve the issue mentioned in the exception and restart the Connection Server.
|
|
com.Thingworx.connectionserver.metrics.MetricsReporterManager
|
Unable to create stream for metrics console reporter, defaulting to standard-out: intended file={}
|
The file specified for the metrics console reporter could not be created. The exception appears after the log message. The Connection Server will continue functioning, but the metrics are written to standard out rather than the intended metrics file. The output file is specified in the configuration file at the following key: cx-server.metrics.reporters.console.outfile.
|
Fix the underlying issue specified in the exception, and restart the Connection Server. Possible causes are non-existent base directories and permissions issues.
|
|
com.Thingworx.connectionserver.metrics.MetricsReporterManager
|
Unable to create directory for metrics CSV reporter, disabling reporter: directory={}
|
The directory specified for the metrics CSV reporter could not be created. The exception appears after the log message. The Connection Server continues to operate, but the CSV metrics reporter is disabled. If the CSV metrics reporter is the only configured reporter, no metrics information is available.
|
Fix the underlying issue specified in the exception and restart the Connection Server. Possible causes are base directories not existing and permissions issues.
|
|
com.Thingworx.fabric.impl.AbstractManyPlatformWebSocketFabric
|
Failure while connecting to platform: endpoint={}
|
The attempt to connect to the ThingWorx Platform failed. The exception appears after the log message. The Connection Server will not start.
|
Resolve the issue mentioned in the exception and restart the Connection Server. Possible causes are:
• The wrong Platform endpoint (host/port) is specified in the configuration.
• The Platform is not accessible over the network from the Connection Server.
• The Platform is not running
.
|