ZET Fails to create pipe for commands

[mikegorman-nf]

When running the ZET, the fact that the pipe cannot be set up due to no ziti group, etc. is lost quickly in the logging depending on level. Some better way to indicate the problem, or mitigate it would be beneficial.

[qrkourier]

Background: The current behavior prioritizes having a running tunneler over failing loudly.

Things that might fail but don't cause the tunneler to exit include setting up the IPC socket/pipe you mentioned and configuring DNS.

As for IPC, I expect the first symptom with the current behavior is the IPC sender failing to connect. That sender is either ZET itself or the Desktop Edge app. Is that where you smelled the problem, @mikegorman-nf?

One way to handle this unclear failure mode is to feedback to the user in the sender app because the IPC receiver is probably in the background anyway.

[sabedevops]

@qrkourier There are a number of control flow situations in he DNS auto-configuration which do cause the tunneler to exit loudly.