 Show Posts
|
|
Pages: [1] 2 »
|
|
I have changed number of threads to 15, then
1) from command line "make DEBUG=1"
2) from command line "gdb ArmoryDB"
3) <gdb> run
now every couple of seconds log in gdb change and looks like:
[New Thread 0x7fff8f7fe700 (LWP 26326)]
[Thread 0x7fff8f7fe700 (LWP 26326) exited]
[New Thread 0x7fff8f7fe700 (LWP 26327)]
[Thread 0x7fff8f7fe700 (LWP 26327) exited]
[New Thread 0x7fff8f7fe700 (LWP 26328)]
[Thread 0x7fff8f7fe700 (LWP 26328) exited]
[New Thread 0x7fff8f7fe700 (LWP 26329)]
[Thread 0x7fff8f7fe700 (LWP 26329) exited]
[New Thread 0x7fff8f7fe700 (LWP 26330)]
[Thread 0x7fff8f7fe700 (LWP 26330) exited]
[New Thread 0x7fff8f7fe700 (LWP 26331)]
[Thread 0x7fff8f7fe700 (LWP 26331) exited]
[New Thread 0x7fff8f7fe700 (LWP 26332)]
[Thread 0x7fff8f7fe700 (LWP 26332) exited]
[New Thread 0x7fff8f7fe700 (LWP 26333)]
[Thread 0x7fff8f7fe700 (LWP 26333) exited]
[New Thread 0x7fff8f7fe700 (LWP 26334)]
[Thread 0x7fff8f7fe700 (LWP 26334) exited]
[New Thread 0x7fff8f7fe700 (LWP 26335)]
[Thread 0x7fff8f7fe700 (LWP 26335) exited]
[New Thread 0x7fff8f7fe700 (LWP 26336)]
[Thread 0x7fff8f7fe700 (LWP 26336) exited]
[New Thread 0x7fff8f7fe700 (LWP 26337)]
[Thread 0x7fff8f7fe700 (LWP 26337) exited]
[New Thread 0x7fff8f7fe700 (LWP 26338)]
[Thread 0x7fff8f7fe700 (LWP 26338) exited]
[New Thread 0x7fff8f7fe700 (LWP 26339)]
[Thread 0x7fff8f7fe700 (LWP 26339) exited]
[New Thread 0x7fff8f7fe700 (LWP 26340)]
[Thread 0x7fff8f7fe700 (LWP 26340) exited]
[New Thread 0x7fff8f7fe700 (LWP 26341)]
[Thread 0x7fff8f7fe700 (LWP 26341) exited]
[New Thread 0x7fff8f7fe700 (LWP 26342)]
[Thread 0x7fff8f7fe700 (LWP 26342) exited]
armoryD is running. Is it all right? Should I wait now for error and the gdb will stop? then I will may type "bt all"?
Thank You in advance for Your help
m.
|
|
|
|
|
should I decrease amount of threads to for example 20 ?
m.
|
|
|
|
|
I have patched the code. Now Armory deamon was terminated after c.a 9 hours of running, then I have started it again and it took c.a 8-9 hours and the error happen again:
In my opinion the patch helped but there must be something more which cuase error:
New Block: 446454
New Block: 446455
New Block: 446456
New Block: 446457
New Block: 446458
New Block: 446459
New Block: 446460
New Block: 446461
New Block: 446462
New Block: 446463
New Block: 446464
-INFO - 1483465297: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465299: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465309: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465314: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465316: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465319: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465321: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465325: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465333: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465334: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465350: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483465398: (SocketObject.cpp:517) POLLIN recv return 0
Can I help You with investigating problem by running my deamon with some kinde of debug etc? I don't know wheter it will be easy to find a reason of problem beause each time I had to wait couple of hours for it.
m.
|
|
|
|
|
I send 100 outgoing transactions from wallet (in c.a 30 seconds all):
and the daemon log an error like below:
(INFO) armoryd.py:3370 - New ZC tx: 2000000
(INFO) armoryd.py:3370 - New ZC tx: 33608
(INFO) armoryd.py:3370 - New ZC tx: -10527220
(INFO) armoryd.py:3370 - New ZC tx: -12913772
(INFO) armoryd.py:3370 - New ZC tx: -1990000
(INFO) armoryd.py:3370 - New ZC tx: -4193393
(INFO) armoryd.py:3370 - New ZC tx: -2020640
(INFO) armoryd.py:3370 - New ZC tx: -18500000
(INFO) armoryd.py:3370 - New ZC tx: -106172
(INFO) armoryd.py:3370 - New ZC tx: -735709
(INFO) armoryd.py:3370 - New ZC tx: -5020640
(INFO) armoryd.py:3370 - New ZC tx: -790640
(INFO) armoryd.py:3370 - New ZC tx: -320640
(INFO) armoryd.py:3370 - New ZC tx: -73220
(INFO) armoryd.py:3370 - New ZC tx: -517525
(INFO) armoryd.py:3370 - New ZC tx: -2257937
(INFO) armoryd.py:3370 - New ZC tx: -1013920
(INFO) armoryd.py:3370 - New ZC tx: -8194190
(INFO) armoryd.py:3370 - New ZC tx: -2324457
(INFO) armoryd.py:3370 - New ZC tx: -11291727
(INFO) armoryd.py:3370 - New ZC tx: -7860640
(INFO) armoryd.py:3370 - New ZC tx: -220640
(INFO) armoryd.py:3370 - New ZC tx: -220640
(INFO) armoryd.py:3370 - New ZC tx: -4300000
(INFO) armoryd.py:3370 - New ZC tx: -1151953
(INFO) armoryd.py:3370 - New ZC tx: -11920640
(INFO) armoryd.py:3370 - New ZC tx: -318831
(INFO) armoryd.py:3370 - New ZC tx: -2143039
(INFO) armoryd.py:3370 - New ZC tx: -1020640
(INFO) armoryd.py:3370 - New ZC tx: -42221280
(INFO) armoryd.py:3370 - New ZC tx: -10532429
(INFO) armoryd.py:3370 - New ZC tx: -28539483
(INFO) armoryd.py:3370 - New ZC tx: -2257059
(INFO) armoryd.py:3370 - New ZC tx: -113000
(INFO) armoryd.py:3370 - New ZC tx: -2020640
(INFO) armoryd.py:3370 - New ZC tx: -4107234
(INFO) armoryd.py:3370 - New ZC tx: -9704437
(INFO) armoryd.py:3370 - New ZC tx: -15220640
(INFO) armoryd.py:3370 - New ZC tx: -4920640
(INFO) armoryd.py:3370 - New ZC tx: -79360
(INFO) armoryd.py:3370 - New ZC tx: -100000
(INFO) armoryd.py:3370 - New ZC tx: -52462500
(INFO) armoryd.py:3370 - New ZC tx: -138673605
(INFO) armoryd.py:3370 - New ZC tx: -10566460
(INFO) armoryd.py:3370 - New ZC tx: -10544487
(INFO) armoryd.py:3370 - New ZC tx: -1400000
(INFO) armoryd.py:3370 - New ZC tx: -1081640
(INFO) armoryd.py:3370 - New ZC tx: -3020640
(INFO) armoryd.py:3370 - New ZC tx: -33072396
(INFO) armoryd.py:3370 - New ZC tx: -945195
(INFO) armoryd.py:3370 - New ZC tx: -5030640
(INFO) armoryd.py:3370 - New ZC tx: -252600
(INFO) armoryd.py:3370 - New ZC tx: -223920640
(INFO) armoryd.py:3370 - New ZC tx: -220640
(INFO) armoryd.py:3370 - New ZC tx: -11229000
(INFO) armoryd.py:3370 - New ZC tx: -9990000
(INFO) armoryd.py:3370 - New ZC tx: -14114489
(INFO) armoryd.py:3370 - New ZC tx: -7862640
(INFO) armoryd.py:3370 - New ZC tx: -14163165
(INFO) armoryd.py:3370 - New ZC tx: -11648277
(INFO) armoryd.py:3370 - New ZC tx: -2670298
(INFO) armoryd.py:3370 - New ZC tx: -2520640
(INFO) armoryd.py:3370 - New ZC tx: -2330640
(INFO) armoryd.py:3370 - New ZC tx: -1013640
(INFO) armoryd.py:3370 - New ZC tx: -1302327
(INFO) armoryd.py:3370 - New ZC tx: -481734
(INFO) armoryd.py:3370 - New ZC tx: -18670640
(INFO) armoryd.py:3370 - New ZC tx: -5650879
(INFO) armoryd.py:3370 - New ZC tx: -10490638
(INFO) armoryd.py:3370 - New ZC tx: -931080
(INFO) armoryd.py:3370 - New ZC tx: -11244500
(INFO) armoryd.py:3370 - New ZC tx: -220640
(INFO) armoryd.py:3370 - New ZC tx: -380640
(INFO) armoryd.py:3370 - New ZC tx: -1020640
(INFO) armoryd.py:3370 - New ZC tx: -1485205
(INFO) armoryd.py:3370 - New ZC tx: -2091110
(INFO) armoryd.py:3370 - New ZC tx: -1078640
-INFO - 1483206291: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206293: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206304: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206309: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206310: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206314: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206316: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206319: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206327: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206328: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206344: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206365: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206367: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206382: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206396: (SocketObject.cpp:517) POLLIN recv return 0
-INFO - 1483206397: (SocketObject.cpp:517) POLLIN recv return 0
terminate called after throwing an instance of 'DbErrorMsg'
I have to start daemon again.
m.
|
|
|
|
|
It seems much better after changing GETZC_THREADCOUNT to 100.
Now I have 3 questions:
1) If I set GETZC_THREADCOUNT for 100 and will have 100 incoming unconfirmed transfers for 10 hours (for example 100 transfers with low fees) does it mean that for 10 hours other ZC transactions will be ignored?
2) Is there any parameter which allow me to spend unconfirmed outputs now (especially I mean unconfirmed change from previous unconfirmed transaction)?
3) For 2-3 times since yesterday I had some error like "POOLIN:0". It was sometking about connection to DB. Do You know it? I will try to provide You a log for the next time when it will appear.
m.
|
|
|
|
|
Thank You. I will test it and let You know.
m.
|
|
|
|
|
tab = TheBDM.bdv().getLedgerDelegateForWallets().getHistoryPage(0)
for above (is it global ledger for You?) result are exaclty the same as for
tab =self.curWlt.cppWallet.getHistoryPage(0)
I have also called below code. Confirmed transactions looks fine but unconfirmed are absent in result.
tab = TheBDM.bdv().getLedgerDelegateForScrAddr(self.curWlt.uniqueIDB58,Hash160ToScrAddr(a160)).getHistoryPage(0)
My problem is not even to sent ZC inputs but when I get unspent outputs for some address and I wanna prepare transaction from it I am not sure whether maybe they had been already used and transaction which included them is waiting in mempool for confirmation. Of course Inputs are not availabe when transaction get at least one confirmation but sometimes it takes 30 minutes or more time and inputs should not be in "getunspentoutputsforaddres" available during this time.
What exactly do You mean rescan & rebuild database? delete database and start client (or Armorydb) with some parameters? Or maybe I may do this when deamon is running?
m.
|
|
|
|
|
Bitcoind 0.13.1 (txindex=1)
Armory 0.95.1
Watchingonly wallet (25000 addresses) - wallet generated with 0.93.1
I have tested function provided by You and I have couple of question:
My code:
tab =self.curWlt.cppWallet.getHistoryPage(0)
for tx in tab:
if tx.getValue()>0:
print tx.getValue()
print '\t', binary_to_hex(tx.getTxHash(),BIGENDIAN)
print '\t', time.ctime(int(tx.getTxTime()))
addr = tx.getScrAddrList()
for a160 in addr:
print '\t',hash160_to_addrStr(a160)
Belowe some LedgerElelementDatas - output from above code:
300000
47a99e5e1e58b2c89b604bd6d1da634e4815f527eca2a761d631d7f393a47d22
Fri Dec 30 09:33:20 2016
11477731
23f65038e91b7bee1b4f6d734ba848708a19d3c4ab17aeb538a7c95ebbde7ada
Fri Dec 30 09:33:20 2016
26687823
1b58c8db6e190f78597ff82985b7c2ba2b00e5b0c017e55c086fad1671082158
Fri Dec 30 09:33:20 2016
2588182
819b13d1431940e172c21cdce5c793e8d7f44c2da97d530f7725f704e1bc27ac
Fri Dec 30 09:33:20 2016
Question 1) Why getScrAddrList() return always empty list? How can I get information aboute addresses (source and destination) from each transaction.
Question 2) getHistoryPage(0) returns:
1 unconfirmed transaction when I have 3-6 unconfirmed transaction in wallet
4 unconfirmed transatcions when I have 50 unconfirmed transactoin in wallet (I am sending 50 transaction from one address to different addresses in wallet or I am sending out 50 transactions from wallet - each from different address to one destination address).
Is it a bug? Why all unconfirmed transactions are not visible in history? Can You investigate it or verify whether the problem exists.
I see that getHistoryPage calls c++ code so the problem is rather not in python layer.
|
|
|
|
|
Fine,so I have an address with some unconfirmed transactions. This code return 0.0 balance when I run:
self.curWlt.getAddrDataFromDB()
self.curWlt.getBalancesAndCountFromDB()
atype,a160 = addrStr_to_hash160("1Ne9KrmTLuePACNXND29j3exxxxxxxxx")
print self.curWlt.getAddrBalance(a160,"unconf")
also getFullUTXOList return only inputs with at least 1 confirmation from the wallet.
How to make it to return also unconfirmed tx data?
m.
|
|
|
|
|
was this TheBDM.bdv().getUnspentTxoutsForAddr160List(scrAddrList, IGNOREZC) deprecated in 0.95.1 version ? Which should I use instead ?
m.
|
|
|
|
|
which function should I use to get this data?
m.
|
|
|
|
|
I am not using ArmoryQt on online machine. I have only shell console - its remote server.
m.
|
|
|
|
|
(INFO) ArmoryUtils.py:1137 - C++ block utilities loaded successfully
(INFO) ArmoryUtils.py:651 - Executing popen: free -m
(INFO) ArmoryUtils.py:651 - Executing popen: ['cat', '/proc/cpuinfo']
(INFO) ArmoryUtils.py:1247 -
(INFO) ArmoryUtils.py:1248 -
(INFO) ArmoryUtils.py:1249 -
(INFO) ArmoryUtils.py:1250 - ************************************************************
(INFO) ArmoryUtils.py:1251 - Invoked: /home/armory/BitcoinArmory-0.95.1/armoryd.py --debug
(INFO) ArmoryUtils.py:1252 - ************************************************************
(INFO) ArmoryUtils.py:1253 - Loading Armory Engine:
(INFO) ArmoryUtils.py:1254 - Armory Version : 0.95.1
(INFO) ArmoryUtils.py:1255 - Armory Build: : None
(INFO) ArmoryUtils.py:1256 - PyBtcWallet Version : 1.35
(INFO) ArmoryUtils.py:1257 - Detected Operating system: Linux
(INFO) ArmoryUtils.py:1258 - OS Variant : debian-8.6-
(INFO) ArmoryUtils.py:1259 - User home-directory : /home/armory
(INFO) ArmoryUtils.py:1260 - Satoshi BTC directory : /home/armory/.bitcoin/
(INFO) ArmoryUtils.py:1261 - Armory home dir : /home/armory/.armory/
(INFO) ArmoryUtils.py:1262 - Detected System Specs :
(INFO) ArmoryUtils.py:1263 - Total Available RAM : 47.26 GB
(INFO) ArmoryUtils.py:1264 - CPU ID string : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz
(INFO) ArmoryUtils.py:1265 - Number of CPU cores : 8 cores
(INFO) ArmoryUtils.py:1266 - System is 64-bit : True
(INFO) ArmoryUtils.py:1267 - Preferred Encoding : UTF-8
(INFO) ArmoryUtils.py:1268 - Machine Arch : x86_64
(INFO) ArmoryUtils.py:1269 - Available HDD (ARM) : 69 GB
(INFO) ArmoryUtils.py:1270 - Available HDD (BTC) : 69 GB
(INFO) ArmoryUtils.py:1271 -
(INFO) ArmoryUtils.py:1272 - Network Name: Main Network
(INFO) ArmoryUtils.py:1273 - Satoshi Port: 8333
(INFO) ArmoryUtils.py:1274 - Do wlt check: True
(INFO) ArmoryUtils.py:1275 - Named options/arguments to armoryengine.py:
(INFO) ArmoryUtils.py:1277 - thread_count : -1
(INFO) ArmoryUtils.py:1277 - rescan : False
(INFO) ArmoryUtils.py:1277 - ignoreAllZC : False
(INFO) ArmoryUtils.py:1277 - rescanBalance : False
(INFO) ArmoryUtils.py:1277 - disableModules : False
(INFO) ArmoryUtils.py:1277 - port : None
(INFO) ArmoryUtils.py:1277 - interport : 8223
(INFO) ArmoryUtils.py:1277 - skipStatsReport : False
(INFO) ArmoryUtils.py:1277 - forceWalletCheck: False
(INFO) ArmoryUtils.py:1277 - regtest : False
(INFO) ArmoryUtils.py:1277 - rebuild : False
(INFO) ArmoryUtils.py:1277 - nettimeout : 2
(INFO) ArmoryUtils.py:1277 - datadir : DEFAULT
(INFO) ArmoryUtils.py:1277 - clearMempool : False
(INFO) ArmoryUtils.py:1277 - offline : False
(INFO) ArmoryUtils.py:1277 - coverageOutputDir: None
(INFO) ArmoryUtils.py:1277 - armoryDBDir : DEFAULT
(INFO) ArmoryUtils.py:1277 - armorydb_port : 9001
(INFO) ArmoryUtils.py:1277 - satoshiPort : DEFAULT
(INFO) ArmoryUtils.py:1277 - useTorSettings : False
(INFO) ArmoryUtils.py:1277 - netlog : False
(INFO) ArmoryUtils.py:1277 - keypool : 100
(INFO) ArmoryUtils.py:1277 - coverageInclude : None
(INFO) ArmoryUtils.py:1277 - forceOnline : False
(INFO) ArmoryUtils.py:1277 - skipAnnounceCheck: False
(INFO) ArmoryUtils.py:1277 - redownload : False
(INFO) ArmoryUtils.py:1277 - armorydb_ip : 127.0.0.1
(INFO) ArmoryUtils.py:1277 - multisigFile : DEFAULT
(INFO) ArmoryUtils.py:1277 - ram_usage : -1
(INFO) ArmoryUtils.py:1277 - testAnnounceCode: False
(INFO) ArmoryUtils.py:1277 - mtdebug : False
(INFO) ArmoryUtils.py:1277 - logDisable : False
(INFO) ArmoryUtils.py:1277 - settingsPath : /home/armory/.armory/ArmorySettings.txt
(INFO) ArmoryUtils.py:1277 - db_type : DB_FULL
(INFO) ArmoryUtils.py:1277 - doDebug : True
(INFO) ArmoryUtils.py:1277 - enableDetSign : True
(INFO) ArmoryUtils.py:1277 - disableConfPermis: False
(INFO) ArmoryUtils.py:1277 - testnet : False
(INFO) ArmoryUtils.py:1277 - rpcport : DEFAULT
(INFO) ArmoryUtils.py:1277 - satoshiHome : DEFAULT
(INFO) ArmoryUtils.py:1277 - satoshiRpcport : DEFAULT
(INFO) ArmoryUtils.py:1277 - logFile : /home/armory/.armory/armoryd.py.log.txt
(INFO) ArmoryUtils.py:1277 - verbosity : None
(INFO) ArmoryUtils.py:1278 - Other arguments:
(INFO) ArmoryUtils.py:1281 - ************************************************************
(INFO) ArmoryUtils.py:1684 - C++ block utilities loaded successfully
(INFO) BDM.py:367 - Using the asynchronous/multi-threaded BlockDataManager.
(INFO) BDM.py:368 - Blockchain operations will happen in the background.
(INFO) BDM.py:369 - Devs: check TheBDM.getState() before asking for data.
(INFO) BDM.py:370 - Registering addresses during rescans will queue them for
(INFO) BDM.py:371 - inclusion after the current scan is completed.
(INFO) armoryd.py:3614 - No other armoryd.py instance is running. We're the first. 8225
(WARNING) armoryd.py:3072 - ************************************************************************
(WARNING) armoryd.py:3074 - * Please note that armoryd v0.95.1 is beta software and is still in
(WARNING) armoryd.py:3075 - * development. Whenever applicable, the interface is designed to match
(WARNING) armoryd.py:3076 - * that of bitcoind, with function parameters and return values closely
(WARNING) armoryd.py:3077 - * matching those of bitcoind. Despite this, the function parameters and
(WARNING) armoryd.py:3078 - * return values may change, both for ported bitcoind function and
(WARNING) armoryd.py:3079 - * Armory-specific functions.
(WARNING) armoryd.py:3080 - ************************************************************************
(WARNING) armoryd.py:3081 -
(WARNING) armoryd.py:3082 - ********************************************************************************
(WARNING) armoryd.py:3084 - * WARNING! WALLET FILE ACCESS IS NOT INTERPROCESS-SAFE!
(WARNING) armoryd.py:3085 - * DO NOT run armoryd at the same time as ArmoryQt if
(WARNING) armoryd.py:3086 - * they are managing the same wallet file. If you want
(WARNING) armoryd.py:3087 - * to manage the same wallet with both applications
(WARNING) armoryd.py:3088 - * you must make a digital copy/backup of the wallet file
(WARNING) armoryd.py:3089 - * into another directory and point armoryd at that one.
(WARNING) armoryd.py:3090 - *
(WARNING) armoryd.py:3091 - * As long as the two processes do not share the same
(WARNING) armoryd.py:3092 - * actual file, there is no risk of wallet corruption.
(WARNING) armoryd.py:3093 - * Just be aware that addresses may end up being reused
(WARNING) armoryd.py:3094 - * if you execute transactions at approximately the same
(WARNING) armoryd.py:3095 - * time with both apps.
(WARNING) armoryd.py:3096 - *
(WARNING) armoryd.py:3097 - ********************************************************************************
(WARNING) armoryd.py:3098 -
(INFO) ArmoryUtils.py:3597 - Using settings file: /home/armory/.armory/ArmorySettings.txt
(WARNING) armoryd.py:3135 - No lockboxes were loaded.
(DEBUG) ArmoryUtils.py:1107 - /home/armory/.armory/databases is a directory.
(INFO) armoryd.py:3155 - Number of wallets read in: 1
(INFO) armoryd.py:3160 - Wallet (Y49z82qM): "a_1000 (Watch) " (No Encryption)
(INFO) armoryd.py:3164 - Number of lockboxes read in: 0
(WARNING) armoryd.py:3173 - Active wallet is set to Y49z82qM
(INFO) armoryd.py:3181 - Initialising RPC server on port 8225
(WARNING) armoryd.py:3586 - Server started...
(WARNING) armoryd.py:3596 - Registering wallet: Y49z82qM
BDM is ready!
New Block: 445384
(INFO) armoryd.py:3299 - New Block! : 445384
|
|
|
|
|
I have only one wallet and its active.
m.
|
|
|
|
|
Hello,
I have c.a 25000 addresses in my watching only wallet. I start armoryd with it. Daemon runs properly.
There is problem with notifications, esepcially with NEW_ZC_ACTION in handleCppNotification()
I recieve 50 new transfers on my wallet (in 10 minutes) - each with different BTC address and in log there is information only about couple of them.
I have found out that only 10% of transfers are visible (logged - which mean the handler is not called (?) ). The same situation with outgoing transfer:
(WARNING) armoryd.py:3173 - Active wallet is set to Y49z82qM
(INFO) armoryd.py:3181 - Initialising RPC server on port 8225
(WARNING) armoryd.py:3586 - Server started...
(WARNING) armoryd.py:3596 - Registering wallet: Y49z82qM
BDM is ready!
New Block: 445336
(INFO) armoryd.py:3299 - New Block! : 445336
(INFO) armoryd.py:3265 - New ZC tx: 2393870
(INFO) armoryd.py:3265 - New ZC tx: 50000
New Block: 445337
(INFO) armoryd.py:3299 - New Block! : 445337
New Block: 445338
(INFO) armoryd.py:3299 - New Block! : 445338
(INFO) armoryd.py:3265 - New ZC tx: 48700
New Block: 445339
(INFO) armoryd.py:3299 - New Block! : 445339
(INFO) armoryd.py:3265 - New ZC tx: 7960018
New Block: 445340
(INFO) armoryd.py:3299 - New Block! : 445340
New Block: 445341
(INFO) armoryd.py:3299 - New Block! : 445341
New Block: 445342
(INFO) armoryd.py:3299 - New Block! : 445342
What may be the reason. All new block are logged correctly (above).
I use armoryd with 0.95.1 version.
Can someone help me?
M.
|
|
|
|
|
goatpig - i have sent you priv. message.
|
|
|
|
|
Now Iam in phase of r&d what armory can or can't do. I have problem with unspentoutputs. Let say I am sending a transaction from one of my address which is in the wallet. The transaction goes to mempool and in Electrum when I call "listunspent" the input which is used in transaction is not listed in results. In armory the input disappear when the transaction get one confirmation. Is it possible with functions which are implemented till today in armory have the same effect like in electrum?
m.
|
|
|
|
|
I have added
this
TheBDM.registerBDV()
in start().
but I see that there is plenty of places in code which should be changed. Iam doing it now but Iam not familiar with python ....
m.
|
|
|
|
|
