Hi CoolWave, i did fill it as soon as i sent through that post, hope you can accelerate them, if you cant, id be happy if you could at least squeeze in the first one for me. thank you so much.

Hi
Will you be able to help me out with these 2?
53dc5c3317baaf35b50e6c60335136565e6aa1867cf808201c36ee7c68298d1f
10bd491a8011da5483ed20ece2b10f491caf0cd1fbb527d93a7e027dddb42929

Id really appreciate it.

PS: I tried to use your site but it says invalid query.
Il also post on google form if you want.

Hi friend, please could you accelerate this tx: 9be4da6331d28f3a7e308982aae4f47de2c3e7a63775e45774b29cf07a108257
I paid the required fee but still unconfirmed.   Would appreciate friend! thank you!

Hi Coolwave friend.

Please could you accelerate these transactions?

29534946d2829622604599bf8af1dcb6f34fc836a489eeb7016fc0c62fd3e510
1d0083b9b92aad33f63e7a2e8e46513fe1f2e0d6cf0767479ffa2398ac60bb71

Thank you so much friend    You are the hero!

Hi friend

Would really appreciate it if you could accelerate these unconfirmed transactions.  They have been like this for many days now

1d0083b9b92aad33f63e7a2e8e46513fe1f2e0d6cf0767479ffa2398ac60bb71
23be0b67cceeb63a5c2b369cc569c3c9793977cdb502cf39ece7cc82f0bfa42f

thank you so much

Stop forking all the time! dammit. You're starting to become like Charlie Sheen! All you forkers just wanna "win"

Im using Intel Core i7 CPU 920.

Can you tell me what do you think the issue might be when the new version of armory is preventing wallets from being opened that were created with 95.1 like i described above?  Is it a bug?

I also noticed something weird (which i dont know if this might be the cause): between the two gcc armory versions, the 4.7 one was the one that ive been trying to get to work with the wallet files (which means it opens up).
However when checking why armory_0.96-gcc5.4_amd64.deb wasnt opening at all. Everytime i tried opening it, i saw in syslog this error line:

traps: python2[29095] trap invalid opcode ip:7f5a01402ec0 sp:7ffeddbf0808 error:0 in _CppBlockUtils.so[7f5a00f4d000+6a9000]

And when i do gcc -v in terminal to see my version of gcc, it prints that i have the latest 5.4:
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)

 

Ok, well i created a test wallet in 95.1 and upgraded to 96.0, i open armory with test wallet files inside folder already and it will create these watch only wallets but as soon as the GUI begins to start up, it crashes.

I especially tried this with offline armory, to import digital backup or even from paper backup and as soon as i import, it crashes, i open offline armory again and the wallet didnt import, yet its still in the folder.
I checked the armorylog.txt file and it says this before the crash:
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2172 -    Wallet (35Qpf31Yj):   "Test                            "   (Encrypted)
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes

crashes just after that.

Im not sure why this is happening even with brand new wallets.  The other thing is that i tried doing a test backup on both wallets and it crashes the gui on that too.

@goatpig
I tried doing what you said above, even in offline mode i tried to import but the gui crashes and theres nothing written in the logs about that issue.
I even deleted the zeroconf-lock files.

when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

I dont know why these files are auto created?

I uninstalled armory 96.0 and reinstalled the old version, seeing everything sync up again, the entry that was unconfirmed is no longer there anymore which is a good thing.
The bad thing is that it doesnt seem like wallet importing works in 96.0.

Im going to recreate a new empty wallet from the old armory and try import that into the new armory and il get back to you on that.

So i sorted that out by removing armory_0.96-gcc5.4_amd64.deb and installing armory_0.96-gcc4.7_amd64.deb

Then when i start armory i get:

(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
-ERROR - 1494239616: (WalletManager.cpp:78) Failed to open wallet with error:
missing main wallet entry
Illegal instruction (core dumped)


I think this is because in version 95.1 i had an unconfirmed transaction because of a low fee given, a mistake i made.  I knew that clear all unconfirmed did not work in armory 95.1, so i upgraded now to run "clear all unconfirmed" but as soon as i open armory it throws that error about the entry.  Anything i can do to get this fixed @goatpig?
I also see the wallet being locked in the folder to "_wallet.lmdb-lock"

I tried removing the wallet or moving it in a temp dir, started up armory again and i see this error message now:

(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
Illegal instruction (core dumped)

After which i went back into .armory folder and deleted databases and settings to start from scratch.  Armory then opened with welcome message etc.

It started scanning and then during 68% it got stuck so i looked in .bitcoin/debug.log and saw this error:

-INFO  - 1494241552: (DatabaseBuilder.cpp:268) parsed block file #587
-INFO  - 1494241554: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 1494241554: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 1494241554: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

So i started up armory again and it is busy scanning now but stuck at preparing databases.. looked in .armory/dbLog.txt and it still scanning but its just not showing it in the GUI anymore.  So currently im waiting for this to finish

can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background.  please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction 

Ubuntu 16.04 with armory_0.96-gcc5.4_amd64.deb, after doing upgrade from 95.1 to 96, i start armory and it doesnt even start up, the icon would flash a few times and the logs wont even write anything.

When i start armory from terminal, i get this: Illegal instruction (core dumped)

Was i supposed to completely remove 95.1 ?

EddieRock i am having the EXACT same problem as you!! im currently on 95.1, did upgrading and clear unconfirmed work for you eventually?, did the grey entry disappear? ?

The problem got solved.  While armory was stuck at some percentage everytime (from deleting the DB completely from armory folder), what i did was, killed the armory process and ArmoryDB as well. Restarted it and it started syncing properly with bitcoind.

So the above problem only happens when deleting the database folder in armory folder and starting it from scratch, it will reach a certain percentage and freeze at scanning transaction history.

The other problem is that i cannot let armory open bitcoind itself, otherwise i get RPC username and password errors.  Currently i am running them separately.

I really hope that the newer version runs bitcoind on its own by using cookie like you mentioned in your posts.

Thanks

Hi goatpig,

I am having big problems with armory 95.1 on Ubuntu 64bit 16.04.
Firstly, running armory while it opens bitcoind itself, gives the errors that others have posted on here which is:
'No JSON object could be decoded' in the armorylog.txt
as well as constant errors in bitcoin debug.log file such as:
'ThreadRPCServer incorrect password attempt from 127.0.0.1:36132'

So i tried to run armory by itself after running bitcoind manually, it scans transaction history and freezes at 97% all the time.
I deleted the armory DB folder, and when restarting armory (while bitcoind is running), it will eventually freeze again at a different %, at a specific block everytime (as far as i can see in the dbLog.txt).
If i repeat this process again, and if i let it run, it would eventually finish, but the block it was stuck on will show at the bottom right hand corner of armory, the block it always freezes on.  So in other words, it is not up to date or does not communicate with bitcoind blocks.

Please help and tell me what i can do to solve this issue? should i revert back to armory 93.3?