BitShares Forum
Main => General Discussion => Topic started by: emski on July 27, 2014, 06:49:25 am
-
All my delegates suddenly started missing blocks.
I've check the forks and it seems like my delegates produce block in time, however other delegates' blocks are included into the chain.
I had 30+ connections and everything looked normal though all delegates were missing blocks.
65964
c3c06bf0f181a5a20ccfb99aac97be655c888add lotto-delegate 0 166 2014-07-27T03:57:00 0 YES NO
1f36f9dd3698a23146ba23969f522905197601ee clout-delegate4 1 361 2014-07-27T03:57:10 0 YES YES
65967
e29d411334d7cf014d01d29d8bcbb13d29a957cb lotto.bitdelegate 0 166 2014-07-27T03:57:40 0 YES NO
d5d6f0a074bf6a678dc8ddae7a7f7526faac573f init13 0 166 2014-07-27T03:57:50 0 YES YES
65975
663f2f2335ceb05c0748d1989ca43a222cf60cbb emski 0 166 2014-07-27T03:59:10 0 YES NO
d6cb455f210c2ada0fe5cd79492e474b658754bb donation 2 588 2014-07-27T03:59:20 0 YES YES
65987
135e681fbd187d4e88f8ffeeeb8c454b011f2211 angel.bitdelegate 0 166 2014-07-27T04:01:30 0 YES NO
2188d6ecd31459782b774fd5ff64c5d0934cdbb8 spartako 0 166 2014-07-27T04:01:40 1 YES YES
66036
e1504729a0a3b5e1e45bca1f8e489363913cba5f emski.bitdelegate 0 166 2014-07-27T04:10:20 0 YES NO
ae39a8e8198296260931f9c7a771d8ef649148ad zhangliangying 4 976 2014-07-27T04:10:40 0 YES YES
66039
9d72429055e46708a5ce07570d000e5f0bbeed7a angel-delegate 0 166 2014-07-27T04:11:10 0 YES NO
6c25e82136b5e7af2c4f94085f05e26f943fbed1 riverhead-del-server-1 0 166 2014-07-27T04:11:20 0 YES YES
66059
e21605b7f1f4cbc7c706bdc43735cabd80ff2b99 emski 0 166 2014-07-27T04:14:40 0 YES NO
a387d388cf4ebce5810616585dcb66a1c5750934 titan.crazybit 0 166 2014-07-27T04:14:50 1 YES YES
66066
2bf11fd78b0e125106fa058c1f422420a61160e6 lotto-delegate 0 166 2014-07-27T04:16:10 0 YES NO
8ade47262f3e68cd2c2fe4ecb38b0ed819c0e034 btsx.chinesecommunity 1 359 2014-07-27T04:16:20 4 YES YES
66090
8beb997cc47e1dad208fb878f2901d4195f4ee32 lotto.bitdelegate 0 166 2014-07-27T04:20:40 0 YES NO
dfefcc81905fb43e4dc1d2d34c111655c89bb6af init65 0 166 2014-07-27T04:20:50 0 YES YES
66116
c454c7e8a85b8f48611b456f763128a649b076f5 angel.bitdelegate 0 166 2014-07-27T04:25:30 0 YES NO
06e7bccc79ae14891eab165d71a9a7454358711f dac.bts500 0 166 2014-07-27T04:25:40 1 YES YES
66124
2f288913cc822c16537820397d797f2479e61c30 angel-delegate 0 166 2014-07-27T04:27:10 0 YES NO
bd81c8820dd9caee56ad8a1d3d0276bb9318e775 delegate.webber 0 166 2014-07-27T04:27:20 0 YES YES
66134
8a731e48aa8a714cf59059372fd5e3f680762f04 emski.bitdelegate 0 166 2014-07-27T04:29:10 0 YES NO
560343177239cf71291f189666812e8010a8b4f9 init59 0 166 2014-07-27T04:29:20 0 YES YES
66147
5fc70347559f9047d15bf456a774ddc50960fe0e emski 0 166 2014-07-27T04:31:30 0 YES NO
bf76f773a74471cffdc5bc01c6e09e43df39648f titan.crazybit 0 166 2014-07-27T04:31:40 1 YES YES
66150
7c0d1d910860055766762bf9e13ac13039d5b019 delegate-alt 0 166 2014-07-27T04:32:20 1 YES NO
ae2796d0ad12574e070cfacb59ec88e7c8d29562 init58 0 166 2014-07-27T04:32:10 21 YES YES
66153
c2dc771cae5db44c1e0f693f92231243809d7e17 lotto-delegate 0 166 2014-07-27T04:33:00 0 YES NO
b51d54b0e3ff6802a0324c3a37748cf423472f1b btsx.chinesecommunity 0 166 2014-07-27T04:33:10 4 YES YES
66155
aea653e9a6855ad15dec82e8c7c362558d13f9b3 emski 0 166 2014-07-27T04:33:40 0 YES NO
625809665ad0f1715e66d6d80bbd7a595e432974 liondani 0 166 2014-07-27T04:33:50 0 YES YES
66162
eaf4d52f42779e1fcb5a5aff5754cae491d631d7 lotto-delegate 0 166 2014-07-27T04:35:00 0 YES NO
37fab9e079f961b47e0ae0dab2f4efa09fdcfe3b delegate.follow-my-vote 1 359 2014-07-27T04:35:20 1 YES YES
Everything went back to normal after I restarted.
I'll investigate further what might be the issue...
-
I have run into similar issues. I reboot regularly to prevent it. I don't know about you, but I get tons of
--- there are now 51 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 51 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 49 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 49 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 49 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 49 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 49 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 51 active connections to the p2p network
--- there are now 50 active connections to the p2p network
--- there are now 51 active connections to the p2p network
spam in my CLI. I know I could turn it off, but I don't because I've noticed that when my box is about to lock up, those stop. So if I log in and I don't see tons of that spam, I restart the client. I could be completely wrong on this as well. The sample size of missing blocks for me is very small. Two instances due to this to be exact.
-
Me too I had the same problem, suddenly I started to create a lot of forks
068a3d24c98602be853a5e15699b63a7c3d6ed1c spartako2 0 166 2014-07-27T11:16:50 0 YES NO
b289e893b412acf484b88e454bad4418f422d89a init53 0 166 2014-07-27T11:17:00 0 YES YES
68431
a3c0410fda4fa097255627a3454d3cb017e052ca init80 0 166 2014-07-27T11:25:00 0 YES YES
9fe043bc51c4de870d7dd61cbc1caf1c446b9255 maqifrnswa 0 166 2014-07-27T11:24:50 11 N/A NO
68501
7c96cebf72bd6fe5ddc87aa67ca3946a89313b6c spartako1 0 166 2014-07-27T11:37:10 0 YES NO
b93c2e133be3220e35796bab119c84d536e3e0da init53 0 166 2014-07-27T11:37:20 0 YES YES
68520
71a63a6e8818e1b5d5222fe24f768ce5d294b222 init72 0 166 2014-07-27T11:40:40 0 YES YES
7ecc54c8ec826cda8517f57aa67762336cab9b14 maqifrnswa 0 166 2014-07-27T11:40:30 11 N/A NO
68534
529281df880628f31e83ce67f88b268aa8645768 spartako2 0 166 2014-07-27T11:43:10 0 YES NO
17ff293763a9c5244d05f7aeb5032e8ee26b9803 dac.bts500 0 166 2014-07-27T11:43:20 1 YES YES
68549
7ea108d821ba3df465e3139ad09703e7622b5c18 spartako 0 166 2014-07-27T11:45:50 0 YES NO
9dd070bdacb856a8d423413c4987aaf70fb5fcbc emski 2 562 2014-07-27T11:46:00 0 YES YES
68562
f707a50faaaba219d538d224501ff8a6e42f9c9e init42 0 166 2014-07-27T11:48:10 11 YES NO
050dfb2c83c2d46e64378255ca6c5b5933dc9dfc btsdac-delegate 0 166 2014-07-27T11:48:20 2 YES YES
68590
4b6e05f676179954fc0c4e39f88dc4429c867646 init4 0 166 2014-07-27T11:53:10 21 YES YES
1062dad0f9872c8786d5d22980ab6e947753f81d delegate.bitder 0 166 2014-07-27T11:53:30 1 N/A NO
68630
b20168e4941b623c9be9290eb13d496a2d439fde spartako1 0 166 2014-07-27T12:00:20 0 YES NO
2b3fe08ea05debbf2336b5ce7af6037714d4db19 delegate.adam 0 166 2014-07-27T12:00:10 21 N/A NO
143764d30b6aec973874b59245bdd0d5504a28e9 bitsuperlab 0 166 2014-07-27T12:00:00 31 N/A NO
082d72c00b2ce1037f2c738c33dd36fb1605fee6 init42 0 166 2014-07-27T12:00:30 1 YES YES
68650
0bdf5de4375695b35ac143108916addb19a0ce62 init8 0 166 2014-07-27T12:03:50 11 YES NO
1350d86b086542ef8bf14b39f39f9cef99fb5ed6 emski 0 166 2014-07-27T12:04:00 1 YES YES
68665
3ff9bd2027a90752da209677c82d4d062fa17f93 maqifrnswa 0 166 2014-07-27T12:06:30 0 YES NO
8c927824e161a7469d7a23bf2fef189700c2c3e6 clout-delegate2 0 166 2014-07-27T12:06:50 0 YES YES
68686
63a52d50f0cfaa9b2293cbaa99774252168a199c fox 0 166 2014-07-27T12:10:30 1 YES YES
c4f9c45528077c6dbf1c3575c9f7883d6b863bbb init8 0 166 2014-07-27T12:10:20 11 N/A NO
68699
611e13c2ce81ca9d5326baf1c4c21332d17684b1 delegate.charity 0 166 2014-07-27T12:12:50 0 YES YES
77dce155151ac819e7eb9207e8901db0b07b9399 init28 0 166 2014-07-27T12:12:40 11 N/A NO
68710
76c3d3bf5481f666c9985e74bfbcc39616cf7e9d spartako1 0 166 2014-07-27T12:14:40 0 YES NO
eeea406f6dc8ebbf20724216fb02c186fa6d4647 delegate.taolje 0 166 2014-07-27T12:14:50 1 YES YES
Now I have restarted the client and it seems that it works:
68739 2014-07-27T12:19:30 spartako 0 166 0.00000 BTSX 15 0.003272
-
me too
来自我的 HUAWEI P7-L00 上的 Tapatalk
-
I've stumble upon similar issue I've reported on the last few dry runs.
There was a single IP creating 20+ connections then instantly disconnecting. This is repeats each second.
However this time there were several of these IP addresses.
I don't know if it is a bug or something else. I'll try to block for a few hours the IPs following this pattern and report back.
-
There needs to be some serious defensive logic in the delegates code. Bitcoind has that even for regular clients.
Suggestions:
- Limit number of times someone connects to you in a 5 minute interval. Once connected they can just stay connected.
- Eliminate fake connections designed to just reduce the usability of the server
- Make it so a delegate can hide and deliver their block signature through any random node on the network
- etc. etc. etc.
-
There needs to be some serious defensive logic in the delegates code. Bitcoind has that even for regular clients.
Suggestions:
- Limit number of times someone connects to you in a 5 minute interval. Once connected they can just stay connected.
- Eliminate fake connections designed to just reduce the usability of the server
- Make it so a delegate can hide and deliver their block signature through any random node on the network
- etc. etc. etc.
"someone" is difficult to identify. There could be an ISP IP with lots of connections. However a filter can be easily applied to limit the amount of connections an IP can create per hour.
"Eliminate fake connections designed to just reduce the usability of the server" - If you explain how to identify these it will be great.
"Make it so a delegate can hide and deliver their block signature through any random node on the network" - I've described something like that here:https://bitsharestalk.org/index.php?topic=5249.0 (https://bitsharestalk.org/index.php?topic=5249.0)
Basically I don't think a delegate should share his IP. Anyone could try to exploit this and there is no way of finding out who is "evil".
-
The way you solve this is by sending a challenge. They connect you give them a challenge to solve a quick hash or something, and if they don't respond within certain time - drop them.
Once connected they don't need to be challenged.
The more they connect the harder the challenge you give them. In fact you could increase the challenge based on how many connection slots you have left. So it becomes prohibitively expensive for them to connect to you as an attack.
But if someone really needs the connection they could spend some time solving a challenge.
-
You can already configure a node to not broadcast its peers. This would allow a delegate to connect to it without revealing who the delegate was.
Delegates can run behind a NAT rather than on the public internet. In this way they only make outgoing connections.
-
I have run into similar issues. I reboot regularly to prevent it. ...
My delegate performance improved as well with a reboot. Think I will make it a regular practice based on this feedback.
-
I rebooted last night and now my delegate is missing blocks. 9 blocks in the last 14 hours. I've missed a total of 15 and 9 of them came after I rebooted. I unlocked wallet after but I did forget to set node parameters. I realized this when I woke up 5 hours ago and saw I missed 7 blocks and I only had 8 connections. So I set the parameters and still since then have missed 2 more and only 21 connections. I find it odd since I went days without missing a block or rebooting since the 2.3 release.