manager: delayed policy-loader exit
2025-01-29 09:15:58,514 supervisor[1530345]: [INFO] spawned: 'policy-loader' with pid 1530390
2025-01-29 09:15:58,601 supervisor[1530345]: [WARN] exited: policy-loader (exit status 0; not expected)
2025-01-29 09:15:58,602 supervisor[1530345]: [WARN] ignoring ready notification from unregistered PID=1530390
2025-01-29 09:15:58,609 manager[1530347]: [ERROR] knot_resolver.manager.manager: Failed to load policy rules: failed to start 'policy-loader'
The error is not common, but it is possible that the policy-loader
will terminate before it is even registered in starting_processes
(sd_notify.py
). This will cause that the READY notification from policy-loader
is not expected and will end with the error.