|
Title: Accept failed with error number: 10038 during doInitialSyncOnLoad Post by: donut on March 30, 2023, 08:13:47 PM Started Armory today after a while. No changes have been made, local Bitcoin node is running as always.
Last time I ran this successfully was not too long ago, either - a month or two ago, tops. I think this may have something to do with those image files filling up the blockchain recently? Armory version 0.96.3.99-beta-1c7f3e91df Here is the log: Code: Log file opened at 16:01:23.000: C:\Coins\Armory/dbLog.txt Title: Re: Accept failed with error number: 10038 during doInitialSyncOnLoad Post by: goatpig on March 31, 2023, 06:49:48 AM You're using an old version of Armory, go get 0.96.5 (https://github.com/goatpig/BitcoinArmory/releases)
As for the specific error, likely something is using the port ArmoryDB is trying to listen on. Title: Re: Accept failed with error number: 10038 during doInitialSyncOnLoad Post by: donut on March 31, 2023, 08:26:49 PM Thanks for responding!
The reason I'm holding off on updating is because I don't want to re-do my offline laptop.. And IIRC the old version cannot sign the transactions created by newer versions unfortunately. Do you happen to remember which port ArmoryDB is listening on? Title: Re: Accept failed with error number: 10038 during doInitialSyncOnLoad Post by: goatpig on April 02, 2023, 07:43:30 AM Thanks for responding! The reason I'm holding off on updating is because I don't want to re-do my offline laptop.. And IIRC the old version cannot sign the transactions created by newer versions unfortunately. Do you happen to remember which port ArmoryDB is listening on? The tx signing message format was extended in 0.96 to support nested segwit scripts. This means, if you are trying to spend coins from a nested segwit script, Armory versions prior to 0.96 will not be able to sign the transaction. My recommendation is for you to update anyways, seeing your online version is already of the 0.96 family. Quote Do you happen to remember which port ArmoryDB is listening on? You are letting ArmoryQt automate your DB process, so it randomizes the port used. As you can see in your logs, this time around it was: Code: -INFO - 16:01:23.062: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 58804 10038 is a Windows socket error code. It happens in either of 2 cases: the client is trying to connect to this port but there is no service running behind it (meaning the server never started or crashed), or the server is trying to listen on this port, but some other process already bound it. |