I had to reboot my pi 4b due to display was lost and wouldn’t come back up. now when i try to start the node I get this. ./goal node start -d data Algorand node failed to start: node exited with an error code, check node.log for more details : exit status 2 I went to the node.log how do i jump t…

The issue was already addressed on master, and was deployed yesterday to betanet ( BetaNet Update: 2.5.6 ). I don’t have any particular date, but would expect it to reach mainnet shortly unless some regression would be found while it’s on betanet.

try tail -n 100 node.log to show the last 100 lines on the log file.

this is the end of my node.log {“Context”:“Agreement”,“Hash”:“KYBONECTBPN2RJVJ3HE2VJLMEJRIQJOKIOCGXYD4FDH5KPFGETPQ”,“ObjectPeriod”:0,“ObjectRound”:0,“ObjectStep”:0,“Period”:0,“Round”:13409875,“Sender”:“3F3QL7IHS2D6LTPP2K6OG35DXW2GY7VNXLRM57PIHUMYHJKZGKGJ3MENAM”,“Step”:0,“Type”:“RoundStart”,“Weight”…

tail -n 100 algod-err.log panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xb559d460] goroutine 1 [running]: runtime/internal/atomic.goLoad64(0x850712ac, 0x852618e4, 0x85071201) runtime/internal/atomic/atomic_a…

[image] Ansuz4u: nextWorker @Ansuz4u , Thanks for providing that info. This is a bug in the implementation that would affect all RasbPI machines. I will file an issue for that so that the algorand dev team could look at this. edit: feel free to subscribe to algod panics on startup · Issue #…

Node has been running for 2 days

General

Ansuz4u April 27, 2021, 12:35pm 6

@tsachi
Do you have a time frame on the update being available to fix this issue? I would like to get my node back up and running.

Topic		Replies	Views
Node start and stop errors	31	3124	June 14, 2021
Node stops running General	26	2018	April 2, 2022
Algorand node failed to start: node exited with an error code, check node.log for more details : exit status 1 General	7	967	December 7, 2022
Node crash after start General noderunner	5	706	October 6, 2022
Algorand Node stop synching after upgrading it to version 3.15.1 General	9	612	June 2, 2023

Node has been running for 2 days

Related topics