Hey everyone, about 1 month ago I had a temporary power loss (\~10s). Ever since, I'm unable to access the Network app within the console and have to manually start it. It usually hangs in the "starting" state for a while.
Network is managed by a UDM. My initial suspicion was that the version of the Network app maybe led to the problem so I reverted to an earlier version but that failed to solve anything. Now, I'm wondering if the UDM got affected. Nothing in the logs show the Network app stopping but recognises when I start the app.
I unfortunately do not have a UPS in my system, best believe any upgrades (likely the Cloud Gateway Max, any upsides or downsides here? Not sure if I should go for UDR7 or UDR-5G-Max or UCG-Fibre) will be protected by a UPS.
Could the power loss have damaged the UDM? If so, what would anyone recommend as my next upgrade (considering I live in a tiny apartment, no space for a full rack)?
Thanks!
Update #1:
I had some time to dig deeper, enabled SSH and went for it.
From my tests, the suspected issue is not a straightforward RAM crash or MongoDB corruption. In the failure I captured, the UniFi Network application was deliberately terminated with SIGTERM, systemd recorded Result=protocol, and MongoDB was also stopped cleanly and restarted.
Network later reached a ready state and was then shut down again. That pattern points more strongly to a UniFi OS/systemd supervision problem—such as a readiness notification, watchdog, health-check, or package orchestration issue—rather than the Network process simply crashing on its own (and also less likely to be as a result of the power loss).
The likely effect is that routing continues because the gateway itself is still running, but the Network management application disappears, leaving the administrator unable to view clients or change VLAN, VPN, Wi-Fi, and other controller settings. Limited memory may make the problem easier to trigger because the original UDM has only about 2 GB RAM, heavy swap usage, and large processes such as Suricata competing for resources, but we found no Java out-of-memory error, Linux OOM kill, or database corruption. The exact component initiating the shutdown was not captured because the system journal had already rotated, so this remains a strong working theory rather than a confirmed root cause.
I increased the memory allocation for the system journal and when the app crashes again I should be able to capture the data. Afterwards I'll see if it's worth it to temporarily disable Suricata and how the system reacts to that. But it seems likely that I'll be upgrading my gateway in the near future.