End users need to know if the client service is working or not, and they do so by running systemctl status velociraptor-client. At boot time the client starts before the network and there is a "network is unreachable" message. We were logging this at ERROR level because INFO level messages won't show without --verbose, and that level is too verbose and spams the journal, see https://github.com/SUSE/linux-security-sensor/issues/65 . But end users only see error messages without any positive messages to say a connection was made, and they assume there is a problem. Fix this by writing failure/waiting/connected messages to stderr.
End users need to know if the client service is working or not, and they do so by running
systemctl status velociraptor-client. At boot time the client starts before the network and there is a "network is unreachable" message. We were logging this at ERROR level because INFO level messages won't show without --verbose, and that level is too verbose and spams the journal, see https://github.com/SUSE/linux-security-sensor/issues/65 . But end users only see error messages without any positive messages to say a connection was made, and they assume there is a problem. Fix this by writing failure/waiting/connected messages to stderr.