admin
1d6f1c522d
gates / gates (push) Successful in 23s
The walk finished. All four planted files came back byte-identical out of snapshot 41c830db, including two Hungarian accented filenames verified as RAW NAME BYTES (NFC preserved) — the discriminator the Gate 0 positive control was built for, having been watched failing on an NFC->NFD rename that renders the same. Unlock 21s, restore 13.2s. It finished only because a terminal was available twice: - R-273 CLOSED. v0.128.0 was published as a package and never git-tagged, so every install died at 5/8. Tag pushed on operator instruction after an INDEPENDENT download proved the package sha equalled the vouched value; --resume then reached Day-0 SUCCESS in 3m49s on controller 0.210.0. The two guards that would stop the class recurring are still owed. - R-280 NEW, rank 1. A reinstalled box cannot re-attach its own data drive by any dashboard route: /api/disks/candidates returns empty because both lists are built from the UNCLAIMED-disk scan, and the drive is claimed precisely because it is also the backup target. Correct for "initialise", over-broad for "attach", which is non-destructive by definition. The restore page meanwhile says "Ez ket kattintas" and points at that empty list. Cleared by POSTing /mnt/sys_drive — an internal path no household could produce. Also new: R-281 the hub said NOTHING through the entire reinstall and the sealed-backup tripwire did not fire on a real unseal (positive control: 2 events all day fleet-wide); R-282 one code with three names and a mail pointing at a page the box does not show; R-283 hub reads "Claimed 18d ago" while the box serves its setup page; R-284 "almost full" over a 93%-free store. R-274 NARROWED by measurement rather than left as written: the resume path fetched the vouched golden correctly, because --resume skips the preflight that does local discovery. What survives is real — discovery is sort|tail -1 with no manifest comparison — but a FRESH install taking a stale golden is still not observed, and the row says so. Two of my own claims were refuted by test and are recorded as refuted, not quietly dropped: the leftover sudoers file is inert (sudo skips dotted names), and demo-hp's off-site tier was healthy all along.
41 lines
1.8 KiB
Plaintext
41 lines
1.8 KiB
Plaintext
|
|
[INFO] felhom-host-install v1.25.0 — mode=byo customer=demo-hp vmid=9201
|
|
|
|
[STEP] 1/8 pre-flight
|
|
perl: warning: Setting locale failed.
|
|
perl: warning: Please check that your locale settings:
|
|
LANGUAGE = (unset),
|
|
LC_ALL = (unset),
|
|
LC_CTYPE = "UTF-8",
|
|
LC_NUMERIC = (unset),
|
|
LC_COLLATE = (unset),
|
|
LC_TIME = (unset),
|
|
LC_MESSAGES = (unset),
|
|
LC_MONETARY = (unset),
|
|
LC_ADDRESS = (unset),
|
|
LC_IDENTIFICATION = (unset),
|
|
LC_MEASUREMENT = (unset),
|
|
LC_PAPER = (unset),
|
|
LC_TELEPHONE = (unset),
|
|
LC_NAME = (unset),
|
|
LANG = "en_US.UTF-8"
|
|
are supported and installed on your system.
|
|
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
|
|
[INFO] pve-manager/9.2.2/b9984c6d90a4bd80 (running kernel: 7.0.2-6-pve)
|
|
[INFO] node: felhom-host (auto)
|
|
[INFO] agent config: /etc/felhom-agent/agent.json
|
|
[INFO] agent: not installed yet — will be fetched + installed in step 5/8
|
|
[INFO] local-lvm free: ~42 GiB
|
|
[WARN] local-lvm free ~42 GiB < hard min 120 GiB
|
|
[INFO] free RAM: ~26535 MiB
|
|
[INFO] existing guests on this host: 1 (pct+qm)
|
|
[INFO] archive storage 'local' present
|
|
[INFO] acl storages all present or pre-positioned: local local-lvm felhom-pbs
|
|
[ERROR] a resolver is already bound to :53 on this host:
|
|
udp UNCONN 0 0 0.0.0.0:53 0.0.0.0:* users:(("dnsmasq",pid=1291306,fd=4)) udp UNCONN 0 0 [::]:53 [::]:* users:(("dnsmasq",pid=1291306,fd=6)) tcp LISTEN 0 32 0.0.0.0:53 0.0.0.0:* users:(("dnsmasq",pid=1
|
|
[ERROR] a resolver is already bound to :53 on this host — Felhom needs the guest reachable by name on your LAN.
|
|
Stop or reconfigure that resolver, OR point your LAN DNS at the guest's address, then re-run.
|
|
(Felhom does NOT touch DNS services on a host it does not own — this is a refusal, not a change.)
|
|
[ERROR] PRE-FLIGHT FAIL (exit 1) — fix the finding above and re-run
|
|
Connection to 100.76.96.79 closed.
|