openclaw - 💡(How to fix) Fix [Bug] Windows: channel /restart fails but CLI gateway restart works [1 comments, 1 participants]

1. The restart fails with an error

Fix Plan

To fix the inconsistency between channel-triggered restart and CLI restart on Windows, we need to modify the triggerOpenClawRestart() function to preserve the environment, similar to the CLI restart.

Steps to Fix

• Modify the triggerOpenClawRestart() function to use the daemon/service manager:

// Before
public void triggerOpenClawRestart() {
    relaunchGatewayScheduledTask();
}

// After
public void triggerOpenClawRestart() {
    // Use daemon/service manager to preserve environment
    DaemonManager.getInstance().restartGateway();
}

• Update the relaunchGatewayScheduledTask() function to use the daemon/service manager as well:

// Before
public void relaunchGatewayScheduledTask() {
    // Directly restart the gateway
    // ...
}

// After
public void relaunchGatewayScheduledTask() {
    DaemonManager.getInstance().restartGateway();
}

• Ensure the DaemonManager class is properly initialized and configured to manage the gateway service.

Verification

To verify the fix, follow these steps:

• Send the /restart command via any channel (Feishu/WeChat/etc.) on a Windows platform.
• Check if the gateway restarts successfully.
• Compare the environment variables and settings before and after the restart to ensure they are preserved.

Extra Tips

• Make sure to test the fix on different Windows platforms and environments to ensure consistency.
• Consider adding logging and monitoring to track the restart process and environment variables for debugging purposes.