When systemd launches a daemon (such as ulb.py) it does not wait to see if there was an error after the process was launched. Thus, even the bpf code compilation failed, systemd will start the dependents services as if everything was ok.
To solve this issue, ulb.py simply needs to call /bin/systemd-notify --ready to signal it is ready to accept connections.
When systemd launches a daemon (such as ulb.py) it does not wait to see if there was an error after the process was launched. Thus, even the bpf code compilation failed, systemd will start the dependents services as if everything was ok.
To solve this issue, ulb.py simply needs to call
/bin/systemd-notify --readyto signal it is ready to accept connections.