Issues with MATLAB® Production Server™ instances can manifest as connectivity failures, slow downs, or server instance crashes. Use log information generated by a server instance to diagnose and solve problems.
endpoint-root | Folder used to store server named endpoints |
hide-matlab-error-stack | Hide the MATLAB stack from the clients |
log-archive-max-size | Maximum size of the log archive folder |
log-archive-root | Path to the folder containing archived log files |
log-root | Path to the log file folder |
log-rotation-size | Size at which the log is archived |
log-severity | Severity at which messages are logged |
log-handler | Add custom log handler |
pid-root | Folder used to store PID files |
profile | Turn profiling on or off |
mps-check | Test and diagnose a MATLAB Production Server instance for problems |
mps-profile | Turn profiling on or off |
mps-status | Display status of a server instance |
mps-support-info | Display licensing and configuration information of a MATLAB Production Server instance |
mps-which | Display path to server instance that is currently using the configured port |
Verify that the server is started
To diagnose a problem with a server instance or configuration of MATLAB Production Server, do the following, as needed:
Diagnose a Corrupted MATLAB Runtime
This example shows a typical diagnostic procedure you might
follow to solve a problem starting server prod_server_x.
Use these recommendations as a guide when defining values for the options listed in Log Retention and Archive Settings.
Each server writes a log file containing data from both the
main server process, as well as the workers, named server_name/log/main.log
Common Error Messages and Resolutions
Commonly caused by requesting a component that is not deployed on the server, or trying to call a function that is not exported by the given component.