fix(network): context.Background() für applyAsync + StartLimitIntervalSec=0
applyAsync()-Goroutinen in networks.go und ipaddresses.go nutzten c.Request.Context() — der wird gecancelt wenn der Handler zurückkehrt, was zu "query: context canceled" in jedem Apply-Lauf führte. Fix: context.Background() direkt in der Goroutine. StartLimitIntervalSec=0 in beiden apply-Services verhindert dass systemd bei mehrfachen schnellen Triggers (Burst > 5) drosselt. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -484,6 +484,7 @@ APPLYIFACES
|
||||
Description=EdgeGuard managed network interfaces apply
|
||||
After=network-online.target
|
||||
Wants=network-online.target
|
||||
StartLimitIntervalSec=0
|
||||
|
||||
[Service]
|
||||
Type=oneshot
|
||||
@@ -549,6 +550,7 @@ APPLYIP
|
||||
Description=EdgeGuard managed IP addresses apply
|
||||
After=network-online.target edgeguard-interfaces.service
|
||||
Wants=network-online.target
|
||||
StartLimitIntervalSec=0
|
||||
|
||||
[Service]
|
||||
Type=oneshot
|
||||
|
||||
Reference in New Issue
Block a user