Show Posts
|
Pages: [1]
|
Thanks, I did nothing just waited and it appeared. I'm guessing it was just slow to process due to low fee? And then the error message generated by Armory was inaccurate? Either way, thanks for responding. I'm sure you are tired of answering the same questions for us noobs all day.
|
|
|
I'm experiencing the same problem but the server=1 solution did not work for me.
|
|
|
Here's the last few lines of the log file:
INFO - 09:23:55.984: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:857) scanned block #679912 -INFO - 09:40:14.531: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2099) sent inv packet -INFO - 09:40:18.640: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2118) got getData packet -INFO - 09:40:18.640: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2148) grabbing tx from node -ERROR - 09:40:28.640: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2160) tx broadcast timed out (get) -INFO - 09:54:26.484: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:857) scanned block #679913 -INFO - 10:01:13.250: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:857) scanned block #679914 -INFO - 10:08:23.187: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2099) sent inv packet -INFO - 10:08:27.296: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2118) got getData packet -INFO - 10:08:27.296: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2148) grabbing tx from node -ERROR - 10:08:37.312: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:2160) tx broadcast timed out (get)
|
|
|
I'm using Bitcoin core v0.21.0 and Armory 0.96.5-beta-8730390989
I'm getting the error message: "The transaction you attempted to broadcast has timed out" and a follow up message about RPC being disabled so armory is unable to use rpc to gather more information about why the transaction timed out
I have created the bitcoin.conf file and added "server=1"
My receiving wallet (on another computer) shows the transaction as pending but has been stuck for 24 hours with no confirmations or any other change. The transaction was sent with the default fee of 50sats per byte. I'm confused how my receiving wallet is getting notice of the pending transaction when armory is claiming that the transaction timed out.
I'm not a programmer or particularly tech savvy so this is all pretty confusing/frustrating so far. Any help is greatly appreciated. I have log file available but don't know how to attach it here.
|
|
|
|