...

Queue Status

Queue Status Details

Scheduling of jobs

aborting jobs, automatic aborts, automatic scheduling

Logging and Verbosity

Standard Log Files

...

1. By default the configuration property log_level  controls all logging. The default value for this is info.
2. If you start the nmis daemon with a debug=<level> command line argument, then that will be used for this daemon and its  workers.
3. For node-admin and nmis-cli invocations the same debug=<level>  command line argument is available.
4. A manually scheduled daemon job can have a custom verbosity and output   propertes,  property, which applies to which control verbosity and target log file for the processing of this job only.
5. All NMIS daemon instances can be instructed to change their verbosity levels  on the fly while the processes remain running, by sending particular UNIX signals to those processes.

Per-job verbosity and custom log file

If a job schedule includes the property job.verbosity=<level> , then the  job will be processed with that verbosity level. At the end of processing the previous verbosity level is restored.

The related but independent property job.output=<prefixtext>  instructs  the NMIS daemon to divert all logging for this one job to a different log file. The log data is saved in the normal logs  directory, and the file is named <prefixtext>-<highprecision-timestamp>.log , e.g. logs/quicktest-1564031667.44838.log. When processing completes log output reverts back to the standard log file.

Adjusting process verbosity levels on the fly

All NMIS daemon processes listen for two particular UNIX signals:

...