openclaw - 💡(How to fix) Fix Gateway crash: unhandled promise rejection at server.impl-D5mN3W3v.js:2050 under event-loop pressure [1 comments, 2 participants]

Unhandled promise rejection at server.impl-D5mN3W3v.js:2050 (Cannot read properties of undefined (reading 'error')) crashes the gateway process under heavy event-loop pressure. systemd auto-restarts, the new instance hits the same condition, and we get a restart loop until the underlying pressure is resolved. Either the rejection is handled (logged + recovered) or, if truly fatal, the process exits with a clear diagnostic instead of a generic undefined.error access.

TL;DR

Add a defensive null-check at server.impl-D5mN3W3v.js:2050 and implement a top-level process.on('unhandledRejection') handler to prevent the gateway process from crashing due to unhandled promise rejections.

Guidance

• Implement a null-check for the error property at server.impl-D5mN3W3v.js:2050 to prevent the Cannot read properties of undefined error.
• Add a process.on('unhandledRejection') event handler to catch and log unhandled promise rejections, providing more informative error messages.
• Review the DNS pathology causing getaddrinfo AAAA queries to hang and consider optimizing or caching DNS lookups to reduce system-prompt assembly time.
• Analyze the stability/openclaw-stability-2026-05-01T19-22-05-735Z-2265767-unhandled_rejection.json log for more insights into the rejection context.

Example

process.on('unhandledRejection', (reason, promise) => {
  console.error('Unhandled Rejection at:', promise, 'reason:', reason);
  // Additional logging or recovery logic can be added here
});

Notes

The suggested fix focuses on handling the unhandled promise rejection and providing more informative error messages. However, addressing the underlying DNS pathology and optimizing system-prompt assembly may require further investigation and changes.

Recommendation

Apply the suggested workaround by adding a defensive null-check and implementing a process.on('unhandledRejection') handler, as this will provide more informative error messages and prevent the gateway process from crashing due to unhandled promise rejections.