search

gcarq / rusty-blockparser

Bitcoin Blockchain Parser written in Rust language
GNU General Public License v3.0
369 stars 145 forks source link

Balances Subcommand runs and creates CSV, but doesn't actually add anything to the file #84

Closed IncendiaryBC closed 1 year ago

IncendiaryBC commented 1 year ago

The code runs as the readme shows it should, but upon completion the specified path has a new csv file labeled 'balances.csv.tmp' and is completely empty

gcarq commented 1 year ago

Can you post how you started the program and some output, also increase the verbosity to see if something is not working as intended

IncendiaryBC commented 1 year ago

Running the balances subcommand results in something like this for me

 ./blockparser balances /path/to/dump/

[6:02:53] INFO - main: Starting rusty-blockparser v0.8.1 ...

[6:02:53] INFO - index: Reading index from ~/.bitcoin/blocks/index ...

[6:02:54] INFO - index: Got longest chain with 639626 blocks ...

[6:02:54] INFO - blkfile: Reading files from ~/.bitcoin/blocks ...

[6:02:54] INFO - parser: Parsing Bitcoin blockchain (range=0..) ...

[6:02:54] INFO - callback: Using `balances` with dump folder: /path/to/dump ...

[6:03:04] INFO - parser: Status: 130885 Blocks processed. (left: 508741, avg: 13088 blocks/sec)
...

[10:28:47] INFO - parser: Status: 639163 Blocks processed. (left:    463, avg:    40 blocks/sec)

[10:28:57] INFO - parser: Status: 639311 Blocks processed. (left:    315, avg:    40 blocks/sec)

[10:29:07] INFO - parser: Status: 639452 Blocks processed. (left:    174, avg:    40 blocks/sec)

[10:29:17] INFO - parser: Status: 639596 Blocks processed. (left:     30, avg:    40 blocks/sec)

Killed

However, if I add a distinct start or endpoint, it runs fine (so far, with the values I've chosen). Using verbosity of 2, I'm seeing the occasional 'invalid utxo ignored', but nothing that halts the program

gcarq commented 1 year ago

Seems like the process gets killed before it can finish. Can you check if your system runs out of memory, maybe there is also a message in the system log that indicates who and why killed the process.

IncendiaryBC commented 1 year ago

I'm not certain, but it seems like that's the issue. I probably should've thought of that sooner, but I appreciate you getting back so quickly!

gcarq commented 1 year ago

If thats the case consider increasing your swap, that should hopefully fix it