Pages:
Author

Topic: CppnotificationHandler problem - page 2. (Read 1070 times)

newbie
Activity: 28
Merit: 0
December 27, 2016, 05:41:13 PM
#9
which function should I use to get this data?

m.
legendary
Activity: 3766
Merit: 1364
Armory Developer
December 27, 2016, 02:57:00 PM
#8
Ok, what about fetching missing history by address?
newbie
Activity: 28
Merit: 0
December 27, 2016, 02:51:54 PM
#7
I am not using ArmoryQt on online machine. I have only shell console - its remote server.

m.
legendary
Activity: 3766
Merit: 1364
Armory Developer
December 27, 2016, 02:45:20 PM
#6
Do you get the full history by loading the wallet in ArmoryQt?
newbie
Activity: 28
Merit: 0
December 27, 2016, 02:39:00 PM
#5
(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
legendary
Activity: 3766
Merit: 1364
Armory Developer
December 27, 2016, 02:03:41 PM
#4
Let me see the whole log file then.
newbie
Activity: 28
Merit: 0
December 27, 2016, 01:58:30 PM
#3
I have only one wallet and its active.

m.
legendary
Activity: 3766
Merit: 1364
Armory Developer
December 27, 2016, 01:33:50 PM
#2
Are you using several wallets? In armoryd, you need to select a wallet to be active in order to fetch data for it. At any rate, since I've taken over Armory alone, I have neglected armoryd. I intent to go over it for the upcoming version. Feel free to drop by the IRC channel (#bitcoin-armory on freenode) or create a issue on the github page to go over the bugs you have encountered and I'll make sure to fix them for 0.96.
newbie
Activity: 28
Merit: 0
December 27, 2016, 09:21:48 AM
#1
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.

Pages:
Jump to: