Bitmessage/PyBitmessage-2024-12-01
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 53 Actions Packages Projects Releases 5 Wiki Activity

Failure to connect shouln't be an error

Browse Source 
It resulted in too many errors in the logs
This commit is contained in:
mailchuck 2015-11-26 02:35:59 +01:00 committed by Peter Surda
parent d0b73eb211
commit 0c19e0c2e4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/class_outgoingSynSender.py
View File

@ -213,7 +213,7 @@ class outgoingSynSender(threading.Thread, StoppableThread):
logger.error('Bitmessage MIGHT be having trouble connecting to the SOCKS server. ' + str(err)) logger.error('Bitmessage MIGHT be having trouble connecting to the SOCKS server. ' + str(err))
else: else:
if shared.verbose >= 1: if shared.verbose >= 1:
logger.error('Could NOT connect to ' + str(peer) + 'during outgoing attempt. ' + str(err)) logger.debug('Could NOT connect to ' + str(peer) + 'during outgoing attempt. ' + str(err))
deletedPeer = None deletedPeer = None
with shared.knownNodesLock: with shared.knownNodesLock: