Log file names

Local Log File Names

For local AEs, three log files are created in the log directory per machine (host or SPUs)--a text file, stderr, and stdout.

By default, when using register_ae and NZAE_LOG_DIR, the main log file name has the format:

NZAE-<function-name>-<machine-name>-<transaction-id>-<undocumented stuff>.txt

There is also a standard output and standard error log file with the same name suffixed by _stdout.txt or _stderr.txt.

Examples

nzae-applyOperationV2Tf-hostname-2660-24771-10167-17646.txt
nzae-applyOperationV2Tf-hostname-2660-24771-10167-17646.txt_stderr.txt
nzae-applyOperationV2Tf-hostname-2660-24771-10167-17646.txt_stdout.txt

Remote Log File Names

Log file naming differs with remote AEs. When a remote AE is started, it has its own standard output and standard error log files that all function requests share. Therefore, the NZAE_LOG_DIR setting must be used in the launch registration.

Examples

nzae-apply_launch_v1-hostname-2662-24771-15233-launch-noexecae17646.txt_parent.txt
nzae-apply_launch_v1-hostname-2662-24771-15235-launch-17646.txt
nzae-apply_launch_v1-hostname-2662-24771-15235-launch-17646.txt_stderr.txt
nzae-apply_launch_v1-hostname-2662-24771-15235-launch-17646.txt_stdout.txt

Each request has its own main log file but its standard output and error goes to the remote AE log files. If the AE does not reach the printf statements, check the main log file for AE error messages.