openclaw - 💡(How to fix) Fix [Bug]: Bonjour advertiser stalling triggers Gateway self-healing loop with log flooding [1 participants]

[2026-04-08T03:51:31.124+08:00] WARN: restarting advertiser (service stuck in announcing for 16853ms) [2026-04-08T03:51:31.124+08:00] WARN: restarting advertiser (service stuck in announcing for 16853ms)

TL;DR

Add a gateway.bonjour.enabled config option to allow disabling bonjour advertising to prevent Gateway from repeatedly restarting the advertiser when mDNSResponder gets stuck.

Guidance

• Investigate the feasibility of adding a gateway.bonjour.enabled config option to disable bonjour advertising, which could help prevent the restart loop.
• Verify that the mDNSResponder stalling is indeed the root cause of the issue by monitoring system logs and network activity during the periods when Gateway restarts the advertiser.
• Consider implementing a retry mechanism with a backoff strategy to reduce the frequency of restart attempts when the advertiser is stuck.
• Review the Gateway logs to understand the frequency and duration of the mDNSResponder stalling to determine the best approach for mitigating the issue.

Example

No code example is provided as the issue does not contain sufficient information about the Gateway's implementation details.

Notes

The suggested fix assumes that the mDNSResponder stalling is the primary cause of the issue. However, without more information about the Gateway's implementation and the underlying system configuration, it is difficult to provide a more comprehensive solution.

Recommendation

Apply workaround: Add a gateway.bonjour.enabled config option to allow disabling bonjour advertising, as this would provide a simple and effective way to prevent the restart loop and log flooding.