| 2026-10-31 |
gitbucket.md: 9th crawler episode (31.10 03:30 UTC) + correction of ep8 timeline (one continuous ~3.5h crawl, ~127k req)
...
9th crawler episode on gitbucket (GHard #1152, 2026-10-31 03:30 UTC, cpu 97.1%): 4x GET /root/smart-home-server/archive/devices/*.zip (3x sha 44250a7a, 1x 8a945d0d), 8x EofException/Broken pipe, java 333.7% CPU (~3 ZIP builds), load peak 7.05, no restart, self-recovered 03:31:51. Correction: ep8 did not self-extinguish 00:09 — enumeration continued ~440-480/min through 00-02 (29k req/h), one continuous crawl 23:58-03:35+, ~126.8k req total, client 192.168.1.100% 192.168.1.150, GPTBot/1.4 + Chrome/Edge 142-145 rotation. Triage: read-only ssh ubuntu@192.168.1.156 (bserv@192.168.1.130 creds) and nginx access.log on 192.168.1.183. Incident journal: workspace/incident_gitbucket_2026-10-31_ep9_crawl.md.
|
gitbucket: 8th archive-burst episode (30.10 23:57 UTC), nextcloud 61-s blip correlation confirmed twice, pending-decision counter updated
...
8th archive-burst episode 2026-10-30 23:57 UTC (panel #1136/#1137, reaction events 63c2c371 + 34367587): added episode to the list, recorded the 2nd confirmed 61-s nextcloud blip coincidence (27.10 + 30.10), updated pending-decision counter to 5 consecutive days (26–30 Oct). Sources: SSH triage on 192.168.1.156, nginx access.log on 192.168.1.183, hard-panel service_incidents.
|
gitbucket host doc: 8th archive-burst episode 2026-10-30 23:57 UTC (short burst, self-recovered ~7 min), GPTBot/1.4 crawl attribution, pending owner decision now 5 consecutive days
...
Episode 8 of the archive-burst class confirmed 2026-10-30 23:57 UTC (panel event #1136, diagnosed by navi rei via SSH + nginx logs): short burst of 20 archive/*.zip requests amid GPTBot crawl, peak load1 11.25, self-recovered ~7 min. Updates episode count, traffic-source note and pending owner decision (5 consecutive days).
|
gitbucket: 8th archive-crawler CPU episode (30.10 23:57 UTC), series 5 consecutive days
...
8th episode of the archive-crawler CPU class: 2026-10-30 23:57 UTC burst (cpu_high 91% #1136, load_high 2.11×cores #1137, cpu_recovered #1140), confirmed via read-only SSH journalctl on .156 — same /archive/*.zip signature, self-recovered in ~3.5 min. Series now 5 consecutive days (26–30 Oct).
|
| 2026-10-29 |
gitbucket: 7th archive-crawl episode (29.10, ~4.5 h sustained, self-recovered)
...
Reaction session rei on GHard event #1100 (cpu_high 90.5%, server 44 gitbucket, 2026-10-29 10:40:57 UTC). SSH triage confirmed the known archive-crawl class (7th episode since 2026-10-12) with a new signature: sustained ~4.5 h crawl 06:00–10:42 UTC, 5248 /archive/*.zip requests from 192.168.1.150 via public route, 29 Broken pipe/EofException errors, load decayed 5.07→0.66 by 10:48 UTC, self-recovered, no restart needed. Known behavior section updated with 7th episode, new signature, and owner recommendation (4 consecutive days of episodes).
|
| 2026-10-28 |
gitbucket: corrected archive-burst section — 6th episode of class, client attributed, proxy is .183 not .226
...
Correction after cross-checking memory of prior sessions: the 28.10 episode is the 6th of the /archive/*.zip class since 12.10; client already attributed (192.168.1.150 via ovpn VM SNAT, browser UA rotation; crawler UAs in 25.10 storm); actual nginx proxy is 192.168.1.183 (inventory .226 entry stale — .226 does not answer SSH/ICMP). Removed the incorrect "client IPs not identified" statement.
|
gitbucket: known behavior — load_high episodes from archive/*.zip download bursts (2026-10-26/27/28)
...
Diagnosed by navi rei during reaction to panel event #1097 (load_high 2.1x, server 44). journalctl evidence: bursts of GET /root/<repo>/archive/<path>/<sha>.zip through git.gnexus.space, clients abort (EofException/Broken pipe), GitBucket keeps building ZIPs -> java 325% CPU, load1 9.8. Self-recovered in ~90 s, HTTP 200 throughout, no restart needed. Triage recipe and pending owner decision (nginx rate-limit on .226) recorded.
|
| 2026-09-19 |
Create host doc for VM gitbucket: GitBucket + navi instance pilar (deployed 2026-09-19)
...
New navi instance pilar deployed on VM gitbucket (192.168.1.156) on 2026-09-19; host doc created per inventory creation workflow (docs field must point to an existing doc).
|