LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: lae_errors

This post has been created for discussion of error code brain.unhandledLogging.

Please reply to this thread with any description of error conditions, diagnostic information, and recommended resolutions.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

This is a very generic error code that can appear in the log.
It might actually not indicate any problem at all, or it could be something quite serious.
Essentially any error messages that come from within a node itself will be written to the log using some other error code.
Anything that comes with a "brain.unhandledLogging" code is something where some information is being written to the standard out, or standard error channels of the node.

This could be something trivial, for instance if you are writing a java node and using a 3rd party jar that is just writing to its standard out channel.
It may mean nothing.

However, in many cases, it can be that the execution infrastructure of the node has encountered a fatal error.
For instance, if you are executing a node and the entire JVM (Java Virtual Machine) for the node crashes, or in a node where an attempt is made to access a protected area of memory, then such information may end up with an error code of "brain.unhandledLogging".

If you have written your own Java or Python node and are writing to the standard error or standard out channels (using System.out/System.err.println in Java or print >> or sys.stdout.write or sys.stderr in Python) then you should modify your code to instead use the logger().log/debug/info/warn/error/ methods in Java or the self.logLow,logHigh etc methods in Python.
For more information, consult the Java Node Getting Started Guide, or the Python Node Getting Started Guide.

If you are writing a Java node and the issue is with a 3rd party jar that you have included which is writing to standard out or standard error and the node is failing, then you probably need to investigate the 3rd party API further.

If the log event is occurring when running a standard node provided with the LAE or LAL and the node itself is failing, then you it is likely that you may need to contact your Lavastorm Support representative about the problem.