-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Open
Description
monerod is segfaulting roughly once per few hours (docker container autorestarts). I have rolled back to 4.2 to see if the issue goes away.
[1699348.429995] monerod[1354261]: segfault at a3 ip 0000561c0c54c018 sp 00007f1159080120 error 4 in monerod[561c0c474000+795000]
Update: rolling back actually didn't fix this.. it seems like there is a flood of traffic, hundreds of IPs are blocked all within one second then the crash happens...
2025-10-13 11:16:09.378 I Host 104.248.206.131 blocked.
2025-10-13 11:16:09.379 I Host 104.248.231.61 blocked.
2025-10-13 11:16:09.380 I Host 116.203.249.163 blocked.
.... x 200+ IPs blocked within a second.
2025-10-13 11:16:16.610 I ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 3515415
2025-10-13 11:16:16.610 I id: <c644920dd719720dece040056b1a512b7963fda79de2cf65786ececd449bd08b>
2025-10-13 11:16:16.610 I PoW: <b662ea2c8f01df66a75315c8019ea1c28559b389a0909d3c6d34960000000000>
2025-10-13 11:16:16.610 I difficulty: 561959871867
2025-10-13 11:35:58.991 I Monero 'Fluorine Fermi' (v0.18.4.2-release)
2025-10-13 11:35:58.991 I Initializing cryptonote protocol...
I don't have debugging on but will do it. Other VMs on the hypervisor are not experiencing any segfaults so I don't believe it is a system hardware issue.
Metadata
Metadata
Assignees
Labels
No labels