sync: auto-sync from HOWARD-HOME at 2026-07-18 21:02:10
Author: Howard Enos Machine: HOWARD-HOME Timestamp: 2026-07-18 21:02:10
This commit is contained in:
@@ -236,4 +236,4 @@
|
||||
- [ask-forum — human-in-the-loop via #ct-forum](../skills/ask-forum/SKILL.md) — ask a teammate a question in the private ct-forum Discord forum, get their human answer back in-session; forum-only, any human can answer, run the --wait as a proper background task
|
||||
- [Claude Code Bun crash -> pin 2.1.110](reference_claude_code_bun_crash_pin.md) - v2.1.114+ segfaults on Win11 at new-session start; npm pin 2.1.110 + DISABLE_AUTOUPDATER=1; unpin on #55219 fix
|
||||
- [GuruRMM build-server SSH key](reference_gururmm_build_server_ssh.md) — guru@172.16.3.30 key is ~/.ssh/gururmm-physical (not id_*); password fallback vault infrastructure/gururmm-server
|
||||
- [LAB-SVR retired](feedback_labsvr_retired.md) — Len's Auto LAB-SVR replaced by LAB-SERVER; never chase LAB-SVR
|
||||
- [LAB-SVR is current](feedback_labsvr_retired.md) — Len's Auto LAB-SVR is the CURRENT server (replaced old LAB-SERVER); powered back on 2026-07-18
|
||||
|
||||
@@ -1,16 +1,19 @@
|
||||
---
|
||||
name: LAB-SVR is retired — replaced by LAB-SERVER
|
||||
description: Len's Auto machine LAB-SVR was decommissioned and replaced by LAB-SERVER; never chase LAB-SVR again
|
||||
name: LAB-SVR is the CURRENT Len's Auto server (replaced LAB-SERVER)
|
||||
description: Len's Auto — LAB-SVR is the current/replacement server; LAB-SERVER is the retired one. LAB-SVR was just powered off temporarily.
|
||||
type: feedback
|
||||
---
|
||||
|
||||
Len's Auto Brokerage's **LAB-SVR was replaced by LAB-SERVER**. Do NOT investigate, probe,
|
||||
queue commands on, or report LAB-SVR as a stale/offline machine — it is retired.
|
||||
Len's Auto Brokerage: **LAB-SVR is the CURRENT server** — it REPLACED the old LAB-SERVER.
|
||||
(Direction corrected by Howard 2026-07-18; his earlier 2026-07-15 "LAB-SVR was replaced"
|
||||
was backwards — it looked retired only because it was powered off.)
|
||||
|
||||
**Why:** Howard has corrected this repeatedly ("for the last time... STOP LOOKING FOR THAT
|
||||
MACHINE", 2026-07-15). LAB-SVR still appears in stale data (GuruRMM offline agent record,
|
||||
old MSP360 plan rows), which keeps baiting audits into flagging it.
|
||||
**Why:** LAB-SVR showed offline in GuruRMM and its MSP360 backups went stale (FILES
|
||||
2026-06-17, IMAGE 2026-06-07), which made it look decommissioned. Howard went onsite
|
||||
2026-07-18 and powered it back on.
|
||||
|
||||
**How to apply:** In any backup/RMM/fleet audit, treat LAB-SVR rows as retired-machine
|
||||
residue. Check LAB-SERVER for Len's Auto server health instead. Cleanup of the stale
|
||||
LAB-SVR records (MSP360 plans/user side, RMM agent record) is the actual actionable item.
|
||||
**How to apply:** Treat LAB-SVR as a live production server: its MSP360 plans (FILES,
|
||||
IMAGE) and GuruRMM agent record are current and should be monitored. If LAB-SERVER
|
||||
residue ever appears anywhere, THAT is the retired machine. Follow-up when work resumes:
|
||||
verify LAB-SVR is back online in RMM and that its FILES/IMAGE plans run clean after the
|
||||
power-on.
|
||||
|
||||
@@ -19,6 +19,8 @@ Categories (the `[type]` tag): _(none)_ = skill/command execution failure ·
|
||||
|
||||
<!-- Append entries below this line -->
|
||||
|
||||
2026-07-19 | Howard-Home | msp360/backups | [correction] 2026-07-15 correction reversed: LAB-SVR is the CURRENT Len's Auto server (replacement FOR LAB-SERVER); it was merely powered off — Howard powered it on onsite 2026-07-18
|
||||
|
||||
2026-07-18 | Howard-Home | bug-tracker | [correction] 12 closed gururmm issues had zero fix comments — fixes were committed but tracker was never updated [ctx: ref=feedback_tracker_discipline]
|
||||
|
||||
2026-07-18 | Howard-Home | bug-tracker | [friction] tracker.py crashed on Windows with UnicodeEncodeError cp1252 when printing issue titles with unicode chars [ctx: ref=feedback_tracker_encoding]
|
||||
|
||||
@@ -11,7 +11,7 @@ MSP360 so we stop carrying and billing a dead endpoint.
|
||||
| **HIGH** | Tucson Safety and Medical | TSAM-SERVER | 2026-02-25 | 140d | A SERVER with no backup for 4.5 months. Is it still running? If yes, agent is dead — needs on-site/remote session to fix. If replaced, what took over its data? |
|
||||
| **HIGH** | Glaztech Industries | GTI-INV-VMHOST | Image 2025-10-26, Hyper-V 2025-10-28 | ~260d | VM host was pushing 60+ GB images, silent since Oct 2025. Retired? Replaced? If in service, its VMs have no image/Hyper-V protection. |
|
||||
| MED | Len's Auto | DESKTOP-BMBTQLI | Image plan NEVER ran | — | Plan was created (next start was 2026-05-03) but never executed once. Does this desktop still exist? Not in RMM. |
|
||||
| — | Len's Auto | ~~LAB-SVR~~ RETIRED | — | — | Replaced by LAB-SERVER (per Howard). Cleanup item, not a contact item: remove stale LAB-SVR plans/user from MSP360 and the dead agent record from GuruRMM. Note: no LAB-SERVER backup plans appear in MSP360 monitoring — confirm where the replacement server backs up. |
|
||||
| MED | Len's Auto | LAB-SVR | FILES 2026-06-17, IMAGE 2026-06-07 | 28-38d | CURRENT server (it replaced the old LAB-SERVER). Was powered off; Howard powered it back on onsite 2026-07-18. Follow-up: verify it's back online in GuruRMM and its FILES/IMAGE plans run clean. |
|
||||
| MED | Desert RV | DESKTOP-9T0UAON | Local Backup 2026-05-07 | 69d | Off/disconnected; consistency check stuck "Running". Still in service? |
|
||||
| LOW | Tedards | DESKTOP-SUFJR0J | 2025-07-12 (51 MB files) | 368d | Silent a full year — almost certainly retired. Confirm, then remove from MSP360 + purge/retain B2 data per retention policy. |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user