Dojo stops communicating with bitcoind after some time about samourai-dojo

[kenshin-samourai]

can you check in the logs of the tracker/api if you see some traces of network errors?

• dojo.sh logs tracker -d error -n 500
• dojo.sh logs api -d error -n 500

[Relaxo143]

Tracker and api logs

[kenshin-samourai]

i see several instances of these errors

host=192.168.0.169 port=8332: Request error: connect ETIMEDOUT 192.168.0.169:8332
host=192.168.0.169 port=8332: Request error: connect ECONNREFUSED 192.168.0.169:8332
host=192.168.0.169 port=8332: Connection Rejected: 403 Forbidden

these errors and your observations suggest a network issue that isn't related to dojo. a few hypotheses:

• local ip addresses used by machines running bitcoind and/or docker aren't static (dhcp?). Do others clients (lnd, cgminer) run on the same machine as your bitcoind? do they contact it through localhost?
• network issue with win10?

it's orthogonal to the network issue but i see an instance of this error

JavaScript heap out of memory

it suggests that the ram allocated to your docker engine may be a bit too low.

[Relaxo143]

I have assigned a permanent IP to the machine. Dojo runs on a VM on top of windows and Bitcoin Core runs on windows itself. lnd and cgminer run on the same windows machine directly, connecting to localhost. The VM uses 1.6 out of 2.2 GB Ram allocated and also uses 700MB of swap. I'm not sure why it's swapping when there is Ram available, but I'll try with 2.5GB.

[LaurentMT]

Closed for inactivty