Log messages like: 2014-07-17 23:15:27 socket recv error (110) #4552

issue sipa opened this issue on July 17, 2014
  1. sipa commented at 11:26 PM on July 17, 2014: member

    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?

  2. laanwj commented at 10:39 AM on July 18, 2014: member

    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?

  3. laanwj added the label Docs and Output on Jul 18, 2014
  4. laanwj commented at 10:42 AM on July 18, 2014: member

    My guess is pull #4479. Can you try with 109849e204f91d8b04b0e57da87e45b461096b50 reverted?

  5. laanwj commented at 9:50 AM on August 1, 2014: member

    @sipa are you still having this issue? if so, can you answer the above questions?

  6. sipa commented at 11:30 AM on August 1, 2014: member

    I still have the problem, and reverting 109849e does not fix it.

    Platform: Ubuntu 12.04.4 LTS

  7. laanwj added the label Linux on Aug 1, 2014
  8. laanwj commented at 8:13 AM on August 14, 2014: member

    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)
    
  9. laanwj commented at 8:20 AM on August 14, 2014: member

    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:

    • Remove any remaining bitcoin-config.h in your tree
    • Re-run ./autogen.sh
    • Re-run ./configure
    • Make sure that at least libbitcoin_common_a-netbase.o is rebuilt (but would be safest to just rebuild everything) and bitcoind
  10. sipa commented at 1:04 PM on August 17, 2014: member

    Ugh, that fixed it, weird. Sorry for wasting your time.

  11. sipa closed this on Aug 17, 2014

  12. charliegama commented at 1:55 AM on December 30, 2017: none

    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

  13. fanquake commented at 2:53 AM on December 30, 2017: member

    @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.

  14. fanquake locked this on Dec 30, 2017

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 15:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me