logs do not report error when running bitmask-root
I had an older bitmask-root. Running bitmaskctl vpn start DOMAIN
failed to run because it could not run bitmask-root. The error showed up in /var/log/syslog:
Feb 11 14:33:27 crow bitmask-root: bitmask-root: ERROR: Bad argument tcp4
Feb 11 14:33:27 crow bitmask-root: ERROR: could not parse openvpn options
but these errors never showed up in the bitmask log file or were reported back to bitmaskctl. instead of reporting a fatal error, bitmaskctl just keep trying to connect to the openvpn management interface.
the expected behavior should be that if the call to bitmask-root returns an error code, it halts the vpn start procedure, does not attempt to connect to openvpn management, and reports a fatal error through the API.