- #UNIFI CONTROLLER OFFLINE HOW TO#
- #UNIFI CONTROLLER OFFLINE INSTALL#
- #UNIFI CONTROLLER OFFLINE UPGRADE#
This device is not able to connect to the internal STUN server on yourĬontroller. While looking at the settings, one of the non working AP's came to life briefly when I refreshed - This is the message it gave. Molan It appears that it is still getting firmware updates. But I will try the firmware fix first because I suspect that this is most likely the problem. I am also considering upgrading the wireless because we get the benefit of AC as well as hopefully fixing all the problems with the wireless. This weekend, I will downgrade back to version 4.3.20.xx because I do suspect that the firmware is the most likely cause. The other three I need to reboot the switch to reconnect to the access points to upgrade. Just upgraded four a couple of days ago to 4.1. Greggmh123 The beginning of this week, they were all on 4.5. They are responding to pings even though it shows up as disconnected in dashboard. [v8.32.It's true power coming from the switch. Check for additional error messages before this one. Oct 04 01:52:45 Unifi2021 rsyslogd: action 'action 3' (module 'builtin:omfile') message lost, could not be processed. Oct 04 01:52:45 Unifi2021 rsyslogd: file '7' write error: No space left on device Oct 04 01:52:46 Unifi2021 snapd: AppArmor status: apparmor is enabled and Oct 04 01:52:45 Unifi2021 rsyslogd: file '7' write error: No space left on Oct 04 01:52:45 Unifi2021 rsyslogd: action 'action 3' (module 'builtin:omfi Journal file /var/log/journal/50594b3ebe9b49808ca00b6abe15ffa9/system.journal is truncated, ignoring file. I looked at the journal and get no space error and apparmor something. The only difference is DO did something and my controller was not recoverable so I destroyed the droplet and created a new one using the Ubiquiti step by step process.
#UNIFI CONTROLLER OFFLINE INSTALL#
I did a basic install as it has been for over 9 years now.
T07:03:04.973+0000 E QUERY Error: couldn't connect to server 127.0.0.1:27117, connection attempt failed connect failed T07:03:04.972+0000 W NETWORK Failed to connect to 127.0.0.1:27117, in(checking socket for error after poll), reason: Connection refused Oct 03 06:54:05 Unifi2021 systemd: Started unifi.ĮRROR: No such file or directory (press mongo -port 27117 < mongo_prune_js.jsĬonnecting to: mongodb://127.0.0.1:27117/ Oct 03 06:49:31 Unifi2021 unifi: 06:49:31,237 main ERROR Unable to locate appender "server_log" for logger config "root" Oct 03 06:49:31 Unifi2021 unifi: 06:49:31,164 main ERROR Null object returned for RollingFile in Appenders. Oct 03 06:49:30 Unifi2021 unifi: jLoggerFactory.java:45)Īt 4j.( AbstractLoggerAdapter.java:48)Īt 4j.Log4jLoggerFactory.getLogger( Log4jLoggerFactory.java:30)Īt ( LoggerFactory.java:363)Īt .for.o00000(Unknown Source)Īt .for.(Unknown Source)Īt .(Unknown Source)Īt 0(Native Method)Īt ( NativeConstructorAccessorImpl.java:62)Īt ( DelegatingConstructorAccessorImpl.java:45)Īt .newInstance( Constructor.java:423)Īt ( Class.java:442)Īt .( DaemonLoader.java:190) at 4j.( LoggerContext.java:263)Īt 4j.( Log4jContextFactory.java:153)Īt 4j.( Log4jContextFactory.java:45)Īt 4j.LogManager.getContext( LogManager.java:194)Īt 4j.( AbstractLoggerAdapter.java:138)Īt 4j.Log4jLoggerFactory.getContext(Log4.
#UNIFI CONTROLLER OFFLINE HOW TO#
Any ideas on how to repair and get it stable? I am getting so many alerts that I am prunning the DB every other day and today the server.log is missing. I notice that the connection is unstable to 127.0.0.1:27117.
#UNIFI CONTROLLER OFFLINE UPGRADE#
I had to upgrade to ubuntu 18.06 and have had nothing but problems.