-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dashd hangs with "failed after select(): Connection refused (111)" #518
Comments
I've been seeing this issue on other coins as well, I think it may be some kind of DoS. |
Obsolete |
I see the same problems with dashd from ppa:dash.org/dash 2018-10-04 11:10:15 ProcessMessage(reject, 42 bytes) FAILED peer=22 |
2015-08-12 04:45:41 ProcessMessageMasternodePOS::mnse - nHeight 317910 MasternodeA 178.33.98.125:9999 MasternodeB 216.189.153.59:9999
2015-08-12 04:45:41 keypool reserve 2
2015-08-12 04:45:41 keypool return 2
2015-08-12 04:45:41 keypool reserve 2
2015-08-12 04:45:41 keypool return 2
2015-08-12 04:45:41 keypool reserve 2
2015-08-12 04:45:41 keypool return 2
2015-08-12 04:45:41 keypool reserve 2
2015-08-12 04:45:41 keypool return 2
2015-08-12 04:45:41 keypool reserve 2
2015-08-12 04:45:41 keypool return 2
2015-08-12 04:45:41 keypool reserve 2
2015-08-12 04:45:41 keypool return 2
2015-08-12 06:15:43 socket inactivity timeout
2015-08-12 06:15:43 connect() to 80.82.64.100:9999 failed after select(): Connection refused (111)
2015-08-12 06:15:48 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:18:33 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:21:18 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:24:02 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:26:47 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:29:32 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:32:16 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:35:01 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:37:46 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:40:30 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:43:15 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:46:00 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:48:44 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:51:29 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:54:14 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:56:58 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 06:59:43 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 07:02:28 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 07:05:12 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 07:07:57 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 07:10:42 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 07:13:26 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
2015-08-12 07:16:11 connect() to 69.46.69.90:9999 failed after select(): Connection refused (111)
These errors repeat in the logs for several hours. No other activity.
The text was updated successfully, but these errors were encountered: