Comment 0 for bug 2060297

as per title

ubuntu@meinfoo:~$ systemctl status maas-apiserver.service
○ maas-apiserver.service - MAAS Region API
     Loaded: loaded (/lib/systemd/system/maas-apiserver.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: https://maas.io/docs

restarting the service fixes it. It should be related to the fact that the apiserver starts before the regiond that creates the unix socket

ubuntu@swoobat:~$ systemctl status maas-apiserver.service
● maas-apiserver.service - MAAS Region API
     Loaded: loaded (/lib/systemd/system/maas-apiserver.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2024-04-05 10:45:39 UTC; 2h 4min ago
       Docs: https://maas.io/docs
   Main PID: 1516178 (maas-apiserver)
      Tasks: 1 (limit: 154276)
     Memory: 67.7M
        CPU: 12.715s
     CGroup: /system.slice/maas-apiserver.service
             └─1516178 /usr/bin/python3 /usr/sbin/maas-apiserver

Apr 05 10:45:39 swoobat systemd[1]: Started MAAS Region API.
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO: Started server process [1516178]
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO:uvicorn.error:Started server process [1516178]
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO: Waiting for application startup.
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO:uvicorn.error:Waiting for application startup.
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO: Application startup complete.
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO:uvicorn.error:Application startup complete.
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO: Uvicorn running on unix socket /var/lib/maas/apiserver-http.sock (Press CTRL+C to quit)
Apr 05 10:45:40 swoobat maas-apiserver[1516178]: INFO:uvicorn.error:Uvicorn running on unix socket /var/lib/maas/apiserver-http.sock (Press CTRL+C to quit)