This is a followup to LBCLASSIC-143 which changed the message from ERROR to WARN.

The WARN message still results in a dump of the logging status messages.
This means that a whole bunch of text is printed to the console whenever Lilith is started - and it looks quite broken due to the stacktrace.

So there are two possible solutions for this problem:
a) the status is only printed in case of an ERROR
b) SocketAppender considers this as an INFO instead of a WARN.

I think b) would be reasonable. Other WARNs are much more important, like duplicate logback.xml.

Lilith is only an example, btw.
We routinely add SocketAppender[localhost] to our console applications. In case of trouble one can simply start Lilith and check the logs that way instead of reading them on the console.

The default use-case is executing the app without Lilith, though, so we get the logback status messages on every start - which is quite noisy and annoying.