[1429] Logging fixes

src/bin/bind10/bind10_messages.mes

@@ -99,7 +99,7 @@ The boss module is sending a kill signal to process with the given name,
 as part of the process of killing all started processes during a failed
 startup, as described for BIND10_KILLING_ALL_PROCESSES
 
-% BIND10_LOST_SOCKET_CONSUMER consumer of sockets disconnected, considering all its sockets closed
+% BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed
 A connection from one of the applications which requested a socket was
 closed. This means the application has terminated, so all the sockets it was
 using are now closed and bind10 process can release them as well, unless the

src/bin/bind10/bind10_src.py.in

@@ -876,7 +876,7 @@ class BoB:
             unix_socket.sendall(CREATOR_SOCKET_OK)
             libutil_io_python.send_fd(unix_socket.fileno(), fd)
         except Exception as e:
-            logger.error(BIND10_NO_SOCKET, token, e)
+            logger.info(BIND10_NO_SOCKET, token, e)
             unix_socket.sendall(CREATOR_SOCKET_UNAVAILABLE)
 
     def socket_consumer_dead(self, unix_socket):
@@ -885,7 +885,7 @@ class BoB:
         sockets sent to it are to be considered closed. This function signals
         so to the _socket_cache.
         """
-        logger.error(BIND10_LOST_SOCKET_CONSUMER, unix_socket.fileno())
+        logger.info(BIND10_LOST_SOCKET_CONSUMER, unix_socket.fileno())
         try:
             self._socket_cache.drop_application(unix_socket.fileno())
         except ValueError: