-
Notifications
You must be signed in to change notification settings - Fork 621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Armory repeatedly losing and re-establishing connection with bitcoin-qt #30
Comments
One thing I haven't figured out too with the new multi-threaded stuff, is some kinds of errors in the code can cascade out of control. The reconnect/disconnect is a symptom of the these errors cascading (not the problem itself). I tried to detect and fix this condition, but it doesn't always work... Please post or email a log file so I can see what error triggered it... |
Here are the files. Thanks. On Fri, Nov 30, 2012 at 9:11 PM, etotheipi notifications@github.com wrote:
|
It seems that this was triggered immediately after finishing scanning. Was Bitcoin-Qt still in the middle of synchronizing? Was there a green checkmark? If not, please wait for Bitcoin-Qt to finish sync'ing before opening Armory. The first occurrence of an error happened during ReadBlkFileUpdate. I've seen this quite a bit, and I'm not sure what is causing it (unless Bitcoin-Qt isn't synchronized... that's will cause it). So, apparently it's taking 10+ seconds to do readBlkFileUpdate -- my own timing tests show that it usually takes 0.0004 seconds to do it... I'm not sure what would cause it to take 25,000 times longer... At least, a lot of issues users are having revolve around this (and it happens to my Win7 machine, too, when Armory has been running for a couple days). It sounds like I can clear up a lot by isolating and fixing this. Thanks for posting your log! |
Thanks for your efforts. To answer your question, bitcoin-qt was finished If it clarifies anything, the Armory client is exceptionally slow on my On Sat, Dec 1, 2012 at 10:23 AM, etotheipi notifications@github.com wrote:
|
The 2 GB of RAM is probably it. The blockchain indexing mechanism is too big to be used on systems with 2 GB of RAM now. The size is increasing so rapidly, that I need a purely-disk-based indexing system to keep it all under control. Satoshi-dice really did me in! (i.e. I thought I had a lot more time before keeping the index in RAM was a problem) I will be upgrading to a pure-disk-based indexing scheme... I'm just not there yet... |
hello I jsut had the same kind of error today... |
I'm having that exact problem right now... Actually the reconnection rate is accellerating, and right now seems to be disconnecting and reconnecting as fast as it can (several times per second)... |
FYI I upgraded my RAM and Armory has been working great now. |
I'm also getting this problem with 8g of RAM. I also can not send bitcoins. |
I seem to have a similar issue, but mine disconnects and reconnects about twice a second (as you can guess, this is crazy annoying / makes the program unusable). Of course, with the new state saving features, I can just restart it quickly and the program will work just fine for many many hours. Log file: https://gist.github.com/arjunyg/87527b0de938d667eede Oh by the way, I am running bitcoind separately, because I have 4GB of RAM and Armory freezes up (at least during the initial check, I'm still setting up for the first time on this computer -my 8GB computer used to have no trouble but that was when the blockchain was a reasonable amount smaller) because it overfills the RAM and then spills into swap space, rendering it useless. |
Mine was disconnecting and reconnecting hundreds of times per second. Running tail -f armorylog.txt would repeat this set of messages as fast as the xterm could keep up: 2013-11-30 23:48 (INFO) -- armoryengine.py:10489 - Connection initiated. Start handshake Updating python-twisted (11.1.0-1ubuntu2) to 12.1.0-1 2013-11-30 23:51 (INFO) -- armoryengine.py:10489 - Connection initiated. Start handshake |
af2da22 Add new tests for invalid Bech32 strings (Clark Moody) Pull request description: Similar updates in the vein of etotheipi#27, etotheipi#29, etotheipi#30, etotheipi#31, etotheipi#32 Adds invalid Bech32 string test cases. Please note: Rust strings are UTF-8, so that the character literal `0xff` [turns into](https://codepoints.net/U+00FF) `0xc3bf` when accessed with the `bytes` function. Tree-SHA512: 73f85762fc22059acb9c4b382068997fb0341354f1de26ecb2d75ba3c57aee80609fd2839967541c9a9f96ccdc04137140174396f5acfe62a6511fd9f18e703e
a4e672d Update Haskell tests (Pieter Wuille) Pull request description: Tree-SHA512: 7da982c437be4f424a431a758a478c1c59f12a8369fe44e9fe8759bc227b2090b0a63ddead7c819813b231a26da1be794d68fc3f2dcc8a41d778e7a76de9e4a2
I left Armory on for about 24 hours, and when I came back I see a notification every 5-10 seconds saying Armory has lost it's connection to Bitcoin-qt, followed by a bubble saying it has reconnected. These messages repeated popping up until I shut down Armory.
I took a screenshot and grabbed the Armory logs. Is there a way to attach them?
The message in the notification bubble is:
Disconnected
Connection to Bitcoin-QT client lost!
Armory cannot send or receive bitcoins until connection is re-established.
Armory version 0.84.5 on Ubuntu 12.04.1 64bit
The text was updated successfully, but these errors were encountered: