Is there a client-side altair units license debug available?
Yes, you can set environment variables...
ALM_LOG_ENABLED=1
ALM_LOG_LEVEL=debug
… and if you can see the log output from the processes being run, then the output can be seen on stderr (by default) - otherwise you’ll need to set:
ALM_LOG_FACILITY=file:filename
The actual ALM_LOG_FACILITY bit is described in the ALSDK documentation as follows:
6. Troubleshooting the ALSDK
-------------------------------------------
[…]
ALM_LOG_FACILITY - valid values are stderr, syslog or file[:filename]. If the
environment variable is not set, or if it is set to an unrecognized value it
will default to stderr. For the file facility, if the optional filename
component is not given a default filename will be used that is:
<tmpdir>\ALM_<date_time_stamp>_<PID>.log
<tmpdir> will be either the value of the TMPDIR environment variable (if set) or
"/tmp" on Unix/Linux systems or the result of GetTempPathA() on Windows. Please
see http://msdn.microsoft.com/en-us/library/aa364992(v=vs.85).aspx for specifics
on how GetTempPath() determines the temporary directory.
If the optional filename component is given there are a few format specifiers
that can be used to control the output filename:
%% A single % character
%p PID of process
%u real UID of process *
%g real GID of process *
%t datetime stamp
* UID and GID are not supported on Windows platforms
So you could have:
ALM_LOG_FACILITY=file:/tmp/ALM_%t_%p.log to get more or less the equivalent of the default log filename.