List of API calls made
Records interactions with the web server, gives you all the java errors from the web application. It also has debugging information in the case of an error.
It contains Tomcat shut down and restart information.
It also records information on the daily backup such as it's status & any errors that occurred during it.
Records every access request to the web-application. Might be useful for security purposes but not much more.
This is intended to provide an audit trail to track your users' activities so you can see who changed what, and who executed what and when. It doesn't cover all actions, just the ones that we see as critical to identify changes.
It prints out once for every node executed, LDAP and AD information is held here. It gives you some useful info, e.g. if you're trying to work out if someone actually logged in, or made an edit or something.
It contains duplicate information of the webapp log but doesn't have debugging info.
This log is documented in the Help Section in D3SA > System Adminsitration > Managing Permissions > Audit Logging.
That is Postgres own log so there is nothing app-specific there. Might be useful for troubleshooting if something goes wrong in the database.
A recently introduced component which speeds up execution. Up to now all nodes run in a separate process.
So for the Java-based nodes (most of our nodes at this stage) each one would run in it's own JVM.
This is slow and resource-consuming because a JVM has to be started for each node.
The Node container allows us to run multiple nodes in the same JVM, reducing the time to execute and the resource usage.
Nodecontainer logs are the logs associated with the container ...they’re probably not that interesting in themselves except to troubleshoot a system that is not behaving as expected.
The node container is just another process like the server process, so any errors (e.g. in communication to the server, to the individual nodes, anything that happens within the node container that is related to the node container infrastructure, not a specific node), would be in the nodeContainer.<port>.log - basically the same way that anything related to server infrastructure is in server.<port>.log rather than the individual node logs.
nodeContainer.<port>.out is information written to standard out – so it’s similar to the server, it’s what you see in its console output when you launch it.
The .err and .out is just a redirect of standard out and standard error from the node container. So .err would often contain catastrophic type failures that occur (cannot create JVM etc) that can't be written to the node log because the logging infrastructure isn't up, or because the process is crashing - or just anything which is written to standard error (doesn't happen much).
There is more on In-container node execution in the Getting Started section > System Administration > Performance tuning > In-container node execution.
This is an important log file as it contains all the errors from the D3SA Server - licensing errors etc are reported here.