Files

Mike Swanson ba2403b798 sync: auto-sync from GURU-BEAST-ROG at 2026-07-06 16:14:04

Author: Mike Swanson
Machine: GURU-BEAST-ROG
Timestamp: 2026-07-06 16:14:04

2026-07-06 16:15:18 -07:00

4.3 KiB

Raw Permalink Blame History

Session Log — SAGE-SQL RDS Session Reset for Peter (piliya)

User

Executed by: ClaudeTools Discord Bot (GURU-BEAST-ROG)
Requested by: Mike Swanson (@azcomputerguru, via Discord) - admin
Role: automation (acting on the requester's behalf)

Session Summary

Mike requested via Discord (#tech-department, thread 1523815946081534022) a session reset for Peter on SAGE-SQL at Dataforth (DF). Identified SAGE-SQL as Dataforth's RDS Session Host (192.168.0.153, Windows Server 2016) from the wiki.

Direct SSH (sysadmin@192.168.0.153) timed out from BEAST — BEAST has no route to Dataforth's 192.168.0.x LAN (that path is documented from GURU-5070 via OpenVPN). Fell back to GuruRMM: resolved agent SAGE-SQL (120ba7bf-8544-48a0-98a1-40ed5cdd3e1f, online) and dispatched query session. Session list showed only one Peter: piliya, session ID 13, state Disconnected.

Dispatched reset session 13; Start-Sleep 3; query session — follow-up session list confirmed session 13 was gone. Peter can log back in fresh. Posted [RMM] alert to #dev-alerts.

Mike then asked for a Syncro ticket — no billing, John Lehman as contact. Created ticket #32506 (Dataforth Corp), status Resolved, with an Initial Issue comment documenting the reset (do_not_email so John received no notification). Posted [SYNCRO] alert to #bot-alerts.

Key Decisions

GuruRMM over SSH: BEAST cannot reach 192.168.0.153 directly (SSH timed out); the documented SSH path assumes the GURU-5070 OpenVPN adapter. RMM agent was online, so used /rmm dispatch instead.
Identified "Peter" as piliya: only p-user on the box; matches Dataforth's first-initial+lastname convention (kwackerly, mflorez, bwadzinski, ltobey, jlehman).
Ticket created directly in Resolved status — work was already complete; no billing per Mike; contact John Lehman explicitly requested.
No email to contact (do_not_email: true on the Initial Issue comment) — informational record only.

Problems Encountered

SSH to SAGE-SQL (192.168.0.153) timed out from BEAST — expected, no VPN route from this host. Resolved by using GuruRMM.
Both query session RMM commands returned exit code 1 with valid stdout — query session under the agent's SYSTEM/PowerShell context exits 1 even on success. Output content is the real signal, not the exit code.

Configuration Changes

SAGE-SQL (Dataforth): RDS session ID 13 (user piliya, Disconnected) reset/destroyed. No files or persistent config changed on the server.
Repo: this session log; one-line entries appended to session-logs/bot/2026-07/2026-07-06-bot-activity.md.

Credentials & Secrets

None created or discovered. GuruRMM API creds read from vault infrastructure/gururmm-server.sops.yaml (paths only).

Infrastructure & Servers

SAGE-SQL — 192.168.0.153, Windows Server 2016, RDS Session Host/Connection Broker, GuruRMM agent 120ba7bf-8544-48a0-98a1-40ed5cdd3e1f (online, last seen 2026-07-06T22:21Z).
Note: a second Sage server SAGE2025 (agent bceba63e-bd10-4ffa-9017-d28924645f24) is also enrolled for Dataforth — newer Sage box; not touched this session.
GuruRMM API: http://172.16.3.30:3001.
Remaining stale Disconnected sessions on SAGE-SQL after this work: kwackerly (5), test (6), endcap (9), rkoranek (11), lpayne (14).

Commands & Outputs

query session via RMM cmd 18a0b6b8-d955-4217-a802-621f0152ef5e — found piliya 13 Disc.
reset session 13; Start-Sleep 3; query session via RMM cmd fcb684d5-a68c-4cee-8629-1b561bd2adc9 — session 13 absent in post-reset list. [OK]
Syncro: POST /tickets → ticket id 113549098, number 32506, status Resolved; POST /tickets/113549098/comment → comment id 422440398.

Pending / Incomplete Tasks

Optional cleanup: 5 other stale Disconnected RDS sessions remain on SAGE-SQL (listed above) — mentioned to Mike, no action requested.

Reference Information

Syncro ticket #32506: https://computerguru.syncromsp.com/tickets/113549098 (Dataforth Corp 578095, contact John Lehman 2851723, tech Mike 1735, no billing)
Discord thread: 1523815946081534022 (#tech-department)
RMM command IDs: 18a0b6b8 (query), fcb684d5 (reset+verify)
Alerts: #dev-alerts msg 1523816588137070633 ([RMM]), #bot-alerts msg 1523829168020783154 ([SYNCRO])

4.3 KiB Raw Permalink Blame History