deployments/systemd-user-service.md defines four units and every one is Type=simple (lines 17, 36, 62, 104) with no WatchdogSec anywhere: verified by count - 4 Type= lines, 0 Type=notify, 0 WatchdogSec.
Consequence: the sd_notify support added in 2fcc32d8 has no effect as documented. systemd marks a Type=simple unit active as soon as it execs, so READY=1 is ignored; and with no WatchdogSec systemd passes no WATCHDOG_USEC, so the loop watchdog never arms (it disables itself cleanly, which is why this is silent).
To make it real the archied unit needs Type=notify and a WatchdogSec value. Value guidance from the implementing lane: healthy beats are sent at WATCHDOG_USEC/2, and a beat is licensed only while the poll marker is within the loops own poll_interval, so there are no false trips at any WatchdogSec - the cost of a larger value is detection latency, roughly poll_interval + WATCHDOG_USEC/2 + WatchdogSec (~105s at a 60s poll_interval and WatchdogSec=30s). Set NotifyAccess as required.
Scope note: apply Type=notify to the archied unit ONLY. archie-gateway and archie-state-store call markServing nowhere and emit no READY, so notifying them would time the unit out at start - see the companion bead. archie-ui is unaffected.
Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
Imported from beads archie-core-y7qc · GitHub #1120 · type bug · priority P2 · created 2026-09-21 · closed 2026-10-17
deployments/systemd-user-service.md defines four units and every one is Type=simple (lines 17, 36, 62, 104) with no WatchdogSec anywhere: verified by count - 4 Type= lines, 0 Type=notify, 0 WatchdogSec.
Consequence: the sd_notify support added in 2fcc32d8 has no effect as documented. systemd marks a Type=simple unit active as soon as it execs, so READY=1 is ignored; and with no WatchdogSec systemd passes no WATCHDOG_USEC, so the loop watchdog never arms (it disables itself cleanly, which is why this is silent).
To make it real the archied unit needs Type=notify and a WatchdogSec value. Value guidance from the implementing lane: healthy beats are sent at WATCHDOG_USEC/2, and a beat is licensed only while the poll marker is within the loops own poll_interval, so there are no false trips at any WatchdogSec - the cost of a larger value is detection latency, roughly poll_interval + WATCHDOG_USEC/2 + WatchdogSec (~105s at a 60s poll_interval and WatchdogSec=30s). Set NotifyAccess as required.
Scope note: apply Type=notify to the archied unit ONLY. archie-gateway and archie-state-store call markServing nowhere and emit no READY, so notifying them would time the unit out at start - see the companion bead. archie-ui is unaffected.
### Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
---
_Imported from beads `archie-core-y7qc` · GitHub #1120 · type bug · priority P2 · created 2026-09-21 · closed 2026-10-17_
sam
added the mediumbug labels 2026-10-27 13:41:19 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
deployments/systemd-user-service.md defines four units and every one is Type=simple (lines 17, 36, 62, 104) with no WatchdogSec anywhere: verified by count - 4 Type= lines, 0 Type=notify, 0 WatchdogSec.
Consequence: the sd_notify support added in 2fcc32d8 has no effect as documented. systemd marks a Type=simple unit active as soon as it execs, so READY=1 is ignored; and with no WatchdogSec systemd passes no WATCHDOG_USEC, so the loop watchdog never arms (it disables itself cleanly, which is why this is silent).
To make it real the archied unit needs Type=notify and a WatchdogSec value. Value guidance from the implementing lane: healthy beats are sent at WATCHDOG_USEC/2, and a beat is licensed only while the poll marker is within the loops own poll_interval, so there are no false trips at any WatchdogSec - the cost of a larger value is detection latency, roughly poll_interval + WATCHDOG_USEC/2 + WatchdogSec (~105s at a 60s poll_interval and WatchdogSec=30s). Set NotifyAccess as required.
Scope note: apply Type=notify to the archied unit ONLY. archie-gateway and archie-state-store call markServing nowhere and emit no READY, so notifying them would time the unit out at start - see the companion bead. archie-ui is unaffected.
Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
Imported from beads
archie-core-y7qc· GitHub #1120 · type bug · priority P2 · created 2026-09-21 · closed 2026-10-17