maxctrl2 terminates if invoked in directory without write rights

Maxctrl2 uses the same log-mechanism as MaxScale and creates a log-file in the current directory. That fails under docker, since maxctrl2 is run using the maxscale user, but the CWD is /, where the log-file obviously cannot be created.

Maxctrl2 should be more resilient to this kind of situation.