Gladex Agent Logs
Agent run logs & app logs · env: prod · LAN-only investor surface
Overview
| Run logs | 1603 files, 116.2 MB |
| Latest run log | run-20261014-201639-1137.log |
| Log directory | /data/agent-logs |
| App log directory | /opt/startup/prod/logs |
Run logs (newest first, last 50)
| File | Size | Modified (UTC) |
|---|---|---|
| run-20261014-201639-1137.log | 322 KB | 2026-10-14 18:51:18 |
| run-20261014-174154-1136.log | 835 KB | 2026-10-14 18:06:28 |
| run-20261014-170319-1135.log | 320 KB | 2026-10-14 15:31:41 |
| run-20261014-161418-1134.log | 270 KB | 2026-10-14 14:53:09 |
| run-20261014-150444-1133.log | 323 KB | 2026-10-14 14:04:07 |
| run-20261014-133301-1132.log | 340 KB | 2026-10-14 12:54:34 |
| run-20261014-124552-1131.log | 194 KB | 2026-10-14 11:22:49 |
| run-20261014-103913-1130.log | 525 KB | 2026-10-14 10:35:42 |
| run-20261014-082946-1129.log | 630 KB | 2026-10-14 08:29:02 |
| run-20261014-061713-1128.log | 454 KB | 2026-10-14 06:19:36 |
| run-20261014-052042-1127.log | 96 KB | 2026-10-14 04:07:02 |
| run-20261014-044319-1126.log | 200 KB | 2026-10-14 03:10:30 |
| run-20261014-032502-1125.log | 531 KB | 2026-10-14 02:33:08 |
| run-20261014-024815-1124.log | 214 KB | 2026-10-14 01:14:52 |
| run-20261014-020537-1123.log | 283 KB | 2026-10-14 00:38:05 |
| run-20261014-015526-1122.log | 154 B | 2026-10-13 23:55:27 |
| run-20261014-014514-1121.log | 191 B | 2026-10-13 23:45:15 |
| run-20261014-013503-1120.log | 191 B | 2026-10-13 23:35:04 |
| run-20261014-012452-1119.log | 154 B | 2026-10-13 23:24:53 |
| run-20261014-011441-1118.log | 154 B | 2026-10-13 23:14:42 |
| run-20261014-010430-1117.log | 154 B | 2026-10-13 23:04:31 |
| run-20261014-005419-1116.log | 154 B | 2026-10-13 22:54:20 |
| run-20261014-004409-1115.log | 154 B | 2026-10-13 22:44:09 |
| run-20261014-003358-1114.log | 154 B | 2026-10-13 22:33:58 |
| run-20261014-002347-1113.log | 154 B | 2026-10-13 22:23:48 |
| run-20261014-001336-1112.log | 154 B | 2026-10-13 22:13:37 |
| run-20261014-000325-1111.log | 154 B | 2026-10-13 22:03:25 |
| run-20261013-235314-1110.log | 154 B | 2026-10-13 21:53:15 |
| run-20261013-234303-1109.log | 154 B | 2026-10-13 21:43:04 |
| run-20261013-233139-1108.log | 159 KB | 2026-10-13 21:32:53 |
| run-20261013-225919-1107.log | 255 KB | 2026-10-13 21:21:29 |
| run-20261013-222935-1106.log | 191 KB | 2026-10-13 20:49:08 |
| run-20261013-214526-1105.log | 128 KB | 2026-10-13 20:19:24 |
| run-20261013-203244-1104.log | 264 KB | 2026-10-13 19:35:16 |
| run-20261013-195951-1103.log | 283 KB | 2026-10-13 18:22:34 |
| run-20261013-192444-1102.log | 95 KB | 2026-10-13 17:49:40 |
| run-20261013-171515-1101.log | 585 KB | 2026-10-13 17:14:33 |
| run-20261013-161458-1100.log | 250 KB | 2026-10-13 15:05:05 |
| run-20261013-153047-1099.log | 183 KB | 2026-10-13 14:04:48 |
| run-20261013-144509-1098.log | 171 KB | 2026-10-13 13:20:37 |
| run-20261013-141129-1097.log | 228 KB | 2026-10-13 12:34:59 |
| run-20261013-123439-1096.log | 494 KB | 2026-10-13 12:01:17 |
| run-20261013-111017-1095.log | 471 KB | 2026-10-13 10:24:29 |
| run-20261013-102815-1094.log | 208 KB | 2026-10-13 09:00:06 |
| run-20261013-095340-1093.log | 162 KB | 2026-10-13 08:18:04 |
| run-20261013-075349-1092.log | 458 KB | 2026-10-13 07:43:30 |
| run-20261013-064410-1091.log | 387 KB | 2026-10-13 05:43:38 |
| run-20261013-052913-1090.log | 255 KB | 2026-10-13 04:34:00 |
| run-20261013-045151-1089.log | 191 KB | 2026-10-13 03:19:02 |
| run-20261013-040348-1088.log | 266 KB | 2026-10-13 02:41:41 |
Tail — run-20261014-201639-1137.log (last 200 lines)
<!DOCTYPE html> <html lang="en"> <head> dev follow: 200 final=https://dev.gladex.de/investor <!DOCTYPE html> <html lang="en"> <head> > build · mimo-v2.6-flash-free Both background suites still running. Let me run the gladex monitor pre-commit (expected: A3/A15 dirty-tree reds, A4–A8 queue-source green since the CHANGELOG entry is already appended on disk). [0m$ [0mbash tests/test_gladex_monitor.sh > /tmp/opencode/run1137/monitor_pre.log 2>&1; echo "monitor rc=$?"; tail -5 /tmp/opencode/run1137/monitor_pre.log monitor rc=1 FAIL A32 the committed tree reached dev AND prod (kind=contains key=sync want=in sync) assertions: 28 passed: 17 failed: 11 summary: 28 assertions, 17 passed, 11 failed > build · mimo-v2.6-flash-free [0m$ [0mgrep -E "^(PASS|FAIL)" /tmp/opencode/run1137/monitor_pre.log | grep -E "A3|A4|A5|A6|A7|A8|A15|A31|A32" FAIL A3 tree clean AND in sync with origin/main (kind=is key=git want=## main...origin/main) FAIL A4 queue-source-check exits 0 (kind=rc key=qsc want=0) FAIL A5 queue has exactly one home (kind=contains key=qsc want=queue-source-check: OK - one queue:) FAIL A6 newest CHANGELOG queue is pointer-only (kind=contains key=qsc want=pointer-only) FAIL A7 queue-source-check json exits 0 (kind=rc key=qscj want=0) FAIL A8 queue-source-check reports no violations (kind=contains key=qscj want="violations": []) FAIL A15 git-tree reports a clean tree (kind=contains key=sys want=[OK] clean) FAIL A30 no unit is left in systemctl --failed (kind=contains key=sys want=[OK] 0 failed unit(s)) FAIL A31 source-sync-check exits 0 (kind=rc key=sync want=0) FAIL A32 the committed tree reached dev AND prod (kind=contains key=sync want=in sync) > build · mimo-v2.6-flash-free [0m$ [0mtail -12 /tmp/opencode/run1137/figread.log PASS: V16a regression-run: figure 350 and suite tests/test_regression_run.sh both read off the section PASS: V16b regression-run: the registry's figure equals what tests/test_regression_run.sh produced (child rc=0) PASS: V17a system-status: figure 26 and suite tests/test_system_status_unread.sh both read off the section PASS: V17b system-status: the registry's figure equals what tests/test_system_status_unread.sh produced (child rc=0) PASS: V18a repo-lint: figure 487 and suite tests/test_repo_lint.sh both read off the section PASS: V18b repo-lint: the registry's figure equals what tests/test_repo_lint.sh produced (child rc=0) PASS: V9 accounting, last assertion in the file: V1 + sixteen figure/child pairs = 33 assertions from section V V: 16 child suites run, 16 sections covered === Results: 43 passed, 1 failed === rc=1 [0m$ [0mcd /data/repo && tools/queue-source-check; echo "qsc rc=$?" queue-source-check: FAIL - 1 violation(s): [0.4.350] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file - [0.4.350] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file qsc rc=1 > build · mimo-v2.6-flash-free [0m$ [0mgrep -E "^FAIL" /tmp/opencode/run1137/figread.log; grep -E "CENSUS" /tmp/opencode/run1137/figread.log FAIL: V14b shift-deploy: the registry's figure equals what tests/test_shift_deploy.sh produced (child rc=0) (want=132 got=127) CENSUS: 18 section(s) carry a **N assertions** figure; 17 read, 1 unread CENSUS-read:alpha budget-show disk-show dns-verify domain-availability-check immich-roundtrip ip-drift-check ip-drift-cron pdns-api.py promote-dev-to-prod regression-run repo-lint shift-deploy smtp-relay-probe source-sync-check system-status test_identity_wrapper.sh test_registry_coverage.sh CENSUS-unread: test_registry_figure_readers.sh > build · mimo-v2.6-flash-free Both background suites are red only on the known pre-existing drift plus the pre-commit queue-state check — no red from my change: - figure-readers: 43/1 (V14b shift-deploy 132 vs 127 — measured pre-existing by run 959), and my `attribution-gap` section isn't in the figure-reader census (no `**N assertions**` line, so nothing to reconcile). - queue-source-check: 1 violation — `[0.4.350] is not named in agent-logs/PROGRESS.md`, exactly what the entry fixes. Writing the PROGRESS entry now. [0m→ [0mRead repo/agent-logs/PROGRESS.md [90m[offset=19180, limit=50][0m > build · mimo-v2.6-flash-free [0m✱ [0mGrep "^## Builder — run (95[5-9]|960)" [90min repo/agent-logs/PROGRESS.md · 5 matches[0m [0m$ [0mwc -l /data/repo/agent-logs/PROGRESS.md 19455 /data/repo/agent-logs/PROGRESS.md > build · mimo-v2.6-flash-free [0m→ [0mRead repo/agent-logs/PROGRESS.md [90m[limit=40, offset=19419][0m > build · mimo-v2.6-flash-free [0m→ [0mRead repo/agent-logs/PROGRESS.md [90m[limit=3, offset=19417][0m [0m$ [0mcd /data/repo echo "=== git status / HEAD ==="; git status --porcelain; git log --oneline -1 echo "=== attribution-gap live readings ===" /usr/bin/time -f "bare: %es" tools/attribution-gap 2>&1 | tail -4 echo "--- rc of bare: $? (see separate) ---" /usr/bin/time -f "all: %es" tools/attribution-gap --all 2>&1 | tail -3 === git status / HEAD === M CHANGELOG.md M tests/test_attribution_gap.sh M tools/REGISTRY.md M tools/attribution-gap 156d9d3 run 1136: 2026-10-14T18:06Z model=opencode/mimo-v2.6-flash-free === attribution-gap live readings === attribution-gap repo=/data/repo since=7 days ago window-day=2026-10-07 7 transcript(s), 56 `identity .. shift` commit date(s) no attribution gap: every transcript touch-date is covered by an `identity <id> shift` commit bare: 0.67s --- rc of bare: 0 (see separate) --- 7 transcript(s), 143 `identity .. shift` commit date(s) no attribution gap: every transcript touch-date is covered by an `identity <id> shift` commit all: 0.64s > build · mimo-v2.6-flash-free [0m$ [0mtail -4 /tmp/opencode/run1137/regcov.log PASS: C33j nothing about the count moved, so figure_stale stayed 0 PASS: C33k plant: the Live line still carries its suite figure PASS: C33l plant: and that figure is the live claim, not a new number PASS: C33m plant: while its date is gone [0m$ [0mgrep -n "builder run 960\|run 960" /data/agent-logs/*.log 2>/dev/null | tail -3; echo "---"; systemctl list-timers 'identity-run@lena.timer' --no-pager 2>/dev/null | head -3 /data/agent-logs/run-20261014-201639-1137.log:2447:+Window fixed ✅ 2026-10-14 (run 960, `[0.4.349]`'s queued step): the window now /data/agent-logs/run-20261014-201639-1137.log:2458:## [0.4.350] - 2026-10-14 — run 960 takes run 959's priced queue: `attribution-gap`'s window now opens on a DAY boundary, so the default reading and `--all` agree by construction instead of by where the clock sits inside a day — suite **58 → 80**, and the false pass the new case exposed (an unreadable history reported as `no attribution gap`) is refused too /data/agent-logs/run-20261014-201639-1137.log:2478:10759:## [0.4.350] - 2026-10-14 — run 960 takes run 959's priced queue: `attribution-gap`'s window now opens on a DAY boundary, so the default reading and `--all` agree by construction instead of by where the clock sits inside a day — suite **58 → 80**, and the false pass the new case exposed (an unreadable history reported as `no attribution gap`) is refused too --- NEXT LEFT LAST PASSED UNIT ACTIVATES Thu 2026-10-15 08:05:53 CEST 11h Wed 2026-10-14 18:05:37 CEST 2h 44min ago identity-run@lena.timer identity-run@lena.service > build · mimo-v2.6-flash-free [0m$ [0mcd /data/repo echo "=== regcov summary ==="; grep -nE "^(assertions:|passed:|failed:|summary:)" /tmp/opencode/run1137/regcov.log; grep -nE "figure_stale|violations" /tmp/opencode/run1137/regcov.log | tail -3 echo "=== figread summary ==="; grep -nE "=== Results|^rc=" /tmp/opencode/run1137/figread.log echo "=== attribution suite summary ==="; grep -nE "^(assertions:|passed:|failed:|summary:)" /tmp/opencode/run1137/ag_suite3.log; grep -nE "^=== |passed, .* failed" /tmp/opencode/run1137/ag_suite3.log | tail -3 echo "=== old-control negative control ==="; grep -nE "passed, .* failed" /tmp/opencode/run1137/ag_old2.log | tail -2 === regcov summary === 206:PASS: C31i VIOLATION figure_stale 114 - the one and only finding 232:PASS: C33j nothing about the count moved, so figure_stale stayed 0 252:PASS: C34l and figure_stale stayed 0 (only the date was removed) === figread summary === 51:=== Results: 43 passed, 1 failed === 52:rc=1 === attribution suite summary === 63:=== I: mutations (each precondition-asserted, each must diverge) === 85:=== J: the live box (/data/repo), race-safe === 92:attribution-gap suite: 80 passed, 0 failed === old-control negative control === 103:attribution-gap suite: 61 passed, 12 failed [0m$ [0mcd /data/repo echo "=== suite-count claim 114 ==="; ls tests/test_* 2>/dev/null | wc -l echo "=== red-watch last tick ==="; tail -2 agent-logs/red-watch-ALERTS.log 2>/dev/null || echo "no red-watch log at that path"; ls agent-logs/ | grep -i redwatch | head === suite-count claim 114 === 114 === red-watch last tick === no red-watch log at that path > build · mimo-v2.6-flash-free [0m$ [0mcd /data/repo echo "=== regcov tail ==="; tail -20 /tmp/opencode/run1137/regcov.log echo "=== red-watch location ==="; ls -la agent-logs/ | grep -iE "red|watch" | head; ls /data/agent-logs/ 2>/dev/null | grep -iE "red|watch" | head === regcov tail === PASS: C34g exactly one violation - the plant, and nothing else PASS: C34h fig_undated counted it once PASS: C34i and the DIAG names the line rather than leaving its text empty PASS: C34j and that text really carries the word Live, i.e. an indented line is READ not merely counted PASS: C34k the singular-count reader still sees one Live figure - widening one reader did not move another PASS: C34l and figure_stale stayed 0 (only the date was removed) PASS: C35a plant: an indented Live claim line carrying a suite figure is present PASS: C35b plant: and it reuses the figure the real claim already carries PASS: C35c plant: and the OLD ^- Live spelling cannot see it, so it could never have been counted PASS: C35d a second LIVE claim line -> exit 1 PASS: C35e VIOLATION figure_duplicate live PASS: C35f exactly one violation - the count, and nothing else PASS: C35g fig_live counted both claims PASS: C35h fig_undated stayed 0 - the plant carries a date, so the undated rule had nothing to say PASS: C35i figure_stale stayed 0 - the reused figure matches what the tool discovers PASS: C35j and the helper the controls read back agrees with the checker: two figure lines PASS: C36a non-vacuity: the definition line was read from this suite PASS: C36b plant-prep: dropping the bold group yields a different, non-empty line PASS: C36c plant: the registry copy no longer carries the definition's bytes PASS: C36d plant: while the suite copy in the same sandbox still does - one-sided drift === red-watch location === -rw-r--r-- 1 root root 7166 Oct 11 02:18 identity-shift-red-modes-2026-10-11.md red-watch-20261002.log red-watch-20261003.log red-watch-20261004.log red-watch-20261005.log red-watch-20261006.log red-watch-20261007.log red-watch-20261008.log red-watch-20261009.log red-watch-20261010.log red-watch-20261011.log > build · mimo-v2.6-flash-free [0m$ [0mcd /data/repo echo "=== regcov last lines by tail bytes ==="; tail -c 400 /tmp/opencode/run1137/regcov.log; echo echo "=== any summary/rc line ==="; grep -nE "rc=[0-9]|^=== Results|summary:" /tmp/opencode/run1137/regcov.log | tail -5 echo "=== red-watch tail (prod path) ==="; tail -3 /data/agent-logs/red-watch-20261014.log 2>/dev/null || echo "no 20261014 file yet" === regcov last lines by tail bytes === d gloss stays silent because the DEFINITION did not move PASS: C36h and this suite's own --help is NOT blamed for a document that drifted PASS: C36i nor the comment above the definition PASS: C36j non-vacuity: all THREE renderings were compared, not two PASS: C36k plant: the definition line in the suite copy now carries the mutant PASS: C36l plant: and the original definition line is gone from it === any summary/rc line === === red-watch tail (prod path) === 2026-10-14T18:15:01Z state=red monitor_exit=1 passed=23 failed=5 alert=RED-SET fails="FAIL A3 tree clean AND in sync with origin/main (kind=is key=git want=## main...origin/main) | FAIL A12 system-status verdict - checks in error: failed-units (kind=is key=sysverdict want=HEALTHY) | FAIL A30 no unit is left in systemctl --failed (kind=contains key=sys want=[OK] 0 failed unit(s)) | FAIL A31 source-sync-check exits 0 (kind=rc key=sync want=0) | FAIL A32 the committed tree reached dev" 2026-10-14T18:30:01Z state=red monitor_exit=1 passed=22 failed=6 alert=RED-SET fails="FAIL A3 tree clean AND in sync with origin/main (kind=is key=git want=## main...origin/main) | FAIL A12 system-status verdict - checks in error: failed-units (kind=is key=sysverdict want=HEALTHY) | FAIL A15 git-tree reports a clean tree (kind=contains key=sys want=[OK] clean) | FAIL A30 no unit is left in systemctl --failed (kind=contains key=sys want=[OK] 0 failed unit(s)) | FAIL A31 source-sync-" 2026-10-14T18:45:02Z state=red monitor_exit=1 passed=17 failed=11 alert=RED-SET fails="FAIL A3 tree clean AND in sync with origin/main (kind=is key=git want=## main...origin/main) | FAIL A4 queue-source-check exits 0 (kind=rc key=qsc want=0) | FAIL A5 queue has exactly one home (kind=contains key=qsc want=queue-source-check: OK - one queue:) | FAIL A6 newest CHANGELOG queue is pointer-only (kind=contains key=qsc want=pointer-only) | FAIL A7 queue-source-check json exits 0 (kind=rc k" > build · mimo-v2.6-flash-free [0m$ [0mdate; date -u; echo "--- regcov log mtime + process ---"; ls -la --time-style=full-iso /tmp/opencode/run1137/regcov.log; ps -eo pid,etime,cmd 2>/dev/null | grep -E "test_registry_coverage" | grep -v grep | head; echo "--- red-watch next tick due ---"; systemctl list-timers 'gladex-red-watch.timer' --no-pager 2>/dev/null | head -3 Wed Oct 14 20:50:59 CEST 2026 Wed Oct 14 18:50:59 UTC 2026 --- regcov log mtime + process --- -rw-r--r-- 1 root root 18807 2026-10-14 20:50:52.976489654 +0200 /tmp/opencode/run1137/regcov.log 2312523 08:38 /usr/bin/bash -c cd /data/repo && mkdir -p /tmp/opencode/run1137 && (bash tests/test_registry_coverage.sh > /tmp/opencode/run1137/regcov.log 2>&1; echo "rc=$?" >> /tmp/opencode/run1137/regcov.log) 2312528 08:38 /usr/bin/bash -c cd /data/repo && mkdir -p /tmp/opencode/run1137 && (bash tests/test_registry_coverage.sh > /tmp/opencode/run1137/regcov.log 2>&1; echo "rc=$?" >> /tmp/opencode/run1137/regcov.log) 2312529 08:38 bash tests/test_registry_coverage.sh 2529798 00:06 bash tests/test_registry_coverage.sh 2529799 00:06 bash /data/repo/tests/test_registry_coverage.sh --- red-watch next tick due --- NEXT LEFT LAST PASSED UNIT ACTIVATES 0 timers listed. > build · mimo-v2.6-flash-free The regcov suite is still finishing. Let me wait for it to complete before writing the entry with its figure.
Select another run log from the list above. Only files matching run-YYYYMMDD-HHMMSS-N.log are readable.
App log tail — prod-8001.log (last 60 lines)
[Wed Oct 14 20:47:33 2026] 127.0.0.1:58338 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58338 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58346 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58346 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58348 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58348 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58358 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58358 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58370 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58370 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58384 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58384 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58398 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58398 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58400 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58400 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58410 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58410 Closing [Wed Oct 14 20:47:33 2026] 127.0.0.1:58412 Accepted [Wed Oct 14 20:47:33 2026] 127.0.0.1:58412 Closing [Wed Oct 14 20:47:34 2026] 127.0.0.1:58424 Accepted [Wed Oct 14 20:47:34 2026] 127.0.0.1:58424 Closing [Wed Oct 14 20:47:34 2026] 127.0.0.1:58428 Accepted [Wed Oct 14 20:47:34 2026] 127.0.0.1:58428 Closing [Wed Oct 14 20:47:34 2026] 127.0.0.1:58442 Accepted [Wed Oct 14 20:47:34 2026] 127.0.0.1:58442 Closing [Wed Oct 14 20:47:34 2026] 127.0.0.1:58446 Accepted [Wed Oct 14 20:47:34 2026] 127.0.0.1:58446 Closing [Wed Oct 14 20:47:34 2026] 127.0.0.1:58460 Accepted [Wed Oct 14 20:47:34 2026] 127.0.0.1:58460 Closing [Wed Oct 14 20:47:34 2026] 127.0.0.1:58474 Accepted [Wed Oct 14 20:47:34 2026] 127.0.0.1:58474 Closing [Wed Oct 14 20:47:35 2026] 127.0.0.1:36208 Accepted [Wed Oct 14 20:47:35 2026] 127.0.0.1:36208 Closing [Wed Oct 14 20:47:35 2026] 127.0.0.1:36216 Accepted [Wed Oct 14 20:47:35 2026] 127.0.0.1:36216 Closing [Wed Oct 14 20:47:35 2026] 127.0.0.1:36218 Accepted [Wed Oct 14 20:47:35 2026] 127.0.0.1:36218 Closing [Wed Oct 14 20:47:35 2026] 127.0.0.1:36232 Accepted [Wed Oct 14 20:47:35 2026] 127.0.0.1:36232 Closing [Wed Oct 14 20:47:35 2026] 127.0.0.1:36238 Accepted [Wed Oct 14 20:47:35 2026] 127.0.0.1:36238 Closing [Wed Oct 14 20:47:36 2026] 127.0.0.1:36242 Accepted [Wed Oct 14 20:47:36 2026] 127.0.0.1:36242 Closing [Wed Oct 14 20:47:36 2026] 127.0.0.1:36256 Accepted [Wed Oct 14 20:47:36 2026] 127.0.0.1:36256 Closing [Wed Oct 14 20:47:36 2026] 127.0.0.1:36270 Accepted [Wed Oct 14 20:47:36 2026] 127.0.0.1:36270 Closing [Wed Oct 14 20:47:36 2026] 127.0.0.1:36272 Accepted [Wed Oct 14 20:47:36 2026] 127.0.0.1:36272 Closing [Wed Oct 14 20:47:36 2026] 127.0.0.1:36278 Accepted [Wed Oct 14 20:47:36 2026] 127.0.0.1:36278 Closing [Wed Oct 14 20:47:51 2026] 127.0.0.1:41064 Accepted [Wed Oct 14 20:47:51 2026] 127.0.0.1:41064 Closed without sending a request; it was probably just an unused speculative preconnection [Wed Oct 14 20:47:51 2026] 127.0.0.1:41064 Closing [Wed Oct 14 20:47:53 2026] 127.0.0.1:41074 Accepted [Wed Oct 14 20:47:53 2026] 127.0.0.1:41074 Closed without sending a request; it was probably just an unused speculative preconnection [Wed Oct 14 20:47:53 2026] 127.0.0.1:41074 Closing [Wed Oct 14 20:52:22 2026] 127.0.0.1:49028 Accepted
Other app logs: downloads.log
Generated 2026-10-14 18:52:22 UTC · Gladex.de