Since some time I'm seeing log messages like:
2014-07-17 23:15:27 socket recv error (110)
Since some error messaging change, I believe. Shouldn't there be a more specific error message?
Since some time I'm seeing log messages like:
2014-07-17 23:15:27 socket recv error (110)
Since some error messaging change, I believe. Shouldn't there be a more specific error message?
Strange. Here they look like this (as of yesterday's master):
2014-07-18 10:37:40 socket recv error Connection reset by peer (104) 2014-07-18 10:18:25 socket recv error Connection timed out (110)
What platform?
I still have the problem, and reverting 109849e does not fix it.
Platform: Ubuntu 12.04.4 LTS
Curious - I've just tried this on an Ubuntu 12.04 VM, even killed a few connections with tcpkill to get similar error messages, but cannot reproduce it:
2014-08-14 07:36:08 connect() to 127.0.0.1:12345 failed after select(): Connection refused (111)
2014-08-14 08:11:42 socket send error Connection reset by peer (104)
I think you have a stale configuration header file (causing STRERROR_R_CHAR_P not to be set, though it should be). Can you try the following:
bitcoin-config.h in your treelibbitcoin_common_a-netbase.o is rebuilt (but would be safest to just rebuild everything) and bitcoindUgh, that fixed it, weird. Sorry for wasting your time.
Pleaase help, errors in debug.log - Scrypt algorit -
2017-12-30 01:05:54 socket recv error 104 2017-12-30 01:08:10 socket recv error 104 2017-12-30 01:18:42 socket recv error 110 2017-12-30 01:24:15 socket recv error 110 2017-12-30 01:30:03 socket recv error 110 2017-12-30 01:30:05 socket recv error 104 2017-12-30 01:30:33 socket recv error 110 2017-12-30 01:31:11 socket recv error 110 2017-12-30 01:36:36 socket recv error 104 2017-12-30 01:39:25 socket recv error 110
@charliegama Please don't post in multiple year old issues, open a new one. However, bitcoin-core doesn't use "Scrypt", so you might have the wrong repository.