Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix MemOS Viewer service.start() not invoked after plugin registration [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#61355•Fetched 2026-04-08 02:59:33
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
xpp0210xpp0210
Participants
xpp0210xpp0210
Timeline (top)
cross-referenced ×1

Error Message

None found. The Viewer server.ts code looks correct (port retry, error handling) — the issue is the framework lifecycle not triggering it.

Fix Action

Workaround

None found. The Viewer server.ts code looks correct (port retry, error handling) — the issue is the framework lifecycle not triggering it.

Code Example

[plugins] memos-local: initialized (db: ~/.openclaw/memos-local/memos.db)
[plugins] memos-local: allowPromptInjection=true, auto-recall enabled

---

$ ss -tlnp | grep 18799
(empty)
RAW_BUFFERClick to expand / collapse

Bug

MemOS Local plugin registers its Viewer service via api.registerService(), but the framework never calls the service's start() method. As a result, the Memory Viewer never starts on the configured port (default 18799).

Evidence

Gateway startup logs show:

[plugins] memos-local: initialized (db: ~/.openclaw/memos-local/memos.db)
[plugins] memos-local: allowPromptInjection=true, auto-recall enabled

But there is no subsequent log indicating the Viewer HTTP server started (expected: password reset banner or listener confirmation). Port 18799 is not bound:

$ ss -tlnp | grep 18799
(empty)

Repro

  1. Install @memtensor/memos-local-openclaw-plugin with viewerPort: 18799 in openclaw.json
  2. openclaw gateway start
  3. Check logs — no Viewer startup log
  4. ss -tlnp | grep 18799 — not listening

Environment

  • OpenClaw: 2026.4.2
  • OS: Ubuntu (Linux 6.17.0)
  • Node: v22.17.1
  • Plugin: memos-local-openclaw-plugin (latest)

Expected

Framework should call service.start() after plugin registration, binding the Viewer HTTP server on the configured port.

Workaround

None found. The Viewer server.ts code looks correct (port retry, error handling) — the issue is the framework lifecycle not triggering it.

extent analysis

TL;DR

The MemOS Local plugin's Viewer service is not starting because the framework is not calling its start() method after registration.

Guidance

  • Verify that the api.registerService() call is correctly registering the Viewer service and that there are no errors in the registration process.
  • Check the framework's lifecycle hooks to ensure that the start() method is being called for all registered services.
  • Investigate the framework's configuration and logs to determine why the start() method is not being called for the Viewer service.
  • Consider adding logging or debugging statements to the Viewer service's start() method to confirm whether it is being called.

Example

No code snippet is provided as the issue seems to be related to the framework's lifecycle and not the plugin's code.

Notes

The issue seems to be specific to the interaction between the MemOS Local plugin and the OpenClaw framework, and may require changes to the framework or the plugin to resolve.

Recommendation

Apply workaround: Modify the plugin to manually start the Viewer service after registration, if possible, to ensure the Viewer HTTP server is bound to the configured port. This is a temporary solution until the underlying issue with the framework's lifecycle is resolved.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#docker error#permission error#memory optimization#batch processing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING