You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the node encounters an error, that error is bubbled up to the highest level of async, where we then initiate our graceful shutdown logic for the node. This graceful shutdown logic is supposed to log the error, generate a crash report, and shut things down in a more graceful manner. However, we are seeing that it doesn't always do this well: there seems to be some code paths in which the error will not actually get logged sufficiently before the shutdown finishes. We just end up with logs that say graceful shutdown has started with no other information.
Below is an example of what this looks like in the logs (no error or useful information prior to this).
{"timestamp":"2024-04-21 10:57:00.890593Z","level":"Info","source":{"module":"Exit_handlers","location":"File \"src/lib/exit_handlers/exit_handlers.ml\", line 31, characters 4-15"},"message":"Running async shutdown handler: $description","metadata":{"description":"Close transition frontier, if exists","host":"46.4.27.171","peer_id":"12D3KooWBtktgL7kvikZScEAioJpv36DVx6vBMECKbMRWc25rT5R","pid":18,"port":8302}}
{"timestamp":"2024-04-21 10:57:00.890632Z","level":"Info","source":{"module":"Exit_handlers","location":"File \"src/lib/exit_handlers/exit_handlers.ml\", line 31, characters 4-15"},"message":"Running async shutdown handler: $description","metadata":{"description":"Remove daemon lockfile","host":"46.4.27.171","peer_id":"12D3KooWBtktgL7kvikZScEAioJpv36DVx6vBMECKbMRWc25rT5R","pid":18,"port":8302}}
The text was updated successfully, but these errors were encountered:
When the node encounters an error, that error is bubbled up to the highest level of async, where we then initiate our graceful shutdown logic for the node. This graceful shutdown logic is supposed to log the error, generate a crash report, and shut things down in a more graceful manner. However, we are seeing that it doesn't always do this well: there seems to be some code paths in which the error will not actually get logged sufficiently before the shutdown finishes. We just end up with logs that say graceful shutdown has started with no other information.
Below is an example of what this looks like in the logs (no error or useful information prior to this).
The text was updated successfully, but these errors were encountered: