Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Client keeps crashing  (Read 2585 times)

0 Members and 1 Guest are viewing this topic.

Offline bobb

  • Full Member
  • ***
  • Posts: 67
    • View Profile
Client keeps crashing
« on: November 10, 2013, 11:48:53 PM »

hey,

after updating the client (git pull from github) and recompiling the client, it quickly crashes.
I already tried to re-download the whole blockchain and started from scratch (just kept the wallet.dat), but it still doesn't work (regardless if I mine or not)

(running on linux 64bit, ubuntu 12.04, reproducible on various machines)

any ideas? thanks in advance.

« Last Edit: November 10, 2013, 11:59:46 PM by bobb »

Offline victor

  • Jr. Member
  • **
  • Posts: 34
    • View Profile
Re: client keeps crashing
« Reply #1 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.

Offline FreeTrade

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 700
    • View Profile
Re: client keeps crashing
« Reply #2 on: November 11, 2013, 03:31:07 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?
“People should be more sophisticated? How are you gonna get that done?” - Jerry Seinfeld reply to Bill Maher

Offline victor

  • Jr. Member
  • **
  • Posts: 34
    • View Profile
Re: client keeps crashing
« Reply #3 on: November 11, 2013, 04:18:01 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...

Offline FreeTrade

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 700
    • View Profile
Re: client keeps crashing
« Reply #4 on: November 11, 2013, 05:05:57 AM »
I am not sure if it is relevant, since I only build the CLI (bitcoind) without QT...

Ok - probably not relevant then. What do you see at the bottom of the log, immediately after the crash?
“People should be more sophisticated? How are you gonna get that done?” - Jerry Seinfeld reply to Bill Maher

Offline bobb

  • Full Member
  • ***
  • Posts: 67
    • View Profile
Re: Client keeps crashing
« Reply #5 on: November 11, 2013, 07:03:35 AM »
This is exactly what happens right before the crash on all systems after the update:

Error: System error: CDB() : can't open database file wallet.dat, error -30973
*** System error: CDB() : can't open database file wallet.dat, error -30973
Error: System error: CDB() : can't open database file wallet.dat, error -30973
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
dumpaddr thread stop
msghand thread interrupt
addcon thread interrupt
Flush(false)
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(false) ended               0ms
StopNode()
net thread interrupt
Flushed 3978 addresses to peers.dat  44ms
terminate called after throwing an instance of 'std::runtime_error'
  what():  CDB() : can't open database file wallet.dat, error -30973

Offline victor

  • Jr. Member
  • **
  • Posts: 34
    • View Profile
Re: Client keeps crashing
« Reply #6 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)

Offline dzhan

  • Newbie
  • *
  • Posts: 7
    • View Profile
Re: Client keeps crashing
« Reply #7 on: November 11, 2013, 08:30:11 AM »
I have exactly the same problem.

Offline bobb

  • Full Member
  • ***
  • Posts: 67
    • View Profile
Re: Client keeps crashing
« Reply #8 on: November 11, 2013, 08:37:00 AM »
I think  we are dealing with two related problems here.

When starting from scratch (without any former wallet.dat files) I experience the same behaviour victor already described.
It crashes and the last lines in the log file look like these:

Code: [Select]
getblocks stopping at 12105 00001fa9bc685efadcbdc3c65603e817d8e02c846b24f47660cd56368d7e71d1
getblocks 12089 to 00001d392ce5eaec0320429b14a66c25cbd574778f9d95fa8e0cba0cc8f502c1 limit 500
getblocks stopping at 12230 00001d392ce5eaec0320429b14a66c25cbd574778f9d95fa8e0cba0cc8f502c1

The even more concerning part is this that the client is not able to access the wallet files after these crashes.

Code: [Select]
Error: System error: CDB() : can't open database file wallet.dat, error -30973

Please note that the wallet issues are the same on a range of different machines.

Is there an official (64bit) linux build, that I can use to test?

It is kind of frustrating that there is no way to build a working linux client at the moment.
In combination with wallet error, this is kind of making me nervous right now.
I have a reasonable amount of coins in these wallets.

If I can help to track down/solve the problem, let me know.
Thanks in advance.

Offline bytemaster

Re: Client keeps crashing
« Reply #9 on: November 11, 2013, 08:55:29 AM »
This is the bug that forced me to take down my pool.   It kept crashing on me.

I have been spending the past several hours trying to track down this issue.

Have not seen the database corruption though.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

Re: Client keeps crashing
« Reply #10 on: November 11, 2013, 08:56:14 AM »
Caught this in GDB:
 0x00007ffff67581f7 in send () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00000000004cc37c in SocketSendData ([email protected]=0x7fffdc0048c0) at net.cpp:716
#2  0x00000000004d20bc in ThreadSocketHandler () at net.cpp:1031
#3  0x00000000004d306b in TraceThread<void (*)()> (name=0x5efc61 "net", func=0x4d1360 <ThreadSocketHandler()>) at util.h:591
#4  0x00007ffff7549242 in thread_proxy () from /usr/local/lib/libboost_thread.so.1.54.0
#5  0x00007ffff6750f8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007ffff5c5ce1d in clone () from /lib/x86_64-linux-gnu/libc.so.6
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline FreeTrade

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 700
    • View Profile
Re: Client keeps crashing
« Reply #11 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.
“People should be more sophisticated? How are you gonna get that done?” - Jerry Seinfeld reply to Bill Maher

Offline victor

  • Jr. Member
  • **
  • Posts: 34
    • View Profile
Re: Client keeps crashing
« Reply #12 on: November 11, 2013, 09:48:04 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?

Offline FreeTrade

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 700
    • View Profile
Re: Client keeps crashing
« Reply #13 on: November 11, 2013, 09:50:47 AM »
Are you guys seeing this in your log files much?

ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 60.247.75.39:3888 (0 -> 100) DISCONNECTING
disconnecting node 60.247.75.39:3888

I've got about 10 of these since the fork - it might be that these are not being handled correctly
“People should be more sophisticated? How are you gonna get that done?” - Jerry Seinfeld reply to Bill Maher

Offline Vizierx

  • Full Member
  • ***
  • Posts: 52
    • View Profile
Re: Client keeps crashing
« Reply #14 on: November 11, 2013, 09:52:31 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?
right you are - or do something like what to stop crush

 

Google+