panic: unaligned 64-bit atomic operation

[aelg]

Subject of the issue

algod panics. Seems like its able to commit a few blocks after each restart, then panics with:

panic: unaligned 64-bit atomic operation
goroutine 565 [running]:
runtime/internal/atomic.panicUnaligned()
        runtime/internal/atomic/unaligned.go:8 +0x24
runtime/internal/atomic.Xadd64(0xee3d10c, 0x1)
        runtime/internal/atomic/atomic_arm.s:256 +0x14
github.com/algorand/go-algorand/network.(*wsPeer).handleFilterMessage(0xee3d080, {{0xe080e0, 0xee3d080}, {0xf52def4, 0x2}, {0x103427e0, 0x20, 0x20}, {0x0, 0x0}, ...})
        github.com/algorand/go-algorand/network/wsPeer.go:589 +0xf0
github.com/algorand/go-algorand/network.(*wsPeer).readLoop(0xee3d080)
        github.com/algorand/go-algorand/network/wsPeer.go:495 +0x57c
created by github.com/algorand/go-algorand/network.(*wsPeer).init
        github.com/algorand/go-algorand/network/wsPeer.go:377 +0x3b8

Seems like the last logged line in node.log consistently is:

{"event":"Disconnected","file":"wsNetwork.go","function":"github.com/algorand/go-algorand/network.(*WebsocketNetwork).removePeer","level":"info","line":2186,"local":"","msg":"Peer r-hg.algorand-mainnet.network:4160 disconnected: ReadError","name":"","remote":"r-hg.algorand-mainnet.network:4160","time":"2022-10-09T16:56:42.369986Z"}

Your environment

§ algod -v
12885557248
3.10.0.stable [rel/stable] (commit #9869cd96)
go-algorand is licensed with AGPLv3.0
source code available at https://github.com/algorand/go-algorand

Raspberry Pi 4 8GB

$ uname -a
Linux alarmpi 5.15.61-4-rpi-ARCH #1 SMP Thu Sep 1 13:35:37 MDT 2022 armv7l GNU/Linux

Steps to reproduce

1. Start node
2. Wait a few seconds

Expected behaviour

No panic

Actual behaviour

panic

[aelg]

Forgot to say, the node has been working fine for a long time (it's not a first installation). I checked in on it today and saw it restart-looping with this panic.

[aelg]

Seems like others are seeing the same thing https://forum.algorand.org/t/node-crash-after-start/7988

[mattstover83]

Experiencing the same problem with the same specs.

[aelg]

As a workaround setting "EnableOutgoingNetworkMessageFiltering": false in config.json, seems to prevent the panic. It made my node working again.

[mattstover83]

Thanks for the info, will try that.

edit: worked!

[mattstover83]

Not working anymore 🙄

panic: unaligned 64-bit atomic operation

goroutine 233 [running]:
runtime/internal/atomic.panicUnaligned()
...

[aelg]

Yes I submitted a new issue in #4855 but I switched to a 64-bit system when it happened again . Seems like the 32-bit build isn't very stable.