P2P log messages appear in console and default.log

[abitmore]

Bug Description

P2P log messages appear in console and default.log . They should be in p2p.log .

Log messages:

2461180ms th_a application.cpp:598 handle_block ] Got block: #17580000 010c3fe0f702a54896d1423f72a28c724adf3ba7 time: 2017-06-20T07:07:21 transaction(s): 2 latency: 121718020180 ms from: verbaltech2 irreversible: 17579981 (-19)
355441ms p2p tcp_socket.cpp:169 bind ] Exception binding outgoing connection to desired local endpoint 0.0.0.0:32979: bind: Bad file descriptor
355442ms p2p tcp_socket.cpp:169 bind ] Exception binding outgoing connection to desired local endpoint 0.0.0.0:32979: bind: Bad file descriptor
355442ms p2p tcp_socket.cpp:169 bind ] Exception binding outgoing connection to desired local endpoint 0.0.0.0:32979: bind: Bad file descriptor
355442ms p2p tcp_socket.cpp:169 bind ] Exception binding outgoing connection to desired local endpoint 0.0.0.0:32979: bind: Bad file descriptor
365664ms p2p tcp_socket.cpp:169 bind ] Exception binding outgoing connection to desired local endpoint 0.0.0.0:32979: bind: Bad file descriptor

Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.

• API (the application programming interface)
• Build (the build process or something prior to compiled code)
• CLI (the command line wallet)
• Deployment (the deployment process after building such as Docker, Travis, etc.)
• DEX (the Decentralized EXchange, market engine, etc.)
• P2P (the peer-to-peer network for transaction/block propagation)
• Performance (system or user efficiency, etc.)
• Protocol (the blockchain logic, consensus, validation, etc.)
• Security (the security of system or user data, etc.)
• UX (the User Experience)
• Other (please add below) : logging

Host Environment
Please provide details about the host environment. Much of this information can be found running: witness_node --version.

• Host OS: -
• Host Physical RAM -
• BitShares Version: 5.2.0
• OpenSSL Version: -
• Boost Version: -

CORE TEAM TASK LIST

• Evaluate / Prioritize Bug Report
• Refine User Stories / Requirements
• Define Test Cases
• Design / Develop Solution
• Perform QA/Testing
• Update Documentation

[abitmore]

Fixed by #2436.