Files
learning-garden/sources/psb-thinking-2026-04-09.md

131 lines
6.5 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
pageType: source
id: source.psb-thinking-2026-04-09
title: psb-thinking-2026-04-09
sourceType: local-file
sourcePath: /home/topher/.openclaw/workspace-psb-thinking/memory/2026-04-09.md
ingestedAt: 2026-05-03T01:54:23.818Z
updatedAt: 2026-05-03T01:54:23.818Z
status: active
growth: seed
---
# psb-thinking-2026-04-09
## Source
- Type: `local-file`
- Path: `/home/topher/.openclaw/workspace-psb-thinking/memory/2026-04-09.md`
- Bytes: 5963
- Updated: 2026-05-03T01:54:23.818Z
## Content
```text
# 2026-04-09 — Session Notes
## Migration: Pi → Media (CasaOS Server) Complete
### What was migrated tonight
- **OpenClaw gateway + all agents** (psb-thinking, psb-gemma, psb-business, 2890-bot, psb-hacker-claude) moved from Pi (hhs-153-pi-01) to CasaOS server (media, 100.91.1.57)
- **Telegram bot** (@PSB_Claw_bot): Pi gateway stopped, media now sole owner — 409 conflict resolved
- **DuckDNS**: Set up on media (token=c99b4fe7-ceec-4b4f-8296-bb206c180064, domain=2890.duckdns.org). Was broken on Pi for ~3 weeks. Updates every 5 min via cron. Confirmed working.
- **Port forward**: Eero still forwarding WAN:80 → Pi:8080 (needs updating to media:80 — pending, kids gaming)
- **Pi cleanup**: OpenClaw gateway disabled, DuckDNS cron removed, ~/duckdns folder deleted
### Pi SSH access gained
- Media can now SSH to Pi: `ssh -i ~/.ssh/id_media_to_pi HHS@100.99.44.24`
- Key-based auth confirmed working (ed25519)
- Pi now acts as dumb backup — safe to reboot
### Telegram 409 conflict resolution
- Root cause: Pi gateway still running after migration, conflicting with media for same bot token
- Fix: `systemctl --user disable openclaw-gateway` + `openclaw gateway stop` on Pi
- Confirmed: no more 409 errors after Pi gateway stopped
### Slowness investigation ( Ollama cloud models)
- Ollama cloud (minimax-m2.7, deepseek-v3.2:cloud) was timing out (77s) during heavy gateway restarts
- `openclaw doctor --fix` ran: installed missing plugin deps, cleared stale session locks
- All agents temporarily reverted to `claude-sonnet-4-6` for reliability
- **psb-thinking** later switched back to `ollama/minimax-m2.7` (no fallbacks) for cost reasons
- psb-gemma, psb-business, 2890-bot still on sonnet (safer default)
- Realized cost constraint: can't use Claude for all agents — need to keep Ollama cloud working
- 2890-bot has exec trust and can manage Ollama directly if needed
### OpenClaw Doctor results
- 56 plugins loaded, 0 errors
- Missing deps (Slack, WhatsApp, Twitch, Matrix, Signal) are for unused plugins — ignore
- Stale session locks cleared via `--fix`
- Gateway running on port 18789, 5 agents, Discord + Telegram both responding
### 2890 Bot / Robotics Dashboard
- 2890-bot on media with full exec trust
- Robotics dashboard (port 8080) is offline — managed by 2890-bot separately, not our problem
- HA dashboard (fridge screen) still on Pi, unaffected
### Pending
- [ ] Flip Eero port forward from Pi:8080 → media:80 (when kids done gaming)
- [ ] Re-enable minimax for psb-gemma, psb-business, 2890-bot if speed is acceptable
- [ ] Investigate Ollama cloud model slowness — was it gateway restarts compounding, or actual model issues?
## End of session (01:27 UTC)
## Session Notes (late night)
### gog Auth — postsecondarybrewing@gmail.com
- MacBook was able to run `gog auth add` with the OAuth credentials file
- Auth appeared to succeed (`gog auth list` showed the account) but NO TOKEN FILE was written to `~/Library/Application Support/gogcli/keyring/`
- Keyring dir was empty — possible permissions issue with the gog keyring on macOS
- SOLUTION: Used LinuxServer WebTop container (Docker: `linuxserver-webtop-app-1`) on media as the auth browser
- WebTop is accessible at `http://media:3000` (port 3000, KasmVNC-based)
- x86_64 Ubuntu container — installed gog directly with: `curl -sL https://github.com/steipete/gogcli/releases/download/v0.12.0/gogcli_0.12.0_linux_amd64.tar.gz | tar xz gog && chmod +x gog && mv gog /usr/local/bin/gog`
- Auth completed successfully in webtop terminal
- Copied token from container's `/config/.config/gogcli/keyring/token:default:postsecondarybrewing@gmail.com` to media's `~/.config/gogcli/keyring/`
- gog now on media at `/usr/local/bin/gog.real` (binary) with wrapper at `/usr/local/bin/gog` that auto-sets `GOG_KEYRING_PASSWORD=rm153`
- Both `hawkcollective@gmail.com` and `postsecondarybrewing@gmail.com` accounts fully working
- Sheets: ✅ works. Docs: ❌ 403 — Google Docs API not enabled on `brewery-assistant` project (easy fix: visit console.developers.google.com/apis/api/docs.googleapis.com/overview?project=57290199244)
### SSH Access to Pi (brewer / 100.99.44.24)
- Generated key on media: `~/.ssh/id_media_to_pi` (ed25519)
- Pi's authorized_keys had 3 duplicate entries — cleaned with `uniq`
- Username on Pi is `HHS` (not `topher`) — once I used correct username, SSH worked
- SSH now works: `ssh -i ~/.ssh/id_media_to_pi HHS@100.99.44.24`
- Tailscale SSH doesn't work due to hostkey verification issues with brewer.taildc9eb.ts.net
### Cron Migration: Pi → Media
- rsync'd all scripts from Pi (`HHS@100.99.44.24:~/.openclaw/scripts/`) to media (`/home/topher/.openclaw/scripts/`)
- 63 scripts transferred
- Installed 20 cron jobs on media (migrated from Pi crontab)
- Skipped: 2890-bot crons (robotics team), fridge kiosk refresh (media uses different approach)
- All logs go to `/home/topher/.openclaw/logs/`
- Scripts will need path/API key validation before running correctly on media
### WebTop
- LinuxServer WebTop container (port 3000-3001) on media
- Full desktop environment with browser — useful for OAuth flows that need a browser on remote machines
- Used it to complete gog OAuth without needing to tunnel
## GPU Upgrade (pending)
- Ordered 10GB GPU from eBay (2026-04-08/09)
- ETA: "a couple of days"
- Plan: limp along with slow Ollama CPU embeddings until card arrives
- Next step: reconfigure Ollama for GPU acceleration once card is installed
- Hardware: Intel i7-2600K (8 threads @ 3.4GHz) — current CPU bottleneck
- CasaOS server (media, 100.91.1.57) — GPU will slot into this machine
## Memory Search Status
- Ollama embeddings are CPU-bound (401% CPU during embedding = all 8 threads)
- 120s batch timeout too short: ~10 chunks × 5-21s each = 50-210s
- Memory search: DISABLED for now — re-enable after GPU upgrade
- Config preserved: memorySearch with ollama/nomic-embed-text + remote.baseUrl
```
## Notes
<!-- openclaw:human:start -->
<!-- openclaw:human:end -->
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->