Set it to 500 manually, did not help sadly.

I'm running aarch64 on the pi3 if that is interesting in some extent.

Desktop has 16GB.

Raspberry pi3 has the 1GB standard and i have gpu_mem=16 in /boot/config.txt to allow maximum RAM for the node.
I also have an extra 1GB Swap file derived from the Pi's SD-card.
But the memory is far from full.

An old launch option was -dbcache=50 but I still had this issue, i'll try to play around with this value a bit more and see if it affects it at all. Thnx for the tip.


EDIT: Tried setting -dbcache=4 (which is minimum) but no difference. Still keeps downloading something at ~92 Mbit/s 

Hello,

I have been fault-tracing something fishy that is going on when i run a node on my raspberry pi but I don't seem to get any further on my own.

The problem:
After the blocks have been indexed/verified etc. the bitcoind process keeps downloading something constantly at around ~92Mbit+/s. I have verified this both using vnstat, bwm-ng locally and on the NAS itself on that side using similar tools so I am 100% that the node is requesting some data constantly from the datadir while the service is up and running.

My setup:
Raspberry Pi 3 running 0.14.1 daemon mounts a NFS share from my NAS to store the data.
I've tested adapted launch options for the rpi such as -dbcache etc. but during the more detailed fault tracing I was just using:
$ bitcoind -datadir=/mnt/bitcoin -printtoconsole

I downloaded bitcoind to my desktop to try to recreate the problem but it works flawlessly there.
It had the exact same circumstances, same NFS share with the same data on it.
It verifies the blocks (a lot faster though since it's a relatively fast computer compared to the pi3) and then just sits there pulling almost no data from the NFS share at all (like it should). Verfied using vnstat, bwm-ng locally and on the NAS itself as before.

It doesn't seem to be an NFS issue, the mounts are mounted exactly the same on both machines during seperate testing.
Could the PI3 not be processing something fast enough that it needs to keep reading something from the datadir?

What could possibly be wrong here?
I really want to run this full node (without constantly draining my NASes bandwidth)

EDIT: The console/outputfile(s) mentions nothing suspicious from what I can tell

Hi. I saw an old post from 2013 touching the following problem but there was no concrete solution.

My question is this:

I run a bitcoind full node on a dedicated machine on my home network. I then run armory/bitcoind on my desktop machine.
Is there a way to have armory use my full node over the network rather than having a duplicate copy of the blockchain just wasting space?

Another great answer, thanks! Just wanted to know if it was safe to send around fairly publicly (for backup intentions).

Great answer, thanks!

EDIT: So if I get this straight the encrypted wallet version is basically the same as the normal wallet just that I manually created it using the program. So the "encrypt"-text is just there to clarify it?
EDIT2: Are my private keys safe should someone get a hold of the "normal" wallet file?

What is the difference between these two:

• armory_xxxxxxxx_.wallet
• armory_xxxxxxxx_encrypt.wallet

That one is encrypted is fairly clear but isn't the normal file "encrypted" as well? Does the first file really contain private keys in plain text?

This problem happened to me too. Solved it by opening port 8333.
Then what happened was that I had another computer in the same network I wanted to open another wallet on.

And this computer just remained idle with 0 connections. And I didn't want to use UPnP.


How I solved it:
My network structure is as follows:

10.0.0.1 NAT
10.0.0.2 Computer 1 running bitcoin
10.0.0.3 Computer 2 running bitcoin

Forward port 8333 from NAT to 10.0.0.2 and connections get through.

On Computer 2 launch bitcoin with:   bitcoin -addnode 10.0.0.2  and it recieves blocks from the other computer.

If you want to add additional computers with bitcoin just launch them as well with -addnode 10.0.0.2

I use 10.0.0.X for ease, this might be 192.168.0.X or similar for you.


Hope this helped someone!