http://www.vnbitcoin.org/litecoincalculator
http://www.vnbitcoin.org/bitcoincalculator
Ha ha ha ugh
Topic: bitcoin-qt won't shutdown? (Read 4295 times)
It will soon
http://www.vnbitcoin.org/litecoincalculator
http://www.vnbitcoin.org/bitcoincalculator
Ha ha ha ugh
http://www.vnbitcoin.org/litecoincalculator
http://www.vnbitcoin.org/bitcoincalculator
Ha ha ha ugh
Lol, after reinstalling and all of that, it still won't shutdown correctly but now I can't send.. I get an error about creating new addresses when I attempt to..
trying to reindex to see if that will correct it.. err... just after that started it spat out an error about opening the wallet.dat.. I'll figure it out eventually and send it off to another wallet.. is there any chance bitcoin will go back up to previous levels?.. might not be worth it if not.. Thanks again..
trying to reindex to see if that will correct it.. err... just after that started it spat out an error about opening the wallet.dat.. I'll figure it out eventually and send it off to another wallet.. is there any chance bitcoin will go back up to previous levels?.. might not be worth it if not.. Thanks again..
It sounds like your issue may be with your wallet.dat, and not with the client itself. Try starting bitcoind with the "-salvgewallet" paramete (back up your wallet again first, especially if you haven't done so already!) and see if it helps. If not, try renaming wallet.dat to "wallet.dat.old" (with Bitcoin-Qt closed) and see if it responds properly with a clean wallet (if the client can't find a wallet, it will automatically generate one, hence the rename).
Just shut it down or control alt delete and force shut down, then restart the wallet.
Lol, after reinstalling and all of that, it still won't shutdown correctly but now I can't send.. I get an error about creating new addresses when I attempt to..
trying to reindex to see if that will correct it.. err... just after that started it spat out an error about opening the wallet.dat.. I'll figure it out eventually and send it off to another wallet.. is there any chance bitcoin will go back up to previous levels?.. might not be worth it if not.. Thanks again..
trying to reindex to see if that will correct it.. err... just after that started it spat out an error about opening the wallet.dat.. I'll figure it out eventually and send it off to another wallet.. is there any chance bitcoin will go back up to previous levels?.. might not be worth it if not.. Thanks again..
Does the main window of the application not close when the popup dialog appears? On my system, the main window closes before the popup (though the entire process takes about a second in total).
From your log, it looks like it's partially shutting down, but not closing completely (some threads are exiting, but not all). The last few lines of my debug.log after shutting down Bitcoin-Qt look like this:
My best guess is that something got corrupted and is preventing it from shutting down cleanly. If you haven't tried it yet, reinstalling the client will probably fix it, otherwise deleting everything it the datadir except your wallet.dat and the "blocks" directory might help (if you have a custom config file, check to make sure it's correct rather than deleting it). You may need to start Bitcoin-Qt with the "-reindex" parameter to rebuild the chainstate afterward, though it will likely do so automatically (it won't need to redownload anything if you leave the "blocks" folder there, but it may take several hours to finish processing the blockchain).
From your log, it looks like it's partially shutting down, but not closing completely (some threads are exiting, but not all). The last few lines of my debug.log after shutting down Bitcoin-Qt look like this:
Code:
2014-10-27 02:24:59 Requesting shutdown
2014-10-27 02:24:59 Running Shutdown in thread
2014-10-27 02:24:59 opencon thread interrupt
2014-10-27 02:24:59 addcon thread interrupt
2014-10-27 02:24:59 dumpaddr thread stop
2014-10-27 02:24:59 msghand thread interrupt
2014-10-27 02:24:59 net thread interrupt
2014-10-27 02:24:59 Shutdown : In progress...
2014-10-27 02:24:59 RPCAcceptHandler: Error: The I/O operation has been aborted because of either a thread exit or an application request
2014-10-27 02:25:00 StopNode()
2014-10-27 02:25:03 Shutdown : done
2014-10-27 02:25:03 Shutdown finished
2014-10-27 02:25:03 Shutdown result: 1
2014-10-27 02:25:03 Stopping thread
2014-10-27 02:25:03 Stopped thread
2014-10-27 02:24:59 Running Shutdown in thread
2014-10-27 02:24:59 opencon thread interrupt
2014-10-27 02:24:59 addcon thread interrupt
2014-10-27 02:24:59 dumpaddr thread stop
2014-10-27 02:24:59 msghand thread interrupt
2014-10-27 02:24:59 net thread interrupt
2014-10-27 02:24:59 Shutdown : In progress...
2014-10-27 02:24:59 RPCAcceptHandler: Error: The I/O operation has been aborted because of either a thread exit or an application request
2014-10-27 02:25:00 StopNode()
2014-10-27 02:25:03 Shutdown : done
2014-10-27 02:25:03 Shutdown finished
2014-10-27 02:25:03 Shutdown result: 1
2014-10-27 02:25:03 Stopping thread
2014-10-27 02:25:03 Stopped thread
My best guess is that something got corrupted and is preventing it from shutting down cleanly. If you haven't tried it yet, reinstalling the client will probably fix it, otherwise deleting everything it the datadir except your wallet.dat and the "blocks" directory might help (if you have a custom config file, check to make sure it's correct rather than deleting it). You may need to start Bitcoin-Qt with the "-reindex" parameter to rebuild the chainstate afterward, though it will likely do so automatically (it won't need to redownload anything if you leave the "blocks" folder there, but it may take several hours to finish processing the blockchain).
thanks for your reply. It happens every time I open it.. I have started using the stand alone version of 0.9.3-win bitcoin-qt.exe.. I have left it to do its thing for probably well over an hour before with no appearance that it will actually shut down on its own..
after selecting File > Exit, I get the pop-up window, warning me not to shut down the computer until the popup window closes.. these are the last few line's of the debug file, it seems as if something isn't getting the shutdown request, I haven't read up on the newer code tech since the 0.9 wallets came out.. it's probably been about 6 or 7 months since I've really read up or kept up with the scene here...
this is the last bit of the debug log.. I didn't have it open very long but it just acts like it's continuing to do all of the network related stuff.. traffic window still show's active data and all of that and the main window of the wallet states that no wallet is loaded, attempting to Exit from file > exit makes it non responsive.. I don't think I have had but probably 1 clean close since 0.9.1.. and that was probably the first time I had it open.
2014-10-27 00:12:22 ext-ip thread exit
2014-10-27 00:12:27 No valid UPnP IGDs found
2014-10-27 00:12:27 upnp thread exit
2014-10-27 00:12:28 receive version message: /Satoshi:0.9.3/: version 70002, blocks=327130, us=98.214.82.33:49380, them=94.112.32.188:8333, peer=94.112.32.188:8333
2014-10-27 00:12:28 Added time data, samples 3, offset +44 (+0 minutes)
2014-10-27 00:12:32 P2P peers available. Skipped DNS seeding.
2014-10-27 00:12:32 dnsseed thread exit
2014-10-27 00:12:34 receive version message: /Satoshi:0.9.0/: version 70002, blocks=327130, us=98.214.82.33:49382, them=76.174.2.118:8333, peer=76.174.2.118:8333
2014-10-27 00:12:34 Added time data, samples 4, offset +55 (+0 minutes)
2014-10-27 00:12:41 receive version message: /Satoshi:0.8.6/: version 70001, blocks=327130, us=98.214.82.33:49384, them=176.103.112.7:8333, peer=176.103.112.7:8333
2014-10-27 00:12:41 Added time data, samples 5, offset +77 (+1 minutes)
2014-10-27 00:12:41 nTimeOffset = +55 (+0 minutes)
2014-10-27 00:12:47 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49387, them=61.10.127.97:8333, peer=61.10.127.97:8333
2014-10-27 00:12:47 Added time data, samples 6, offset +54 (+0 minutes)
2014-10-27 00:12:59 receive version message: /Satoshi:0.9.3/: version 70002, blocks=327130, us=98.214.82.33:49390, them=193.109.68.62:8333, peer=193.109.68.62:8333
2014-10-27 00:12:59 Added time data, samples 7, offset +53 (+0 minutes)
2014-10-27 00:12:59 nTimeOffset = +54 (+0 minutes)
2014-10-27 00:12:59 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49391, them=188.134.79.203:8333, peer=188.134.79.203:8333
2014-10-27 00:12:59 Added time data, samples 8, offset +56 (+0 minutes)
2014-10-27 00:13:22 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49396, them=24.63.153.124:8333, peer=24.63.153.124:8333
2014-10-27 00:13:22 Added time data, samples 9, offset +55 (+0 minutes)
2014-10-27 00:13:22 nTimeOffset = +55 (+0 minutes)
2014-10-27 00:14:36 Requesting shutdown
2014-10-27 00:14:56 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2014-10-27 00:15:11 ResendWalletTransactions()
2014-10-27 00:15:35 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49404, them=74.115.75.131:8333, peer=74.115.75.131:8333
2014-10-27 00:15:35 Added time data, samples 10, offset +51 (+0 minutes)
2014-10-27 00:16:47 UpdateTip: new best=0000000000000000097c3ed1551f808bbae8081507530ebf7958a4a9ce50d0fc height=327131 log2_work=81.234063 tx=49820780 date=2014-10-27 00:17:01 progress=1.000000
2014-10-27 00:16:47 ProcessBlock: ACCEPTED
Again, thanks for any help you can give on the issue..
after selecting File > Exit, I get the pop-up window, warning me not to shut down the computer until the popup window closes.. these are the last few line's of the debug file, it seems as if something isn't getting the shutdown request, I haven't read up on the newer code tech since the 0.9 wallets came out.. it's probably been about 6 or 7 months since I've really read up or kept up with the scene here...
this is the last bit of the debug log.. I didn't have it open very long but it just acts like it's continuing to do all of the network related stuff.. traffic window still show's active data and all of that and the main window of the wallet states that no wallet is loaded, attempting to Exit from file > exit makes it non responsive.. I don't think I have had but probably 1 clean close since 0.9.1.. and that was probably the first time I had it open.
2014-10-27 00:12:22 ext-ip thread exit
2014-10-27 00:12:27 No valid UPnP IGDs found
2014-10-27 00:12:27 upnp thread exit
2014-10-27 00:12:28 receive version message: /Satoshi:0.9.3/: version 70002, blocks=327130, us=98.214.82.33:49380, them=94.112.32.188:8333, peer=94.112.32.188:8333
2014-10-27 00:12:28 Added time data, samples 3, offset +44 (+0 minutes)
2014-10-27 00:12:32 P2P peers available. Skipped DNS seeding.
2014-10-27 00:12:32 dnsseed thread exit
2014-10-27 00:12:34 receive version message: /Satoshi:0.9.0/: version 70002, blocks=327130, us=98.214.82.33:49382, them=76.174.2.118:8333, peer=76.174.2.118:8333
2014-10-27 00:12:34 Added time data, samples 4, offset +55 (+0 minutes)
2014-10-27 00:12:41 receive version message: /Satoshi:0.8.6/: version 70001, blocks=327130, us=98.214.82.33:49384, them=176.103.112.7:8333, peer=176.103.112.7:8333
2014-10-27 00:12:41 Added time data, samples 5, offset +77 (+1 minutes)
2014-10-27 00:12:41 nTimeOffset = +55 (+0 minutes)
2014-10-27 00:12:47 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49387, them=61.10.127.97:8333, peer=61.10.127.97:8333
2014-10-27 00:12:47 Added time data, samples 6, offset +54 (+0 minutes)
2014-10-27 00:12:59 receive version message: /Satoshi:0.9.3/: version 70002, blocks=327130, us=98.214.82.33:49390, them=193.109.68.62:8333, peer=193.109.68.62:8333
2014-10-27 00:12:59 Added time data, samples 7, offset +53 (+0 minutes)
2014-10-27 00:12:59 nTimeOffset = +54 (+0 minutes)
2014-10-27 00:12:59 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49391, them=188.134.79.203:8333, peer=188.134.79.203:8333
2014-10-27 00:12:59 Added time data, samples 8, offset +56 (+0 minutes)
2014-10-27 00:13:22 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49396, them=24.63.153.124:8333, peer=24.63.153.124:8333
2014-10-27 00:13:22 Added time data, samples 9, offset +55 (+0 minutes)
2014-10-27 00:13:22 nTimeOffset = +55 (+0 minutes)
2014-10-27 00:14:36 Requesting shutdown
2014-10-27 00:14:56 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2014-10-27 00:15:11 ResendWalletTransactions()
2014-10-27 00:15:35 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=327130, us=98.214.82.33:49404, them=74.115.75.131:8333, peer=74.115.75.131:8333
2014-10-27 00:15:35 Added time data, samples 10, offset +51 (+0 minutes)
2014-10-27 00:16:47 UpdateTip: new best=0000000000000000097c3ed1551f808bbae8081507530ebf7958a4a9ce50d0fc height=327131 log2_work=81.234063 tx=49820780 date=2014-10-27 00:17:01 progress=1.000000
2014-10-27 00:16:47 ProcessBlock: ACCEPTED
Again, thanks for any help you can give on the issue..
It works perfectly fine for me, and only takes a few seconds (though my computer is extremely fast). If giving it more time doesn't work, try backing up your datadir and then uninstalling and reinstalling Bitcoin-Qt.
Also, can you post the last few (~20) lines of your debug.log the next time it gets stuck? That may be helpful for troubleshooting.
Also, can you post the last few (~20) lines of your debug.log the next time it gets stuck? That may be helpful for troubleshooting.
no one?.. 
I appreciate the replies, when I close out the newest bitcoin wallet I get the popup saying not to shutdown until the window disappears.. it never does disappear, and I have to force close the client.. after the popup window though, it will say no wallet loaded, so I guess the most I should have to worry about is reloading the chain.. any tips with the further info perhaps?.. It's strange that no one else seems to experience this..
btw.. I am running on a quad core with 8gb ram and an ssd.. (blockchain and application data are on a separate hdd though)
edit* also, it is the 0.9.3 bitcoin-qt.exe wallet.. same happened with 0.9.1..
btw.. I am running on a quad core with 8gb ram and an ssd.. (blockchain and application data are on a separate hdd though)
edit* also, it is the 0.9.3 bitcoin-qt.exe wallet.. same happened with 0.9.1..
Maybe due to hardware performance.
You can always try a lightweight wallet.
MultiBit and MultiDoge is the way to go
You can always try a lightweight wallet.
MultiBit and MultiDoge is the way to go
I think it means it is set to minimize on exit so the node is still running. You can change that setting if that is what you want but each time you start the blockchains downloads will have to catch up.
I don't know what you exactly mean...
Why don't you try to download the newest releases of that wallets?
however you should ask that details in that coins threads
Why don't you try to download the newest releases of that wallets?
however you should ask that details in that coins threads
my *coin-qt for doge and bit coins never exit and I have to force close them, I haven't seen anything while searching the subject, is there a trick to it?.. or?.. Thanks in advance.. 
Jump to: