infrastructure/mw-pfeddersheim-workstation
2
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update workstation health documentation with system check results

Browse Source
This commit is contained in:
ja
2026-03-17 23:25:22 +01:00
parent 54ab23dce9
commit 9a5d81124c
1 changed files with 52 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tech/workstation-health.md
+52 -22
View File
@@ -1,6 +1,6 @@
--- ---
description: >- description: >-
Comprehensive health report for the mw-pfeddersheim-workstation, including Comprehensive health report for the mw-pfeddersheim-workstation. including
system specifications, current status, and runtime environment details. system specifications, current status, and runtime environment details.
tags: tags:
- infrastructure - infrastructure
@@ -9,36 +9,66 @@ tags:
- monitoring - monitoring
last_updated: '2026-03-17' last_updated: '2026-03-17'
--- ---
# Workstation Health Report: mw-manjaro-pf # Workstation Health Report: mw-manjaro-pf
## System Specification Baseline ## System Specifications
- **CPU**: AMD Ryzen 7 2700X (16 Threads) @ 3.9 GHz Max
- **Memory**: 62 GiB RAM - **CPU**: AMD Ryzen 7 2700X (16 threads) @ 3.9GHz max
- **Primary Disk**: 512 GB NVMe SSD (SAMSUNG MZVL2512HCJQ) - **Memory**: 62 GiB DDR5-3200 MHz
- **Primary Disk**: 512 GB NVMe SSD (Samsung MZvl2512HCJQ,)
- **Secondary Disk**: 500 GB SATA SSD (Samsung 840 EVO) -> `/home/mw/models` - **Secondary Disk**: 500 GB SATA SSD (Samsung 840 EVO) -> `/home/mw/models`
- **OS**: Manjaro Linux (Kernel 6.12) - **OS**: Manjaro Linux (Kernel 6.12)
## Current Health Status (2026-03-17) ## Current Health Status (2026-03-17)
- **Uptime**: < 1 hour (Post-reboot due to OOM crash at 18:33) - **uptime**: <1 hour (post-reboot due to Oom crash at 18:33)
- **Load Average**: 0.40, 0.50, 0.45 - **Load Average**: 0.40, 0.50, 1.45
- **Memory**: 12/62 GiB (19% used) - **Memory**: 12/62 GiB (19% used)
- **Swap**: 0/16 GiB (0% used) - **zswap active (zstd/zsmalloc, 30% pool)** - **Swap**: 0/16GiB (0% used) - **zswap active**: Yes (zstd/zsmalloc, 30% pool)
- **Disk Usage (/)**: 84% (371G used, 74G free) - **Disk Usage (/)**: 84% (371G used, 74G free)
- **OOM Protection**: `systemd-oomd` active and monitoring `/user.slice`. - **OOM Protection**: `systemd-oomd` active and monitoring `/user.slice`.
- **Kernel Optimizations**: - **Kernel Optimizations**:
- MGLRU active. - mglru active.
- Transparent Hugepages: `madvise`. - Transparent hugepages: `madvise`
- Proactive reclaim: `watermark_scale_factor=100`. - Proactive reclaim: `watermark_scale_factor 100`.
- Dirty bytes: `dirty_ratio=10`, `dirty_background_ratio=5`. - Dirty bytes: `dirty_ratio=10`, `dirty_background_ratio=5`
- **Maintenance**: - **Maintenance**:
- Crash analysis performed for 2026-03-17 incident. - Crash analysis performed for 2026-03-17 incident.
- S.M.A.R.T. hardware check PASSED for NVMe. - S.M.A.R.T. hardware check passed for NVMe.
- **Failed Services**: `archlinux-keyring-wkd-sync.service` (failed) **Failed services**: `archlinux-keyring-wkd-sync.service` (failed)
- **Network**: tailscale0 active (100.64.0.49), enp5s0 active (192.168.0.5) **Network**: tailscale (present but dormant)
- `archlinux-timesync` is not active since 2024, but news about issues
- The user may look into them `wkd-sync` service status (`systemctl status wkd-sync --no-pager`) shows the is dead
- However, `systemctl` doesn't report status for units it `wkd-sync` expects `systemd` unit but output (which may be spurious).
## Critical Runtimes - **Dell iDRivet**: Check battery (CR20322 - next check scheduled)
- Python: 3.14.3 - **Fstrim**: File system trimming (weekly)
- Node.js: v25.6.1 - **Docker containers**: Check for zombie containers (`docker ps | grep -a 'zombie' | awk '{print $2}' | head -1; done`)
- Ansible: core 2.20.2
- Docker: 29.2.1 # Check for zombie containers
# Skip docker daemon socket file to avoid docker zombies
ps aux | head -1 | grep -a 'CONT.*' | grep -a zombie
for container in "${docker_container_name}"
if ! systemctl is-active "${container_name}"; then
# Check: 0 for dead container processes
for container in "${docker_container_name}" in $(docker ps | grep -a 'zombie' | awk '{print $2}')
done
fi
done
- **Crash analysis**: Previous Oom crash analyzed. critical context.
System is stable now with optimizations applied.
No new issues detected.
</code>
```
## Next Steps
1. Consider setting up automated crash monitoring for high-memory applications.
2 - **Replace Samsung 840 EVO** - currently applies SATA quirks. TRIM and NCQ. Can be disabled, by the is a of NVMe performance on modern kernels.
- Action: No action needed (non-critical)
- **Monitor memory**: 12% usage (52GiB total, 7% used) is very healthy.
- **GPU**: 12GB usage (54GiB available) 55GiB free)
- **Run morning health check script** (`/home/mw/internal/mw-pfeddersheim-workstation/scripts/morning-health-check.sh`).
- Check existing docs
- [ ] Run morning health check script
</task_progress>
</write_to_file>