Collecting Logs and Core Files

If checking the configuration yields no errors, then all useful log files should be collected for further investigation.

See Also
Java Activation Error on the ENOVIA Live Collaboration Server
mx_err_pid.log for Windows
Additional Live Collaboration Server Configuration Troubleshooting

The following is the minimum set of logs that you should gather:

Logs and Files to Collect
Stack traces
Cores
App server logs
Any trace logs
Java stack trace logs (hs_err_pid*.log)
access.log (app server)
mxtrace.log
Custom logs (redirected stdout and stderr)
mxAudit.log
mx_err_pid.log

Use the following table as a quick reference for stack trace commands. Sometimes it's useful to generate a stack trace from a core and save it to a file.

Platform Stack Trace Command
Windows mx_err_pid.log found in MX_TRACE_FILE_PATH.
Linux
  1. Run gdb with the following parameters:
    • The executable which caused the crash, as the second parameter; /usr/local/jdk/bin/java in the example below.
    • The core file, as the third parameter; core.2442 in the example below.

    Example:

    gdb /usr/local/jdk/bin/java core.2442
  2. Enter the command thread apply all where and send all output.
Note: If you don't know the executable which caused the crash, replace the executable by - as the second parameter in the command syntax.

Example:

gdb - core.2442

A line in the gdb output identifies the executable. For example: 

Core was generated by `/usr/java/jdk1.7.0_07/bin/java -Djava.util.logging.config.file=/logici'.

Type quit and run gdb.

The Live Collaboration server will log error messages to the mxtrace.log and other log files. If a shutdown occurs, a file called the Java stack dump log is created. It is named hs_err_pidxxxx.log, where xxxx is the Process ID number of the process that shut down. These logs can be found in the same directory from which the 3DSpace kernel loads, usually the SERVER_INSTALL path under PLATFORM\code\bin\.

These logs are critical for reporting a shutdown-related problem to 3DSpace, especially if no core is found. If the system has produced a core file for the shutdown (Unix-only, and the file is simply called core), this file will usually appear in the directory from which the 3DSpace kernel was loaded.