-
Notifications
You must be signed in to change notification settings - Fork 746
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node crashes seen after stable-2412 from segmentation fault:"status=11/SEGV" #6936
Comments
For the time being I'm reducing my 'db cache' to leave more free ram. |
Thanks for the report. Can you provide us with the full command you use to start the node and more logs? Best are full logs some minutes before the crash. Also debug levels would be helpful if possible. Not really clear what causes the crash, but |
Even better would be to collect some backtrace using |
I'll work on additional logs, or getting settings in place so I can capture more data in the future.
|
Issue occurred on one of my nodes, then upon restart of the service seems to then result in database error and the service failing to be able to run. GRANDPA voter error: could not complete a round on disk: Database error: Background worker error: Compression error Dec 20 15:42:06 phost01 polkadot[15579]: 2024-12-20 15:42:06 Report 12D3KooWSKN2LWthvaNoF31CShhUb954KsrRVhwn6R5wxgzgqwJT: -2147483648 to -2147483648. Reason: A collator provided a collation for the wrong para. Banned, disconnecting. |
So this happened again @infrachris? It looks like because of the segfault the database is not written correctly to disk. We still need to find out what the segfault happens. Can you at least get us a crashdump? |
Yes, happened again. |
FYI |
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
Node crashes and restarts with the below in the log, I've had this occur on two nodes post update to stable-2412:
systemd[1]: polkadot.service: Main process exited, code=dumped, status=11/SEGV
systemd[1]: polkadot.service: Failed with result 'core-dump'.
Logs immediately proceeding the error:
Dec 17 23:15:20 host polkadot[1288]: 2024-12-17 23:15:19 Report 12D3KooWEUxAyoPAR4es3zyznSkFawiFwDqb8kENAzcSH1DKtxrE: -2147483648 to -2147483648. Reason: A collator provided a collation for the wrong para. Banned, disconnecting.
Dec 17 23:16:12 host polkadot[1288]: 2024-12-17 23:16:12 Report 12D3KooWNbNtjv24TPMoF3fgxSJ9vtdp7g9eG74DiWt6aNdgCh97: -2147483648 to -2147474548. Reason: A collator provided a collation for the wrong para. Banned, disconnecting.
Dec 17 23:16:12 host polkadot[1288]: 2024-12-17 23:16:12 Report 12D3KooWP4gxZf4YdsiKGAdtQ14T2auE2NVoTx4gRjXvXCpf1WhP: -2147483648 to -2147456365. Reason: A collator provided a collation for the wrong para. Banned, disconnecting.
Dec 17 23:23:13 host polkadot[1288]: 2024-12-17 23:23:13 Report 12D3KooWQWoFP9Rhtmx4cobJVpYHqEASwicH3soJ8khN9Lvsg8FQ: -2147483648 to -2147474792. Reason: A collator provided a collation for the wrong para. Banned, disconnecting.
Dec 17 23:27:55 host polkadot[1288]: 2024-12-17 23:27:55 Report 12D3KooWAb28SE14QhAhiH83SPWqJvGRZiQDejp4NGwDvQPjQqGE: -2147483648 to -2147483648. Reason: A collator advertising a collation for an async backing relay parent using V1. Banned, disconnecting.
Dec 17 23:46:31 host polkadot[1288]: 2024-12-17 23:46:31 Report 12D3KooWPJFhYLZv2v2HBJQYPgsfLdWazDPtvcu3ci7oCj2xzyzm: -2147483648 to -2147483648. Reason: Same block request multiple times. Banned, disconnecting.
Dec 18 00:07:12 host polkadot[1288]: 2024-12-18 00:07:12 Report 12D3KooWPJFhYLZv2v2HBJQYPgsfLdWazDPtvcu3ci7oCj2xzyzm: -2147483648 to -2147483648. Reason: Same block request multiple times. Banned, disconnecting.
Only interesting error after the node starts again:
Received msg before first active leaves update. This is not expected - message will be dropped. msg=DetermineUndisputedChain
I have restart time 180 seconds.
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: