[rescue01] Fix stateless-uptime-kuma startup #112

New issue

Open

opened 2024-06-02 11:52:23 +02:00 by mdebray · 0 comments

mdebray commented

2024-06-02 11:52:23 +02:00

Member

After = [ "uptime-kuma.service" ] is not enough.

× stateless-uptime-kuma.service - Uptime-kuma probes deployment
     Loaded: loaded (/etc/systemd/system/stateless-uptime-kuma.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sat 2024-06-01 22:02:45 CEST; 266ms ago
    Process: 870 ExecStart=/nix/store/1jzzzgvs684vm4x444523r9z8fq1d2vl-unit-script-stateless-uptime-kuma-start/bin/stateless-uptime-kuma-start (code=exited, status=1/FAILURE)
   Main PID: 870 (code=exited, status=1/FAILURE)
         IP: 100B in, 140B out
        CPU: 213ms

Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]:   File "/nix/store/agsmr5zr5h6b9szz60njvpjbjvw2jabq-python3.11-uptime-kuma-api-1.2.1/lib/python3.11/site-packages/uptime_kuma_api/api.py", line 510, in __init__
Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]:     self.connect()
Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]:   File "/nix/store/agsmr5zr5h6b9szz60njvpjbjvw2jabq-python3.11-uptime-kuma-api-1.2.1/lib/python3.11/site-packages/uptime_kuma_api/api.py", line 669, in connect
Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]:     raise UptimeKumaException("unable to connect")
Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]: uptime_kuma_api.exceptions.UptimeKumaException: unable to connect
Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Main process exited, code=exited, status=1/FAILURE
Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Failed with result 'exit-code'.
Jun 01 22:02:45 rescue01 systemd[1]: Failed to start Uptime-kuma probes deployment.
Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Triggering OnFailure= dependencies.
Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Consumed 213ms CPU time, received 100B IP traffic, sent 140B IP traffic.

`After = [ "uptime-kuma.service" ]` is not enough. ``` × stateless-uptime-kuma.service - Uptime-kuma probes deployment Loaded: loaded (/etc/systemd/system/stateless-uptime-kuma.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2024-06-01 22:02:45 CEST; 266ms ago Process: 870 ExecStart=/nix/store/1jzzzgvs684vm4x444523r9z8fq1d2vl-unit-script-stateless-uptime-kuma-start/bin/stateless-uptime-kuma-start (code=exited, status=1/FAILURE) Main PID: 870 (code=exited, status=1/FAILURE) IP: 100B in, 140B out CPU: 213ms Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]: File "/nix/store/agsmr5zr5h6b9szz60njvpjbjvw2jabq-python3.11-uptime-kuma-api-1.2.1/lib/python3.11/site-packages/uptime_kuma_api/api.py", line 510, in __init__ Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]: self.connect() Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]: File "/nix/store/agsmr5zr5h6b9szz60njvpjbjvw2jabq-python3.11-uptime-kuma-api-1.2.1/lib/python3.11/site-packages/uptime_kuma_api/api.py", line 669, in connect Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]: raise UptimeKumaException("unable to connect") Jun 01 22:02:45 rescue01 stateless-uptime-kuma-start[876]: uptime_kuma_api.exceptions.UptimeKumaException: unable to connect Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Main process exited, code=exited, status=1/FAILURE Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Failed with result 'exit-code'. Jun 01 22:02:45 rescue01 systemd[1]: Failed to start Uptime-kuma probes deployment. Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Triggering OnFailure= dependencies. Jun 01 22:02:45 rescue01 systemd[1]: stateless-uptime-kuma.service: Consumed 213ms CPU time, received 100B IP traffic, sent 140B IP traffic. ```

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DGNum/infrastructure#112

No description provided.