Station output log messages can include errors and warnings that let you why something is not working, as well as simple informational messages about events as they occur. If needed, you can also change the log “level” of station output—see “Station log levels”.
The general format of a station output log message is:
TYPE [timestamp] [station_process] message_text
For example:
INFO [17:05:18 16-Feb-15 EST][fox] FOXS server started on port [4911]
Message log types seen in station output include the following, by leading text descriptor
Typical of most default station output log messages. Usually, each message lets you know some process milestone was started or reached, such as a service or the station itself.
Informs you of a potential problem, such as inability to open a specific port. Typically, warnings do not keep a station from starting.
Informs you of a problem that might keep the station from starting. Or, if it can start, an error that prevents some function of the station from operating correctly.
A verbose debug-level message that may be generated upon every process transaction. Typically this is useful only in advanced debugging mode. You see these for station processes only if you have set the log level at "Trace".
In addition to the “typed” output messages described above, occasionally you may see a string of “java exception” text in the a station’s output. This indicates an unforeseen station execution issue, which can range from a licensing problem, a misconfiguration, or some other unexpected problem. If an unexplained exception reoccurs, copy the exception text and report the problem to Systems Engineering.
Copyright © 2000-2016 Tridium Inc. All rights reserved.