Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - victor

Pages: 1 2 [3]
31
BitShares PTS / Re: Client keeps crashing
« on: November 11, 2013, 09:48:04 am »
Quote from: FreeTrade on November 11, 2013, 09:40:33 am
So I think we have two colliding networks - some bug is causing the command line version to be affected, but not the QT client.

As a stop-gap measure we could compile a list of misbehaving IPs and block them at a higher level.

I think we should make the new client more robust instead. Some users have not upgraded to the latest client, and when a new client is communicating with the old ones is just crashes. It is hard to block all these IPs; and what if they upgrade to the latest client?

32
BitShares PTS / Re: Client keeps crashing
« on: November 11, 2013, 07:25:29 am »
Crash log 1:

Code: [Select]
getblocks 12094 to 000013f13f50db53a53d758bc5806aff4208856cfb8f0b1c13ddeb985a821558 limit 500
  getblocks stopping at 12103 000013f13f50db53a53d758bc5806aff4208856cfb8f0b1c13ddeb985a821558
getblocks 12094 to 00001d75ecbde6b0d68856923465284a33532130a0b0c3d7f633b2cfd8391543 limit 500
  getblocks stopping at 12107 00001d75ecbde6b0d68856923465284a33532130a0b0c3d7f633b2cfd8391543
getblocks 12094 to 00001026c23e93e093b00fb5b2fdb3505ac6964a9e17834161493a9d53df2234 limit 500
  getblocks stopping at 12140 00001026c23e93e093b00fb5b2fdb3505ac6964a9e17834161493a9d53df2234
getblocks 12094 to 0000096bd5afd9bbdea554e820271bb596863c7d9123ccd89726c41d194601cb limit 500
  getblocks stopping at 12144 0000096bd5afd9bbdea554e820271bb596863c7d9123ccd89726c41d194601cb
getblocks 12094 to 00000debd784366414f0e74b710a5970634809a2d982206306960ca7829a3e2d limit 500
  getblocks stopping at 12146 00000debd784366414f0e74b710a5970634809a2d982206306960ca7829a3e2d
getblocks 12094 to 00001b2926f366440b32d5eae8c22f0b8ae215964f2c03b2e9b339c3dc2bb3f5 limit 500
  getblocks stopping at 12154 00001b2926f366440b32d5eae8c22f0b8ae215964f2c03b2e9b339c3dc2bb3f5
received getdata (59 invsz)
getblocks 12094 to 000015998ef76ec5b326e869972093bd325d39e5be40de22c147b3653834e3f5 limit 500
  getblocks stopping at 12097 000015998ef76ec5b326e869972093bd325d39e5be40de22c147b3653834e3f5
getblocks 12094 to 000015998ef76ec5b326e869972093bd325d39e5be40de22c147b3653834e3f5 limit 500
  getblocks stopping at 12097 000015998ef76ec5b326e869972093bd325d39e5be40de22c147b3653834e3f5
getblocks 12094 to 00001b454a10ada02429aa55aa552cd1bae1fb2b195acf0bca771fbb8a2f3e72 limit 500
  getblocks stopping at 12100 00001b454a10ada02429aa55aa552cd1bae1fb2b195acf0bca771fbb8a2f3e72
getblocks 12094 to 00001026c23e93e093b00fb5b2fdb3505ac6964a9e17834161493a9d53df2234 limit 500
  getblocks stopping at 12140 00001026c23e93e093b00fb5b2fdb3505ac6964a9e17834161493a9d53df2234
getblocks 12094 to 00000debd784366414f0e74b710a5970634809a2d982206306960ca7829a3e2d limit 500
  getblocks stopping at 12146 00000debd784366414f0e74b710a5970634809a2d982206306960ca7829a3e2d
received getdata (37 invsz)
getblocks 12094 to 000004c63a1ebb204c84fabf27cac560f0c1b164abf04c43bf9708fd3a745b53 limit 500
  getblocks stopping at 12101 000004c63a1ebb204c84fabf27cac560f0c1b164abf04c43bf9708fd3a745b53
getblocks 12094 to 0000028729900e6ad655cad22e7be7c4a940f5915a218a11cc7b696efb71e00c limit 500
  getblocks stopping at 12123 0000028729900e6ad655cad22e7be7c4a940f5915a218a11cc7b696efb71e00c
getblocks 12094 to 000004c7ab85ac74edca488399183448258990e81c747bb677b9abbf84520fe0 limit 500
  getblocks stopping at 12129 000004c7ab85ac74edca488399183448258990e81c747bb677b9abbf84520fe0
getblocks 12094 to 0000096bd5afd9bbdea554e820271bb596863c7d9123ccd89726c41d194601cb limit 500
  getblocks stopping at 12144 0000096bd5afd9bbdea554e820271bb596863c7d9123ccd89726c41d194601cb
received getdata (32 invsz)
socket recv error 104
disconnecting node 218.75.114.210:1072

Crash log 2:

Code: [Select]
connection timeout
trying connection 146.185.171.65:3888 lastseen=18.8hrs
connect() failed after select(): Connection refused
trying connection 54.221.104.112:3888 lastseen=132.2hrs
connection timeout
trying connection 71.82.34.194:3888 lastseen=13.8hrs
getblocks 12089 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 12089 to 000010bb273ac0c42e2c9c30733b1a0ae9f78211bc06ce8b82bdeb2ca176956a limit 500
  getblocks stopping at 12106 000010bb273ac0c42e2c9c30733b1a0ae9f78211bc06ce8b82bdeb2ca176956a
received getdata (50 invsz)

33
BitShares PTS / Re: client keeps crashing
« on: November 11, 2013, 04:18:01 am »
Quote from: FreeTrade on November 11, 2013, 03:31:07 am
Quote from: victor on November 11, 2013, 12:02:40 am
I think the diff adjustment should be harmless, however, commit 776832f419649211cb7b173ffb437e7d2af68b8b could cause this problem since there are some big changes.

Hi Victor,

Can you try commenting out this line -
emit miningChanged(dHashesPerSec, nThreads);

in src/qt/clientmodel.cpp (line 87)

and let us know if that helps?

I am not sure if it is relevant, since I only build the CLI (bitcoind) without QT...

34
BitShares PTS / Re: client keeps crashing
« on: November 11, 2013, 12:02:40 am »
I have the same issue on Ubuntu 13.10 64bit.

The old client worked fine, but the new one with new diff adjustment just crashes after a few minutes, with or without miner enabled. It is not even possible to do normal transactions.

I think the diff adjustment should be harmless, however, commit 776832f419649211cb7b173ffb437e7d2af68b8b could cause this problem since there are some big changes.

Pages: 1 2 [3]

Page created in 0.024 seconds with 22 queries.