NOTE: This is affecting more versions I believe (I checked 8.2.24, 8.2.22, and couple others).
Starting daserver in daemon mode through either systemctl or manually (daserver --daemon something) is NOT working.
According to daserver usage:
Yet the code parsing arguments doesn't seem to care (at least at one point) about <instanceName>.
Now when starting daserver in interactive mode, this is not an issue.
When starting daserver in daemon mode, adding the <instanceName> will cause the program to exit right away.
The email@example.com ExecStart is defined as such:
When parsing arguments there, it just skips the --daemon argument, and no <instanceName> is collected/swallowed.
So the next argument will be "mydali" and it will fall in https://github.com/hpcc-systems/HPCC-Platform/blob/community_8.2.26-1/dali/server/daserver.cpp#L437 and exit.
Since daemon(1,0) is used, any standard output is redirected to /dev/null (correct me if I'm wrong). So it's impossible to notice that in say syslog or anywhere else at the moment.