Unit maintains a single general-purpose log for diagnostics and troubleshooting
(not to be confused with the access log).
Usually, the log file is found here:
/var/log/unit.log; to locate it in
$ unitd --help unit options: ... --log FILE set log filename default: "/path/to/unit.log"
Use unitd --log <filename> to set the location at startup. To check the settings of a running unitd:
$ ps ax | grep unitd ... unit: main v1.8 [/path/to/unitd --log /path/to/unit.log --pid /path/to/unit.pid]
If Unit’s not running, see its startup scripts or configuration files in your system to discover the log location.
Unit log has two verbosity modes: common and debug; steps to enable the latter vary by install method.
Debug log is meant for developers; it grows rapidly, so enable it only for detailed reports and inspection.
Installation From Our Repositories§
Our repositories provide a debug version of unitd called unitd-debug within the unit package:
# unitd-debug <command line options>
Also, there are debug symbol packages for core dump analysis; their names