Access log files

Node logs

Using the default configuration, nodes log their activity in various log files:

  • node_directory/var/log/node.log
  • node_directory/var/log/node-error.log
  • node_directory/var/log/node-lifecycle.log
  • node_directory/var/log/audit.log
  • node_directory/var/log/integration.log
  • node_directory/var/log/integration-error.log
  • node_directory/var/log/ui.log
  • node_directory/var/log/migration-error.log

The location, content, name of these log files (except migration-error.log) can be configured by editing the conf/log4j.properties file. For more information about how to configure the logging system, see Log configuration.

node.log

This file is located by default in the var/log directory and contains all logs messages (INFO, WARN, ERROR) produced by the node.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 99 files.

When the node.log file exceeds 10 MB, it is renamed into  node.logs.1 (if node.log.1 is already present, it is renamed into  node.log.2, etc.).

With this configuration, a node may require up to 1 GB of disk space to store all node.log files.


Here is an example of the content of this file:

var/log/node.log
2016-11-15 13:58:48,493 [FelixStartLevel] INFO platform - ###############################################################################
2016-11-15 13:58:48,494 [FelixStartLevel] INFO platform - #                                                                             #
2016-11-15 13:58:48,494 [FelixStartLevel] INFO platform - #   JVM INFORMATION                                                           #
2016-11-15 13:58:48,494 [FelixStartLevel] INFO platform - #                                                                             #
2016-11-15 13:58:48,494 [FelixStartLevel] INFO platform - ###############################################################################
2016-11-15 13:58:48,495 [FelixStartLevel] INFO platform - Java home: T:\opt\jdk-1.8.0_112\jre
2016-11-15 13:58:48,495 [FelixStartLevel] INFO platform - Java version: 1.8.0_112
2016-11-15 13:58:48,495 [FelixStartLevel] INFO platform - Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
2016-11-15 13:58:48,496 [FelixStartLevel] INFO platform - Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
...
2016-11-15 13:58:55,675 [Domain-calcium-10] INFO calcium.metamodelInitializer - Metamodel 00000019-0000-0000 initialized at TT=1551069070632157185
2016-11-15 13:58:55,757 [Domain-calcium-35] INFO calcium.checkpointManager - Reading workflow elements checkpoint with transaction time 1551068669667180545
2016-11-15 13:58:55,850 [Domain-calcium-35] INFO calcium.asynchronousWorkflowEngine - Asynchronous workflow engine started in 92 ms
2016-11-15 13:58:55,871 [Domain-calcium-33] INFO calcium.workflowTransactionProcessor - All synchronous interceptors deployed in 18 ms
2016-11-15 13:58:55,876 [Domain-calcium-10] INFO calcium.absorptionManagerService - Absorption manager is ready
2016-11-15 13:58:55,894 [Domain-photon-application-9] INFO photon-application.applicationReplicaProvider - Task <default> not scheduled (No more execution)
2016-11-15 13:58:55,895 [Domain-calcium-33] INFO calcium.clusterPrimaryStatusTask - Task <default> not scheduled (No more execution)
2016-11-15 13:58:55,897 [Domain-photon-authentication-20] INFO photon-authentication.authenticationConfiguration - SSO mode is off
2016-11-15 13:58:56,085 [Domain-carbon-semantic-17] INFO carbon-semantic.indicatorInitializer - Creating default indicators for System
2016-11-15 13:58:56,156 [Domain-cobalt-security-16] INFO cobalt-security.userAccountDeactivationTask - Task <default> not scheduled (No more execution)
2016-11-15 13:58:57,123 [Domain-carbon-semantic-17] INFO carbon-semantic.indicatorInitializer - Created default indicators for System in 1039 ms
2016-11-15 13:58:57,124 [Domain-carbon-semantic-17] INFO carbon-semantic.indicatorInitializer - Creating default indicators for Semantic
2016-11-15 13:58:57,737 [Domain-carbon-semantic-17] INFO carbon-semantic.indicatorInitializer - Created default indicators for Semantic in 613 ms
2016-11-15 13:58:57,737 [Domain-carbon-semantic-17] INFO carbon-semantic.indicatorInitializer - Creating default indicators for Security
2016-11-15 13:58:57,746 [Domain-carbon-semantic-17] INFO carbon-semantic.indicatorInitializer - Created default indicators for Security in 9 ms
2016-11-15 13:58:57,747 [Domain-actinium-8] INFO carbon-semantic.indicatorInitializer - Creating default indicators for Activity
2016-11-15 13:58:57,786 [Domain-actinium-8] INFO carbon-semantic.indicatorInitializer - Created default indicators for Activity in 39 ms
2016-11-15 13:58:59,156 [PlatformStartMonitor] INFO platform.availabilityMonitor - ###############################################################################
2016-11-15 13:58:59,157 [PlatformStartMonitor] INFO platform.availabilityMonitor - #                                                                             #
2016-11-15 13:58:59,157 [PlatformStartMonitor] INFO platform.availabilityMonitor - #   PLATFORM STARTED                                                          #
2016-11-15 13:58:59,157 [PlatformStartMonitor] INFO platform.availabilityMonitor - #                                                                             #
2016-11-15 13:58:59,157 [PlatformStartMonitor] INFO platform.availabilityMonitor - ###############################################################################
2016-11-15 13:58:59,157 [PlatformStartMonitor] INFO platform.availabilityMonitor - Platform started in 19.494 sec
...

node-error.log

This file is located by default in the var/log directory and contains only warning and error messages produced by the node.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 99 files. With this configuration, a node may require up to 1 GB of disk space to store all node-error.log files.

For more information, read What is the list of error logs ?

Here is an example of the content of this file:

var/log/node-error.log
2014-05-05 12:46:44,303 [Camel (Instances.Steps) thread #1 - timer://foo] ERROR org.apache.camel.processor.DefaultErrorHandler - 
Failed delivery for (MessageId: 1399286801643-0-3 on ExchangeId: ID-1399286801643-0-5). Exhausted after delivery attempt: 1 caught: 
com.systar.calcium.absorption.AbsorptionException: Not compatible operation detected...Stacktrace

---------------------------------------------------------------------------------------------------------------------------------------
com.systar.calcium.absorption.AbsorptionException: Not compatible operation detected: The auto-create entity specified in the 
resolveByKey operation does not correspond to a parent in the entity hierarchy of the resolved instance
	at com.systar.calcium.impl.absorption.preprocessor.RequestResolver.resolveAndQueueKey(RequestResolver.java:243)
	at com.systar.calcium.impl.absorption.preprocessor.RequestResolver.resolveInstanceByKey(RequestResolver.java:629)...
 

node-lifecycle.log

This file is located by default in the var/log directory and contains all logs messages (INFOWARNERROR) that are related to the node lifecycle.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 1 file.

When the node-lifecycle.log file exceeds 10 MB, it is renamed into node-lifecycle.logs.1.

With this configuration, the node may require up to 20 MB of disk space to store all node-lifecycle.log files.

Here is an example of the content of this file:

var/log/node-lifecycle.log
2014-05-15 04:00:34,988 [FelixStartLevel] INFO platform - ###############################################################################
2014-05-15 04:00:34,995 [FelixStartLevel] INFO platform - #                                                                             #
2014-05-15 04:00:34,995 [FelixStartLevel] INFO platform - #   JVM INFORMATION                                                           #
2014-05-15 04:00:34,995 [FelixStartLevel] INFO platform - #                                                                             #
2014-05-15 04:00:34,995 [FelixStartLevel] INFO platform - ###############################################################################
2014-05-15 04:00:34,996 [FelixStartLevel] INFO platform - Java home: /usr/java/jdk1.8.0_XX/jre
2014-05-15 04:00:34,996 [FelixStartLevel] INFO platform - Java version: 1.8.0_XX
2014-05-15 04:00:34,996 [FelixStartLevel] INFO platform - Java(TM) SE Runtime Environment (build 1.X.0_XX-bXX)
2014-05-15 04:00:34,996 [FelixStartLevel] INFO platform - Java HotSpot(TM) 64-Bit Server VM (build XX.XX-bXX, mixed mode)
...
2014-05-15 04:00:35,003 [FelixStartLevel] INFO platform - 
2014-05-15 04:00:35,003 [FelixStartLevel] INFO platform - ###############################################################################
2014-05-15 04:00:35,003 [FelixStartLevel] INFO platform - #                                                                             #
2014-05-15 04:00:35,003 [FelixStartLevel] INFO platform - #   STARTING PLATFORM                                                         #
2014-05-15 04:00:35,003 [FelixStartLevel] INFO platform - #                                                                             #
2014-05-15 04:00:35,003 [FelixStartLevel] INFO platform - ###############################################################################
2014-05-15 04:00:35,004 [FelixStartLevel] INFO platform - Starting Gluon platform in directory...
2014-05-15 04:00:35,019 [FelixStartLevel] INFO platform - Create RMI registry on port 1099
2014-05-15 04:00:39,810 [Domain-platform-1] INFO platform.termsOfUseValidator - The terms of use of domain 'platform' are verified
2014-05-15 04:00:39,893 [Domain-platform-1] INFO platform.extender - Starting domain 'aluminium-camel-editor' in bundle 'com.systar.aluminium.camel.editor [57]'
2014-05-15 04:00:41,547 [Domain-platform-1] INFO platform.extender - Starting domain 'aluminium-camel-sandbox' in bundle 'com.systar.aluminium.camel.sandbox [60]'
2014-05-15 04:00:41,570 [Domain-platform-1] INFO platform.extender - Starting domain 'argon-migration' in bundle 'com.systar.argon.migration [62]'
...

integration.log

This file is located by default in the var/log directory and contains all logs messages (INFOWARNERROR) produced by the data integration.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 99 files.

When the integration.log file exceeds 10 MB, it is renamed into integration.logs.1 (if  integration.log.1 is already present, it is renamed into  integration.log.2, etc.).

With this configuration, a node may require up to 1 GB of disk space to store all  integration.log files.

Here is an example of the content of this file:

var/log/integration.log
2016-11-15 12:09:38,216 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO com.systar.aluminium.engine.impl.context.CamelContextAdapter$AdaptedCamelContext - Apache Camel  (CamelContext: space.log) is starting
2016-11-15 12:09:38,216 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO org.apache.camel.management.ManagedManagementStrategy - JMX is enabled
2016-11-15 12:09:38,233 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO org.apache.camel.impl.DefaultRuntimeEndpointRegistry - Runtime endpoint registry is in extended mode gathering usage statistics of all incoming and outgoing endpoints (cache limit: 1000)
2016-11-15 12:09:38,247 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO com.systar.aluminium.engine.impl.context.CamelContextAdapter$AdaptedCamelContext - AllowUseOriginalMessage is enabled. If access to the original message is not needed, then its recommended to turn this option off as it may improve performance.
2016-11-15 12:09:38,247 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO com.systar.aluminium.engine.impl.context.CamelContextAdapter$AdaptedCamelContext - StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html
2016-11-15 12:09:38,261 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO com.systar.aluminium.engine.impl.context.CamelContextAdapter$AdaptedCamelContext - Route: route1 started and consuming from: Endpoint[timer://foo?repeatCount=1]
2016-11-15 12:09:38,261 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO com.systar.aluminium.engine.impl.context.CamelContextAdapter$AdaptedCamelContext - Total 1 routes, of which 1 is started.
2016-11-15 12:09:38,262 [Domain-aluminium-engine-62-contextRuntimeFactory.00000000-f024-0000-1586-7aabd4d00801] INFO com.systar.aluminium.engine.impl.context.CamelContextAdapter$AdaptedCamelContext - Apache Camel  (CamelContext: space.log) started in 0.045 seconds
2016-11-15 12:09:39,261 [Camel (space.log) thread #4 - timer://foo] INFO route1 - I'm a log with level INFO
2016-11-15 12:09:39,262 [Camel (space.log) thread #4 - timer://foo] WARN route1 - I'm a log with level WARN
2016-11-15 12:09:39,263 [Camel (space.log) thread #4 - timer://foo] ERROR route1 - I'm a log with level ERROR

integration-error.log

This file is located by default in the var/log directory and contains only warning and error messages produced by the data integration.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 99 files. With this configuration, a node may require up to 1 GB of disk space to store all integration-error.log files.

Here is an example of the content of this file:

var/log/integration-error.log
2016-11-15 12:09:39,262 [Camel (space.log) thread #4 - timer://foo] WARN route1 - I'm a log with level WARN
2016-11-15 12:09:39,263 [Camel (space.log) thread #4 - timer://foo] ERROR route1 - I'm a log with level ERROR

audit.log

This file is located by default in the var/log directory and contains all audit events produced by the node.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 99 files. With this configuration, a node may require up to 1 GB of disk space to store all audit.log files.

For more information, see Audit Events.


Here is an example of the content of this file:

var/log/audit.log
2013-08-27 15:19:51,153 DEBUG - hharris:User logs in.
2013-08-27 15:20:24,862 INFO  - hharris:Application imported. {sessionToken=e201ccda-15c0-4486-bfd0-2c0933c56e00}.
2013-08-27 17:19:17,272 INFO  - hharris:Connector created. {UUID=00000001-f014-0000-140c-05b820100001}.
2013-08-27 17:21:59,731 INFO  - hharris:Route created. {UUID=00000001-f014-0000-140c-05dfca500801}.
2013-08-27 15:22:04,153 DEBUG - mtaylor:User logs in.
2013-08-27 17:22:08,898 INFO  - hharris:Route updated. {UUID=00000001-f014-0000-140c-05dfca500801}.
2013-08-27 17:22:17,482 INFO  - hharris:Route status changed. {UUID=00000001-f014-0000-140c-05dfca500801, new status=START}.
2013-08-27 17:24:25,436 INFO  - hharris:Data injected to route. {UUID=00000001-f014-0000-140c-05dfca500801, resource=00000001-f014-0000-140c-060135b00001}.
2013-08-27 17:24:35,345 INFO  - hharris:Route status changed. {UUID=00000001-f014-0000-140c-05dfca500801, new status=STOP}.
2013-08-27 17:32:53,033 DEBUG - hharris:User logs out.
2013-08-27 15:34:04,153 DEBUG - mtaylor:Dashboard updated. {UUID=00000001-f014-0000-140c-0952ca580801}.

ui.log

This file is located by default in the var/log directory and contains only warning and error messages produced by the client.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 99 files. With this configuration, a node may require up to 1 GB of disk space to store all ui.log files.

Here is an example of the content of this file:

var/log/ui.log
2016-01-20 09:43:56,754 [fx00000003] ERROR flex.querypageletsBundle.queryPageletEditorService - Either onFulfilled or onRejected throws an exception, promise will be rejected with the following error
caused by: Error #1009: Il est impossible d'accéder à la propriété ou à la méthode d'une référence d'objet nul.
TypeError: Error #1009: Il est impossible d'accéder à la propriété ou à la méthode d'une référence d'objet nul.
	at com.systar.silicon.querypagelets.editor::QueryPageletEditorMediator/getDimensions()[/mnt/work/buildslaves/buildslave-08/jenkins/workspace/RTM-rc/tornado/silicon/com.systar.silicon.querypagelets-editor-lib/src/main/flex/com/systar/silicon/querypagelets/editor/QueryPageletEditorMediator.as:410]
	at com.systar.silicon.querypagelets.editor::QueryPageletEditorMediator/setToolTipAndErrorInformation()[/mnt/work/buildslaves/buildslave-08/jenkins/workspace/RTM-rc/tornado/silicon/com.systar.silicon.querypagelets-editor-lib/src/main/flex/com/systar/silicon/querypagelets/editor/QueryPageletEditorMediator.as:284]
	at Function/<anonymous>()[/mnt/work/buildslaves/buildslave-08/jenkins/workspace/RTM-rc/tornado/silicon/com.systar.silicon.querypagelets-editor-lib/src/main/flex/com/systar/silicon/querypagelets/editor/QueryPageletEditorMediator.as:248]
	at com.systar.photon.promises::Promise/transitionState()[/mnt/work/buildslaves/buildslave-08/jenkins/workspace/RTM-rc/tornado/photon/com.systar.photon.foundation-api-lib/src/main/flex/com/systar/photon/promises/Promise.as:196]
	at com.systar.photon.promises::Promise/resolution()[/mnt/work/buildslaves/buildslave-08/jenkins/workspace/RTM-rc/tornado/photon/com.systar.photon.foundation-api-lib/src/main/flex/com/systar/photon/promises/Promise.as:137]
	at com.systar.photon.promises::Promise/resolve()[/mnt/work/buildslaves/buildslave-08/jenkins/workspace/RTM-rc/tornado/photon/com.systar.photon.foundation-api-lib/src/main/flex/com/systar/photon/promises/Promise.as:93]
	at com.systar.photon.remote::RemoteASService$/successListener()[/mnt/work/buildslaves/buildslave-08/jenkins/workspace/RTM-rc/tornado/photon/com.systar.photon.foundation-api-lib/src/main/flex/com/systar/photon/remote/RemoteASService.as:132]
	at mx.rpc::Responder/result()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\Responder.as:46]
	at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyResult()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\AsyncToken.as:199]
	at mx.rpc.events::ResultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\events\ResultEvent.as:172]
	at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\AbstractOperation.as:199]
	at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:263]
	at mx.rpc::Responder/result()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\Responder.as:46]
	at mx.rpc::AsyncRequest/acknowledge()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:74]
	at NetConnectionMessageResponder/resultHandler()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:524]
	at mx.messaging::MessageResponder/result()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\messaging\MessageResponder.as:199]

...

migration-error.log

This file is located in the var/log directory and contains information about failed automatic configuration migrations.

When possible, it also contains manual steps to finalize the migration.

Data integration specific logs

A node creates a directory per space and stores the log files produced by the data integration routes. These files are stored on disk and can be downloaded via the GUI.

These log files are located by default in the var/log/data-integration/<UUID>/ directory (where <UUID> represents the identifier of the space of the route) and are named absorption.log.

The default configuration rotates the log files when the file reaches 10 MB and keep up to 9 files. As a consequence, the default configuration may require up to 100 MB of disk space per data-integration space.

Related Links