peerbit
peerbit copied to clipboard
Bootstrap node terminating at random
"level":50,"time":1710967109450,"pid":3351,"hostname":"ip-172-31-47-233","module":"lazystream","err":{"type":"AbortError","message":"Read aborted","stack":"Error: Read aborted\n at EventTarget.listener (file:///usr/lib/node_modules/@peerbit/server/node_modules/it-byte-stream/dist/src/index.js:64:28)\n at [nodejs.internal.kHybridDispatch] (node:internal/event_target:761:20)\n at EventTarget.dispatchEvent (node:internal/event_target:703:26)\n at abortSignal (node:internal/abort_controller:314:10)\n at Timeout._onTimeout (node:internal/abort_controller:120:7)\n at listOnTimeout (node:internal/timers:573:17)\n at process.processTimers (node:internal/timers:514:7)","code":"ABORT_ERR"},"msg":"Read aborted"}
Shutting down node (exit)
file:///usr/lib/node_modules/@peerbit/server/node_modules/@peerbit/stream/lib/esm/index.js:137
Seems like a node was terminated hence AbortError was thrown for all pending writes.
CPU usage was low when this happened.
Seems like a certificate renewal issue
NET::ERR_CERT_DATE_INVALID Subject: 3835c3783230009a90ae4f8acc7ee22bee09e317.peerchecker.com