Skip to content

Conversation

@rebroad
Copy link
Contributor

@rebroad rebroad commented Jul 25, 2016

…ones.

For years, I've been getting many many of these in my debug.log:-

2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719
2016-07-25 15:10:45 Unknown command "notfound" from peer=62719

This pull request will remove this message, which is technically incorrect anyway.


boost::this_thread::interruption_point();
if (inv.type == MSG_TX || inv.type == MSG_WITNESS_TX)
LogPrint("tx", "notfound: %s from peer=%d\n", inv.ToString(), pfrom->id);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you really want to log a line for every single record? This can be up to 50,000 in one message.

@laanwj
Copy link
Member

laanwj commented Jul 25, 2016

Concept ACK, though I think the number of log lines per message should be limited.

@gmaxwell
Copy link
Contributor

Do we need to log any details here at all? We've done fine for years without doing so...

@sipa
Copy link
Member

sipa commented Jul 26, 2016 via email

@laanwj
Copy link
Member

laanwj commented Jul 26, 2016

Agree @sipa.
"just don't regard them as unknown" would be the most obvious, and likely best, solution.
Now you just move them to two other log classes, which get burdened with more messages.

If you really, really want to log them (say, for debugging purposes) they should be in a separate log class, and the entire processing should be skipped if this log class is not enabled.

@laanwj
Copy link
Member

laanwj commented Jul 29, 2016

Closing in favor of #8427.

@laanwj laanwj closed this Jul 29, 2016
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants