openclaw - 💡(How to fix) Fix Isolated cron jobs fail: 'Unable to resolve plugin runtime module' on ARM64 Pi 5 [1 participants]

[message-action-discovery] telegram.actions.describeMessageTool failed: Error: Unable to resolve plugin runtime module at resolveCreatePluginRuntime (pi-embedded-CbCYZxIb.js:149430:33) at resolveRuntime (pi-embedded-CbCYZxIb.js:149438:23) at Object.describeMessageTool (telegram-CcmyE7TJ.js:135:52)

cron: disabling one-shot job after error — reason: permanent error

Fix Plan

The fix involves ensuring the correct Node version is used for cron jobs and resolving the plugin runtime module issue.

Here are the steps:

• Update the package.json to include the required @lancedb/lancedb package:

"dependencies": {
  "@lancedb/lancedb": "^1.0.0"
}

• Run npm install or yarn install to install the dependencies.
• Update the cron job to use the correct Node version by modifying the shebang line in the cron script to point to the correct Node version (v24.14.0):

#!/usr/bin/env node --version=v24.14.0

Alternatively, you can set the NODE_VERSION environment variable before running the cron job:

NODE_VERSION=v24.14.0 node your_cron_job.js

• If using a systemd service, update the ExecStart line to use the correct Node version:

ExecStart=/usr/bin/env node --version=v24.14.0 /path/to/your_cron_job.js

Verification

To verify the fix, run the cron job manually and check the logs for any errors. If the job completes successfully, the issue is resolved. You can also check the cron list output to ensure that the jobs are no longer in an error state.

Extra Tips

• Ensure that the @lancedb/lancedb package is compatible with your OpenClaw version.
• If you're using a different package manager like yarn, make sure to update the yarn.lock file accordingly.
• Consider setting the NODE_VERSION environment variable globally to avoid version conflicts in the future.