I think this is fixed by https://github.com/mariadb-corporation/MaxScale/commit/bc2f7f4040f3a44617100d23e64948d9db140dfe as there's no more extra information available from the daemon process that maxscale could log.

Hi markus makela,

Yeah, hopefully the fix for MXS-2597 provides enough information most of the time.

For this issue, I was primarily requesting some kind of message like this, in case the service failed to start, and microhttpd didn't provide any useful information:

Attempting to start REST API on [127.0.0.1]:8989

The error message added by MXS-2597 doesn't mention "REST API" at all, so it might still be a good idea to add a message like this during startup. That way, if the user sees an "HTTP daemon error" in the log, then it will be clearer that it was caused by starting the REST API.

Another thing that I noticed about the current log messages is that they don't use a consistent name for the REST API. For example, we can see that when the service successfully starts, the log message refers to the "REST API", but when the service fails to start, the log message refers to the "admin interface."

https://github.com/mariadb-corporation/MaxScale/blob/maxscale-2.3.9/server/core/gateway.cc#L2227

https://github.com/mariadb-corporation/MaxScale/blob/maxscale-2.3.9/server/core/gateway.cc#L2231

It may be more user friendly if the log messages used a consistent name.

Use REST API consistently in the error messages.