Node stops running

General
21

To add swap:

  • edit the file /etc/dphys-swapfile using root, e.g., sudo nano /etc/dphys-swapfile
  • replace the line CONF_SWAPSIZE=100 with CONF_SWAPSIZE=4096
  • restart swap: sudo /etc/init.d/dphys-swapfile restart

Also, disable catchpoint tracking following this post: Archival Node Sync Time - #6 by tsachi

You will need to create a file config.json in your data folder data/ if it does not exist. It’s a JSON file and you must make it look something like:

{
   "CatchpointTracking": -1,
   ...
}

(where ... are all the other settings - if no other settings remove the comma above)

22

Thank you I will do this when I get home from work.

23

Edit this is using -w command it never did this before…

pi@Ansuz4u:~/node ./goal node start -d data Algorand node successfully started! pi@Ansuz4u:~/node ./goal node status -d data -w 1000
Last committed block: 13262769
Time since last block: 0.0s
Last committed block: 13262773
Time since last block: 1.9s
Last committed block: 13262782
Time since last block: 2.2s
Last committed block: 13262798
Time since last block: 2.0s
Last committed block: 13262818
Time since last block: 2.1s
Last committed block: 13262835
Time since last block: 1.3s
Last committed block: 13262840
Time since last block: 2.7s
Last committed block: 13262840
Time since last block: 3.7s
Last committed block: 13262851
Time since last block: 1.1s
Last committed block: 13262856
Time since last block: 2.7s
Last committed block: 13262872
Time since last block: 2.8s
Last committed block: 13262898
Time since last block: 1.2s
Last committed block: 13262900
Time since last block: 0.8s
Last committed block: 13262900
Time since last block: 3.6s
Last committed block: 13262900
Time since last block: 4.6s
Last committed block: 13262900
Time since last block: 5.6s
Last committed block: 13262916
Time since last block: 1.4s
Last committed block: 13262938
Time since last block: 2.8s
Last committed block: 13262942
Time since last block: 1.3s
Last committed block: 13262963
Time since last block: 3.9s
Sync Time: 60.3s
Last consensus protocol: GitHub - algorandfoundation/specs at 3a83c4c743f8b17adfd73944b4319c25722a6782
Next consensus protocol: GitHub - algorandfoundation/specs at 3a83c4c743f8b17adfd73944b4319c25722a6782
Round for next consensus protocol: 13262964
Next consensus protocol supported: true
Last Catchpoint:
Genesis ID: mainnet-v1.0
Genesis hash: wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=
Cannot contact Algorand node: Get “http://127.0.0.1:8080/versions”: dial tcp 127.0.0.1:8080: connect: connection reset by peer
pi@Ansuz4u:~/node $

Edit
I did notice that it did not use the swap file at all during the time it was running prior to the node stopping

I also closed out of chromium to see if that was effecting it

24

I did some digging and found this it seemed promising so I followed it.

still doing the same thing but the memory usage is a lot less. still some spikes to 98% but not like it was and its not touching the swap file.

Thinking back this problem started when i tried to set up the participation node.

So just as an Idea what should my part key string look like following the instructions.
$./goal account addpartkey -a address-of-participating-account --roundFirstValid= partkey-first-round --roundLastValid= partkey-last-round --keyDilution= key-dilution-value

Using numbers for round first valid and round last valid and key dilution? Im think me not adding enough or key dilution or private spending key? is the private spending key my send algo from my algo wallet?

25

I get this exact same issue:

Get “http://127.0.0.1:8080/v1/transactions/params”: dial tcp 127.0.0.1:8080: connect: connection refused

seems to be happening at random but I got it twice after callig goal account changeonlinestatus…

26

Welcome to Algorand!

The first step is to check that your node is powerful enough. Now you need at least 8GB of RAM and a not-too-slow SSD. An SD card or an HDD will be too slow.

If you are satisfying the above specs, then can you check RAM use, CPU use just before the crash?

27

I am running it with a rpi 4gb ram. I increased the swap file to 2gb though. Running it with an m.2 so hd shouldn’t be an issue. It could be a ram problem indeed… I did not check it before the crash.