Ninjastic
Search content
Sort by
Showing 7 of 7 results by m.fridge
Post
Topic
Board Armory
Re: Armory 0.95 is out
by
m.fridge
on 23/10/2016, 16:09:53 UTC
Hi,

thanks for finalizing the new release! I am keen to check it out Smiley

I get the following compilation error in Swig:
Code:
CppBlockUtils_wrap.cxx:3991:77: error: ‘type_name’ is not a member of ‘swig::traits’

Regards,
Michael
Post
Topic
Board Armory
Re: Starting preliminary 0.94 testing - "Headless fullnode"
by
m.fridge
on 18/01/2016, 15:20:49 UTC
They made Armory closed-source, which is why you don't find the latest tree on github anymore. There won't be any open releases. As far as I noticed, this step was done without any public communication.
Post
Topic
Board Armory
Re: Starting preliminary 0.94 testing - "Headless fullnode"
by
m.fridge
on 17/08/2015, 20:46:08 UTC
I did a rebuild and rescan and now end up with "std::bad_alloc". I thought that my harddrive might have problems and used a usb drive for the armory datadir, where I got the same error. Any ideas what's wrong here?

Code:
[New Thread 0xabe84b40 (LWP 24368)]
[Thread 0xabe84b40 (LWP 24368) exited]
[New Thread 0xabe84b40 (LWP 24369)]
[Thread 0xabe84b40 (LWP 24369) exited]
-INFO  - 1439844030: (BlockUtils.cpp:1691) Loading block data... file 0 offset 0
[New Thread 0xabe84b40 (LWP 24370)]
-INFO  - 1439844030: (BlockUtils.cpp:395) reading blocks from file 0
[Thread 0xabe84b40 (LWP 24370) exited]
-ERROR - 1439844030: (BDM_mainthread.cpp:430) BDM thread failed: std::bad_alloc

"std::bad_alloc" is shown as a popup. After okay-ing it, armory exits normally according to gdb.
Post
Topic
Board Armory
Re: Starting preliminary 0.94 testing - "Headless fullnode"
by
m.fridge
on 16/08/2015, 13:17:01 UTC
Quote from: goatpig on August 14, 2015, 11:17:33 PM
I fixed this issue in the last commit a couple days ago. Pull again and give it a spin.

The problem still exists with the latest version. Here is the log, where the crash seems to have another cause than before. I also got a popup saying "Cannot find block with hash".

Code:
-ERROR - 1439730764: (BlockWriteBatcher.cpp:711) error grabbing block 0|0 in file #0, offset: 8, with a size of 285 bytes
-ERROR - 1439730764: (BlockWriteBatcher.cpp:715) error: std::bad_alloc
-ERROR - 1439730764: (BlockWriteBatcher.cpp:403) No block in DB at height 0
[Thread 0xaad70b40 (LWP 24086) exited]
[New Thread 0x93e6eb40 (LWP 24087)]
-ERROR - 1439730764: (BlockWriteBatcher.cpp:711) error grabbing block 1|0 in file #0, offset: 301, with a size of 215 bytes
-ERROR - 1439730764: (BlockWriteBatcher.cpp:715) error: std::bad_alloc
-ERROR - 1439730764: (BlockWriteBatcher.cpp:403) No block in DB at height 1
[Thread 0x93e6eb40 (LWP 24087) exited]
[Thread 0x94ff0b40 (LWP 24084) exited]
[New Thread 0x94ff0b40 (LWP 24088)]
-ERROR - 1439730764: (BlockWriteBatcher.cpp:2175) hit interruption marker from pull threads
[New Thread 0x934ffb40 (LWP 24089)]
[Thread 0x934ffb40 (LWP 24089) exited]
[Thread 0x94ff0b40 (LWP 24088) exited]
[Thread 0x959ffb40 (LWP 24085) exited]
-WARN  - 1439730764: (BlockWriteBatcher.cpp:602) --- feedSleep: 0 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:605) --- workers: 0 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:608) --- writeStxo: 0.000131 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:610) --- writeStxo_grabMutex: 0 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:613) --- waitingOnSerThread: 0.004589 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:615) --- waitForDataToWrite: 0.872389 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:619) --- checkForCollisions: 0 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:621) --- getExistingKeys: 0.023769 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:623) --- getNewKeys: 0 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:625) --- getSSHHeadersLock: 1.7e-05 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:627) --- computeDBKeys: 0 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:629) --- getSshHeaders: 5.6e-05 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:631) --- finalizeSerialization: 0.004755 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:636) --- serializeBatch: 0.007962 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:638) --- serializeSubSsh: 3.6e-05 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:640) --- waitOnSSHser: 0.004153 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:644) --- waitOnWriteThread: 1.9e-05 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:647) --- putSSH: 0.000573 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:649) --- putSTX: 0.000375 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:652) --- getnextfeed: 0.814203 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:654) --- inControlThread: 1.09172 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:658) --- cleanup: 0 s
-WARN  - 1439730764: (BlockWriteBatcher.cpp:660) --- finishCleanup: 0 s
-INFO  - 1439730764: (BDM_supportClasses.cpp:259) Done with side scan of wallet
[Thread 0x947efb40 (LWP 24081) exited]
[Thread 0xacabfb40 (LWP 24083) exited]
-ERROR - 1439730764: (BDM_mainthread.cpp:430) BDM thread failed: Cannot find block with hash
[Thread 0xabe84b40 (LWP 20427) exited]
[New Thread 0xacabfb40 (LWP 24090)]
[Thread 0xacabfb40 (LWP 24090) exited]
[New Thread 0xacabfb40 (LWP 24091)]
[Thread 0xacabfb40 (LWP 24091) exited]
[New Thread 0xacabfb40 (LWP 24092)]
[Thread 0xacabfb40 (LWP 24092) exited]
[New Thread 0xacabfb40 (LWP 24093)]
[Thread 0xacabfb40 (LWP 24093) exited]
[New Thread 0xacabfb40 (LWP 24094)]
[Thread 0xacabfb40 (LWP 24094) exited]
[New Thread 0xacabfb40 (LWP 24095)]
[Thread 0xacabfb40 (LWP 24095) exited]
[New Thread 0xacabfb40 (LWP 24096)]
[Thread 0xacabfb40 (LWP 24096) exited]
[New Thread 0xacabfb40 (LWP 24097)]
[Thread 0xacabfb40 (LWP 24097) exited]
[New Thread 0xacabfb40 (LWP 24098)]
[Thread 0xacabfb40 (LWP 24098) exited]
[New Thread 0xacabfb40 (LWP 24099)]
[Thread 0xacabfb40 (LWP 24099) exited]
[Thread 0xb7c0a940 (LWP 20123) exited]
[Inferior 1 (process 20123) exited normally]
(gdb) backtrace
No stack.
(gdb)
Post
Topic
Board Armory
Re: Starting preliminary 0.94 testing - "Headless fullnode"
by
m.fridge
on 14/08/2015, 18:55:17 UTC
Hi,

my previously reported bug (post #156 in this thread) has been fixed. Thanks for that! However, I've got new issues here:

When I first import a wallet before the database is built, then armory seems to stuck in an endless loop when beginning to scan transactions. The program consumes CPU and has high I/O, but it keeps staying at 4% scanning progress (even when running for one night).

When I first build the database and import the wallet afterwards, armory crashes when it comes to transaction scanning. Here is backtrace of such a crash:

Code:
[Thread 0xabcf0b40 (LWP 15657) exited]
[New Thread 0xabcf0b40 (LWP 15658)]
[Thread 0xabcf0b40 (LWP 15658) exited]
[Thread 0xab2ffb40 (LWP 15283) exited]
[New Thread 0xab2ffb40 (LWP 15659)]
terminate called after throwing an instance of 'LMDBException'
  what():  Failed to insert: need transaction

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xab2ffb40 (LWP 15659)]
0xb7fdda0c in ?? ()
(gdb) backtrace
#0  0xb7fdda0c in ?? ()
#1  0x65637845 in ?? ()
(gdb)
Post
Topic
Board Armory
Re: Starting preliminary 0.94 testing - "Headless fullnode"
by
m.fridge
on 06/07/2015, 21:27:01 UTC
Yes, I tried it 3 times. Although only the last time in gdb, where I got the backtrace.
Post
Topic
Board Armory
Re: Starting preliminary 0.94 testing - "Headless fullnode"
by
m.fridge
on 06/07/2015, 19:52:35 UTC
I get a segmentation fault during the "Organizing Blockchain" step.

The last messages:
Code:
[New Thread 0xac9f1b40 (LWP 12492)]
[Thread 0xac9f1b40 (LWP 12492) exited]
[New Thread 0xac9f1b40 (LWP 12493)]
[Thread 0xac9f1b40 (LWP 12493) exited]
[New Thread 0xac9f1b40 (LWP 12494)]
[Thread 0xac9f1b40 (LWP 12494) exited]
-INFO  - 1436209883: (BlockUtils.cpp:1651) Loading block data... file 0 offset 0
[New Thread 0xac9f1b40 (LWP 12495)]
-INFO  - 1436209883: (BlockUtils.cpp:395) reading blocks from file 0

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xab9b5b40 (LWP 12174)]
0xb7d87062 in ?? () from /lib/libc.so.6

And the backtrace:
Code:
#0  0xb7d87062 in ?? () from /lib/libc.so.6
#1  0xb7d852b5 in ?? () from /lib/libc.so.6
#2  0xb4bf23b0 in BlockDataManager_LevelDB::BitcoinQtBlockFiles::readRawBlocksFromFile(BlockFileAccessor&, unsigned int const&, unsigned long long, unsigned long long, std::function const&, unsigned int)> const&) const (this=0x8cba778, bfa=..., f=@0xab9b4edc: 0, blockFileOffset=0, stopBefore=2097361271, blockDataCallback=...) at BlockUtils.cpp:506
#3  0xb4bf1bd9 in BlockDataManager_LevelDB::BitcoinQtBlockFiles::readRawBlocks(LMDBBlockDatabase*, std::pair, std::pair, std::function const&, unsigned int)> const&) (this=0x8cba778, db=0x83829d0, startAt=..., stopAt=..., blockDataCallback=...) at BlockUtils.cpp:401
#4  0xb4bea795 in BlockDataManager_LevelDB::loadBlockData (this=0x8344ef0, prog=..., stopAt=..., updateDupID=true) at BlockUtils.cpp:1653
#5  0xb4be8403 in BlockDataManager_LevelDB::loadDiskState(std::function const&, bool) (this=0x8344ef0, progress=..., forceRescan=false) at BlockUtils.cpp:1395
#6  0xb4be70df in BlockDataManager_LevelDB::doInitialSyncOnLoad(std::function const&) (this=0x8344ef0, progress=...) at BlockUtils.cpp:1224
#7  0xb4c9243f in BlockDataManagerThread::run (this=0x838e7f0) at BDM_mainthread.cpp:289
#8  0xb4c9349f in BlockDataManagerThread::thrun (_self=0x838e7f0) at BDM_mainthread.cpp:446
#9  0xb7e00ffb in start_thread () from /lib/libpthread.so.0
#10 0xb7d48fee in clone () from /lib/libc.so.6