Error log

Use the -L flag to p4d or the environment variable P4LOG to specify the Helix Core Server error output file. If no error output file is defined, errors are dumped to standard error of the p4d process. Although p4d tries to ensure that all error messages reach the user, if an error occurs and the user application disconnects before the error is received, p4d also logs these errors to its error output.

Helix Core Server also supports trace flags used for debugging. To learn more, see Diagnostic flags for monitoring the server.

Manage log file growth

The log file defined by P4LOG continually grows. To prevent the log file from growing to an unmanagable size, consider writing a script (or a batch file) that automatically renames or moves the log file according to the criteria you choose. You can also rename or move the log manually. When the P4LOG log file is renamed or moved, Helix Core Server automatically creates a new log file in the original location.

The rate of log file growth can be rapid, especially when verbose server logging is enabled. To learn about logging levels, see Using P4LOG.

The Helix Core Server rejects commands when free space falls below certain limits. To learn more, see Monitor disk space usage.