problem with RPC console in 0.7.1 (re-post from forum thread) #1960

1. 
   Diapolo commented at 9:59 am on October 25, 2012: none

   https://bitcointalk.org/index.php?topic=117874.msg1273313#msg1273313

   “I’m test-running 0.7.1rc1 (self-compiled with libdb5.1 and without upnp on linux) and found it drop dead already twice after sending it commands in the debug-console.

   This (2nd) time it was the “move” command. I instantly saw the mining-activity stop (cpu-meter in the panel), and the move command didn’t return a response. When it happened, I could still type more commands in the console (though without getting an answer), but meanwhile also the debug-widget has dropped dead and doesn’t redraw anymore. I’ll leave it stuck for a while and will look back in this thread for debugging instructions before killing&restarting it…

   PS: gdb says, it’s stuck in pthreads_cond_wait in boost::unique_lock in AddressTableModel::labelForAddress(QString) in TransactionTableModel::lookupAddress(string,bool)”

2. 
   laanwj commented at 11:14 am on October 25, 2012: member

   Sounds like a deadlock…
3. 
   94m3k1n9 commented at 8:42 pm on October 29, 2012: contributor

   I’m using Bitcoin version v0.7.1-95-gc13f5db-beta.

   I’ve got the same issue here, after using move at least the RPC server is broken. as i don’t mine with the client i can’t tell about other stuff breaking, though tail -f -n 0 debug.log still shows it connecting to peers:

    010/29/12 20:38:45 received: inv (37 bytes)
    110/29/12 20:38:45   got inventory: tx fd684056c7c7debb3ff1  have
    210/29/12 20:38:45 connection timeout
    310/29/12 20:38:45 ThreadRPCServer method=move
    410/29/12 20:38:46 trying connection 82.177.152.52:8333 lastseen=4.2hrs
    510/29/12 20:38:51 connection timeout
    610/29/12 20:38:51 trying connection 78.72.91.171:8333 lastseen=6.8hrs
    710/29/12 20:38:56 connection timeout
    810/29/12 20:38:57 trying connection 69.115.20.67:8333 lastseen=4.8hrs
    910/29/12 20:38:57 connected 69.115.20.67:8333
   1010/29/12 20:38:57 send version message: version 60002, blocks=205609, us=88.198.39.134:8333, them=69.115.20.67:8333, peer=69.115.20.67:8333
   1110/29/12 20:38:57 sending: version (101 bytes)
   1210/29/12 20:38:57 trying connection 98.218.70.45:8333 lastseen=8.0hrs
   1310/29/12 20:39:02 connection timeout
   

4. 
   Nicolai-s commented at 6:35 pm on November 9, 2012: none

   Same problem here. RPC command “move” locks the client. Tested on Windows 7 x64 & Linux 2.6.32-5-amd64, BitCoin v0.7.1 (64 bit)
5. 
   Diapolo commented at 11:28 am on November 10, 2012: none

   @laanwj You are way more skilled to debug this, so as this is now high priority you can perhaps take a look at it?
6. 
   sipa commented at 11:35 pm on November 13, 2012: member

   Fixed by #2009.
7. 
   Diapolo commented at 12:41 pm on November 17, 2012: none

   @94m3k1n9 Can you verify current master is fixing your problem with move?
8. 
   94m3k1n9 commented at 1:02 pm on November 17, 2012: contributor

   Yes, moving works for me after applying this patch.
9. 
   Diapolo commented at 2:06 pm on November 17, 2012: none

   Fixed!
10. Diapolo closed this on Nov 17, 2012

    ---

11. MarcoFalke locked this on Sep 8, 2021

Contributors
Diapolo laanwj 94m3k1n9 Nicolai-s sipa

Labels
Bug Wallet