-
Notifications
You must be signed in to change notification settings - Fork 32
Troubleshooting
lemker edited this page May 28, 2026
·
5 revisions
UniFi OS Server runs as a collection of systemd services inside a container. When a service does not start properly, it can break the startup sequence and prevent the next service from starting.
At a high level, the service startup sequence is as follows: postgres > mongodb > unifi-core > unifi
View the container logs with docker logs unifi-os-server. The output should look similar to:
No UOS_UUID present, generating...
Setting UOS_SYSTEM_IP to <IP>
Setting UOS_UUID to <UOS_UUID>
Setting UOS_SERVER_VERSION to 5.0.8
Setting FIRMWARE_PLATFORM to linux-x64Make sure all services are up and running inside the container. Open a shell into the container with docker exec -it unifi-os-server bash and run:
systemctl --type=service list-unitsThe output should look similar to:
UNIT LOAD ACTIVE SUB DESCRIPTION
cron.service loaded active running Regular background program processing daemon
dbus.service loaded active running D-Bus System Message Bus
epmd.service loaded active running Erlang Port Mapper Daemon
mongodb.service loaded active running An object/document-oriented database
nginx.service loaded active running nginx - high performance web server
postgresql-cluster@14-main.service loaded active exited PostgreSQL initial setup service
postgresql.service loaded active exited PostgreSQL RDBMS
postgresql@14-main.service loaded active running PostgreSQL Cluster 14-main
rabbitmq-server.service loaded active running RabbitMQ Messaging Server
snmpd.service loaded active running Simple Network Management Protocol (SNMP) Daemon.
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysusers.service loaded active exited Create System Users
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
ubnt-dpkg-daemon.service loaded active exited UniFi dpkg daemon
ubnt-dpkg-restore.service loaded active exited UniFi Application Restore
ucs-agent.service loaded active running UniFi Credential Server Agent
uid-agent.service loaded active running UID Agent service
ulp-go.service loaded active running ULP-GO
unifi-core.service loaded active running UniFi Core
unifi-directory.service loaded active running UniFi Directory Service
unifi-identity-update.service loaded active running UniFi Identity Update
unifi.service loaded active running unifi
uos-agent.service loaded active running UniFi OS AgentIf the above troubleshooting steps did not resolve your issue, please feel free to create a new issue in the repo with the following information:
- Your host specs including hardware, OS, CPU, RAM, and number of connected devices
- Your Docker Compose file
- The container logs
- The output of
systemctl --type=service list-unitsfrom inside the container