8
2016-Jul-30 22:32:06.864931 [P2P0][x.x.x.x:18080 OUT]NOTIFY_NEW_BLOCK (hop 3)
2016-Jul-30 22:32:06.865073 [P2P5][x.x.x.x:18080 OUT]NOTIFY_NEW_BLOCK (hop 4)
2016-Jul-30 22:32:06.865221 [P2P1][x.x.x.x:18080 OUT]NOTIFY_NEW_BLOCK (hop 2)
2016-Jul-30 22:32:06.865326 [P2P2][x.x.x.x:18080 OUT]NOTIFY_NEW_TRANSACTIONS
2016-Jul-30 22:32:06.865449 [P2P2][x.x.x.x:18080 OUT]NOTIFY_NEW_BLOCK (hop 2)
2016-Jul-30 22:32:06.835879 [P2P5][x.x.x.x:18080 OUT]COMMAND_TIMED_SYNC
-field1-------------------| |-f2-| -field3----------|----field4----------

So, field 1 is obvious the date and time (local system time?).

Field 2 (here as f2) - what is this? P2P instance 1? There only ever seems to be 0-9, even when my daemon says I have 40 OUT connections.

Field 3 is the IP and port of the peer, and whether the local node initiated the connection or the peer node.

Field 6 is the command or notification? What does the hop mean? Does hop 0 mean that the local daemon is the first to receive this block notification (with the peer node being the solver of the block), and hop 1 would mean that there is 1 other node between you and the block solver?

And what is command_timed_sync mean?

Giacomo1968
  • 117
  • 5
Ginger Ale
  • 5,694
  • 2
  • 19
  • 46

1 Answers1

3

Not sure random debug log questions are on topic for stack exchange, but...

Field 2 is the thread logging this message.

Hop is the (untrusted) number of peers forwarding the object.

COMMAND_TIMED_SYNC is one of the P2P traffic messages.

user36303
  • 34,928
  • 2
  • 58
  • 123