storlets

loglines lost with the introduction of host logging for docker container

Bug #1495601 reported by Eran Rom
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
storlets
New
Undecided
Unassigned

Bug Description

Here is a list of the lost log lines:
Aug 5 14:30:28 UNKNOWN_LOCALHOST [main] StorletDaemon_com.ibm.storlet.test.test1 TRACE com.ibm.storlet.test.test1: SBus listen() returned
Aug 5 14:30:28 UNKNOWN_LOCALHOST [main] StorletDaemon_com.ibm.storlet.test.test1 TRACE com.ibm.storlet.test.test1: Calling receive
Aug 5 14:30:28 UNKNOWN_LOCALHOST [main] StorletDaemon_com.ibm.storlet.test.test1 TRACE com.ibm.storlet.test.test1: Receive returned
Aug 5 14:30:28 UNKNOWN_LOCALHOST [main] StorletDaemon_com.ibm.storlet.test.test1 TRACE com.ibm.storlet.test.test1: Calling createStorletTask with com.ibm.storlet.sbus.SBusDatagram@2c9596e
Aug 5 14:30:28 UNKNOWN_LOCALHOST [main] StorletDaemon_com.ibm.storlet.test.test1 TRACE createStorletTask: received EXECUTE command
Aug 5 14:30:28 UNKNOWN_LOCALHOST [main] StorletDaemon_com.ibm.storlet.test.test1 TRACE StorletTask: Got 5 fds
Aug 5 14:30:28 UNKNOWN_LOCALHOST [main] StorletDaemon_com.ibm.storlet.test.test1 TRACE createStorletTask: fd 0 is of type SBUS_FD_INPUT_OBJECT

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.