Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] - Unifi-Controller: Unifi. Unraid. Reborn.

Featured Replies

Information requested below;

Am also seeing several lines of RED text in the Unifi log file. Never looked at the log filer before, is that normal? Can supply the log file if needed.

Thank you !

image.png

image.png

image.png

image.png

  • Replies 994
  • Views 185k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • 8.0.28 has failed testing and will not be promoted to an unraid tag and will be skipped.

  • PeteAsking
    PeteAsking

    8.3.32-unraid tag is tested and available for home users in production.

  • Yeah not sure what is happening with Linuxserver.io or their images. I switched to binhex for everything.   As he didnt have a unifi docker I had to make one with 11notes. 11notes has docker

Posted Images

  • Author
2 hours ago, oakley4404 said:

Information requested below;

Am also seeing several lines of RED text in the Unifi log file. Never looked at the log filer before, is that normal? Can supply the log file if needed.

Thank you !

image.png

image.png

image.png

image.png

Yes post the log file also please copy and paste the entire text from the extra parameters line as its truncated in the screenshot.

Extra parameters text:

--memory=8G --tmpfs /unifi/log:exec,uid=99,gid=100 --tmpfs /unifi/run:exec,uid=99,gid=100 --tmpfs /tmp:exec,uid=99,gid=100

Log file text with RED text :

14:48:02,696 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/migration.log.%i" substituted for "${logDir}/migration.log.%i"

14:48:02,696 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@7f284218 - No compression will be used

14:48:02,696 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

14:48:02,696 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

14:48:02,696 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[migration_log] - Active log file name: logs/migration.log

14:48:02,696 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[migration_log] - File property is set to [logs/migration.log]

14:48:02,696 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [tasks_log]

14:48:02,696 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/tasks.log" substituted for "${logDir}/tasks.log"

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/tasks.log.%i" substituted for "${logDir}/tasks.log.%i"

14:48:02,697 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@407a7f2a - No compression will be used

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

14:48:02,697 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[tasks_log] - Active log file name: logs/tasks.log

14:48:02,697 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[tasks_log] - File property is set to [logs/tasks.log]

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [hotspot_log]

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/hotspot.log" substituted for "${logDir}/hotspot.log"

14:48:02,697 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/hotspot.log.%i" substituted for "${logDir}/hotspot.log.%i"

14:48:02,697 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4ea5b703 - No compression will be used

14:48:02,698 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

14:48:02,698 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

14:48:02,698 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[hotspot_log] - Active log file name: logs/hotspot.log

14:48:02,698 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[hotspot_log] - File property is set to [logs/hotspot.log]

14:48:02,698 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [inform_request_log]

14:48:02,698 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

14:48:02,698 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/inform_request.log" substituted for "${logDir}/inform_request.log"

14:48:02,698 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/inform_request.log.%i" substituted for "${logDir}/inform_request.log.%i"

14:48:02,698 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@2a7ed1f - No compression will be used

14:48:02,698 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

14:48:02,699 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[inform_request_log] - Active log file name: logs/inform_request.log

14:48:02,699 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[inform_request_log] - File property is set to [logs/inform_request.log]

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [startup_log]

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.FileAppender]

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/startup.log" substituted for "${logDir}/startup.log"

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

14:48:02,699 |-INFO in ch.qos.logback.core.FileAppender[startup_log] - File property is set to [logs/startup.log]

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [sdwan_log]

14:48:02,699 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.FileAppender]

14:48:02,700 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/sdwan.log" substituted for "${logDir}/sdwan.log"

14:48:02,700 |-WARN in ch.qos.logback.core.model.processor.ImplicitModelHandler - Ignoring unknown property [triggeringPolicy] in [ch.qos.logback.core.FileAppender]

14:48:02,700 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

14:48:02,700 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

14:48:02,700 |-INFO in ch.qos.logback.core.FileAppender[sdwan_log] - File property is set to [logs/sdwan.log]

14:48:02,700 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [InMemoryAppender]

14:48:02,700 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [com.ubnt.ace.logs.InMemoryAppender]

14:48:02,703 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

14:48:02,703 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

14:48:02,703 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [AnalyticsAppender]

14:48:02,703 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [com.ubnt.service.trace.logerror.AnalyticsAppender]

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [java] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [javax] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [javax.jmdns] to OFF

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [sun] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache] to WARN

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [httpclient.wire] to WARN

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [net.schmizz] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.codahale] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.tomcat] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.commons] to WARN

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.catalina] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.hibernate.validator] to WARN

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.mongodb] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.mongodb] to ERROR

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.springframework] to WARN

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [de.javawi.jstun] to WARN

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.ubnt] to INFO

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.ubiquiti] to INFO

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.amazonaws.internal] to WARN

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [springfox] to WARN

14:48:02,886 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [state_log] to Logger[state]

14:48:02,886 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [migration_log] to Logger[migration]

14:48:02,886 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [tasks] to DEBUG

14:48:02,887 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [tasks] to false

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [tasks_log] to Logger[tasks]

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [hotspot_log] to Logger[guest]

14:48:02,887 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [inform_request] to false

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [inform_request_log] to Logger[inform_request]

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [startup_log] to Logger[startup]

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [sdwan_log] to Logger[sdwan]

14:48:02,887 |-INFO in ch.qos.logback.classic.model.processor.RootLoggerModelHandler - Setting level of ROOT logger to INFO

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [server_log] to Logger[ROOT]

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [InMemoryAppender] to Logger[ROOT]

14:48:02,887 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [AnalyticsAppender] to Logger[ROOT]

14:48:02,888 |-INFO in ch.qos.logback.core.model.processor.DefaultProcessor@3fa247d1 - End of configuration.

14:48:02,888 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@2cb2fc20 - Registering current configuration as safe fallback point

14:48:02,888 |-INFO in ch.qos.logback.classic.util.ContextInitializer@23202fce - ch.qos.logback.classic.util.DefaultJoranConfigurator.configure() call lasted 391 milliseconds. ExecutionStatus=DO_NOT_INVOKE_NEXT_IF_ANY

  • Author

@oakley4404 Im not clear why its not working for you. Are you sure you are on the same network and can ping the container ip you gave it?

Yes, am on the same network, can connect to UnRaid, @ 10.0.0.251, with no issues.... Yes, can ping 10.0.0.249 when the Unfi-controller-re-born has been started. When the Unfi-controller-re-born is stopped the ping to 10.0.0.249 will not reply.

Couple of Questions:

  • Does the Unfi-controller-re-born require a specific "Docker custom Network type" or will it operate successfully on both Ipvlan or macvlan?

  • Are there any known issues with running Unfi-controller-re-born container from Docker App data on a Cache drive?

May try to remove and delete ALL associated Docker folders and files, then re-install. Could you please confirm that removing the following folders will allow for a clean install, or are there folders/files at other locations that also need to be removed?

/mnt/user/system/docker/docker-xfs.img

/mnt/cache/appdata/

Thank you for your time and help !!!

  • Author
3 hours ago, oakley4404 said:

Yes, am on the same network, can connect to UnRaid, @ 10.0.0.251, with no issues.... Yes, can ping 10.0.0.249 when the Unfi-controller-re-born has been started. When the Unfi-controller-re-born is stopped the ping to 10.0.0.249 will not reply.

Couple of Questions:

  • Does the Unfi-controller-re-born require a specific "Docker custom Network type" or will it operate successfully on both Ipvlan or macvlan?

  • Are there any known issues with running Unfi-controller-re-born container from Docker App data on a Cache drive?

May try to remove and delete ALL associated Docker folders and files, then re-install. Could you please confirm that removing the following folders will allow for a clean install, or are there folders/files at other locations that also need to be removed?

/mnt/user/system/docker/docker-xfs.img

/mnt/cache/appdata/

Thank you for your time and help !!!

Do not remove /mnt/user/system/docker/docker-xfs.img

Remove only:

/mnt/cache/appdata/unifi-controller-reborn (and any other unifi-controller-reborn directories you might have created unless you need to back them up somewhere).

/boot/config/plugins/dockerMan/templates-user/my-unifi-controller-reborn.xml

also any other "my-unifi-controller-reborn.xml" related files in above templates-user directory.

Test without any changes to the docker template and all other dockers stopped first before altering networking settings.

Edited by PeteAsking

1 hour ago, PeteAsking said:

@oakley4404 what happened?

If I were to guess, as I've seen it with other Unifi Docker there is an error and a log spam that fills Unraid's Docker image and causes lockouts. I have not seen this with the reborn controller.

Well am happy to report that after deleting the recommended files and a fresh install, everything appears to be working. Now have one Docker Container running Unfi-controller-re-born. And a second Docker Container running Stirling PDF. Both now seem to be playing well together.

May never know why, but things are working now........

Thank you again for your time and help !!!

  • 2 weeks later...
On 3/23/2026 at 7:35 PM, oakley4404 said:

Well am happy to report that after deleting the recommended files and a fresh install, everything appears to be working. Now have one Docker Container running Unfi-controller-re-born. And a second Docker Container running Stirling PDF. Both now seem to be playing well together.

May never know why, but things are working now........

Thank you again for your time and help !!!

On 3/22/2026 at 2:22 PM, PeteAsking said:

@oakley4404 what happened?

@PeteAsking I too had the same issues as oakley4404. My log file (which I will post below, looks identical to oakley's.)

I have a rather old CPU, 4770. But by all accounts appears to support avx. Running unraid 7.2.4

I got everything working by renaming the old directory and basically following method 2. Where i removed the the container all together and pulled a new template/install

My question is I still have the red text in my logs in reference to several things of which mongodb is included. Don't guess i've ever noticed these warnings if they've existed in the past.

Thanks.

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called

WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper (file:/usr/lib/unifi/lib/local/guava-33.3.1-jre.jar)

WARNING: Please consider reporting this to the maintainers of class com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper

WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release

19:44:35,739 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[migration_log] - Active log file name: logs/migration.log

19:44:35,739 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[migration_log] - File property is set to [logs/migration.log]

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [tasks_log]

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/tasks.log" substituted for "${logDir}/tasks.log"

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/tasks.log.%i" substituted for "${logDir}/tasks.log.%i"

19:44:35,740 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@407a7f2a - No compression will be used

19:44:35,740 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,740 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,740 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[tasks_log] - Active log file name: logs/tasks.log

19:44:35,740 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[tasks_log] - File property is set to [logs/tasks.log]

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [hotspot_log]

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/hotspot.log" substituted for "${logDir}/hotspot.log"

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/hotspot.log.%i" substituted for "${logDir}/hotspot.log.%i"

19:44:35,741 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4ea5b703 - No compression will be used

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,742 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[hotspot_log] - Active log file name: logs/hotspot.log

19:44:35,742 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[hotspot_log] - File property is set to [logs/hotspot.log]

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [inform_request_log]

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/inform_request.log" substituted for "${logDir}/inform_request.log"

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/inform_request.log.%i" substituted for "${logDir}/inform_request.log.%i"

19:44:35,742 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@2a7ed1f - No compression will be used

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,743 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[inform_request_log] - Active log file name: logs/inform_request.log

19:44:35,743 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[inform_request_log] - File property is set to [logs/inform_request.log]

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [startup_log]

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.FileAppender]

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/startup.log" substituted for "${logDir}/startup.log"

19:44:35,744 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,744 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,744 |-INFO in ch.qos.logback.core.FileAppender[startup_log] - File property is set to [logs/startup.log]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [sdwan_log]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.FileAppender]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/sdwan.log" substituted for "${logDir}/sdwan.log"

19:44:35,745 |-WARN in ch.qos.logback.core.model.processor.ImplicitModelHandler - Ignoring unknown property [triggeringPolicy] in [ch.qos.logback.core.FileAppender]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,745 |-INFO in ch.qos.logback.core.FileAppender[sdwan_log] - File property is set to [logs/sdwan.log]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [InMemoryAppender]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [com.ubnt.ace.logs.InMemoryAppender]

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [AnalyticsAppender]

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [com.ubnt.service.trace.logerror.AnalyticsAppender]

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [java] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [javax] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [javax.jmdns] to OFF

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [sun] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [httpclient.wire] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [net.schmizz] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.codahale] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.tomcat] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.commons] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.catalina] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.hibernate.validator] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.mongodb] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.mongodb] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.springframework] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [de.javawi.jstun] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.ubnt] to INFO

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.ubiquiti] to INFO

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.amazonaws.internal] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [springfox] to WARN

19:44:35,963 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [state_log] to Logger[state]

19:44:35,964 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [migration_log] to Logger[migration]

19:44:35,964 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [tasks] to DEBUG

19:44:35,965 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [tasks] to false

19:44:35,965 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [tasks_log] to Logger[tasks]

19:44:35,965 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [hotspot_log] to Logger[guest]

19:44:35,966 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [inform_request] to false

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [inform_request_log] to Logger[inform_request]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [startup_log] to Logger[startup]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [sdwan_log] to Logger[sdwan]

19:44:35,966 |-INFO in ch.qos.logback.classic.model.processor.RootLoggerModelHandler - Setting level of ROOT logger to INFO

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [server_log] to Logger[ROOT]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [InMemoryAppender] to Logger[ROOT]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [AnalyticsAppender] to Logger[ROOT]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.DefaultProcessor@3fa247d1 - End of configuration.

19:44:35,967 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@2cb2fc20 - Registering current configuration as safe fallback point

19:44:35,967 |-INFO in ch.qos.logback.classic.util.ContextInitializer@23202fce - ch.qos.logback.classic.util.DefaultJoranConfigurator.configure() call lasted 433 milliseconds. ExecutionStatus=DO_NOT_INVOKE_NEXT_IF_ANY

Edited by bglawson42
to add colors to log

  • Author
2 hours ago, bglawson42 said:

@PeteAsking I too had the same issues as oakley4404. My log file (which I will post below, looks identical to oakley's.)

I have a rather old CPU, 4770. But by all accounts appears to support avx. Running unraid 7.2.4

I got everything working by renaming the old directory and basically following method 2. Where i removed the the container all together and pulled a new template/install

My question is I still have the red text in my logs in reference to several things of which mongodb is included. Don't guess i've ever noticed these warnings if they've existed in the past.

Thanks.

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called

WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper (file:/usr/lib/unifi/lib/local/guava-33.3.1-jre.jar)

WARNING: Please consider reporting this to the maintainers of class com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper

WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release

19:44:35,739 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[migration_log] - Active log file name: logs/migration.log

19:44:35,739 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[migration_log] - File property is set to [logs/migration.log]

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [tasks_log]

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/tasks.log" substituted for "${logDir}/tasks.log"

19:44:35,739 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/tasks.log.%i" substituted for "${logDir}/tasks.log.%i"

19:44:35,740 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@407a7f2a - No compression will be used

19:44:35,740 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,740 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,740 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[tasks_log] - Active log file name: logs/tasks.log

19:44:35,740 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[tasks_log] - File property is set to [logs/tasks.log]

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [hotspot_log]

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/hotspot.log" substituted for "${logDir}/hotspot.log"

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/hotspot.log.%i" substituted for "${logDir}/hotspot.log.%i"

19:44:35,741 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4ea5b703 - No compression will be used

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,741 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,742 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[hotspot_log] - Active log file name: logs/hotspot.log

19:44:35,742 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[hotspot_log] - File property is set to [logs/hotspot.log]

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [inform_request_log]

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/inform_request.log" substituted for "${logDir}/inform_request.log"

19:44:35,742 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/inform_request.log.%i" substituted for "${logDir}/inform_request.log.%i"

19:44:35,742 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@2a7ed1f - No compression will be used

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,743 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[inform_request_log] - Active log file name: logs/inform_request.log

19:44:35,743 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[inform_request_log] - File property is set to [logs/inform_request.log]

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [startup_log]

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.FileAppender]

19:44:35,743 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/startup.log" substituted for "${logDir}/startup.log"

19:44:35,744 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,744 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,744 |-INFO in ch.qos.logback.core.FileAppender[startup_log] - File property is set to [logs/startup.log]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [sdwan_log]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.FileAppender]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "logs/sdwan.log" substituted for "${logDir}/sdwan.log"

19:44:35,745 |-WARN in ch.qos.logback.core.model.processor.ImplicitModelHandler - Ignoring unknown property [triggeringPolicy] in [ch.qos.logback.core.FileAppender]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,745 |-INFO in ch.qos.logback.core.FileAppender[sdwan_log] - File property is set to [logs/sdwan.log]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [InMemoryAppender]

19:44:35,745 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [com.ubnt.ace.logs.InMemoryAppender]

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@37911f88 - value "[%date{"yyyy-MM-dd'T'HH:mm:ss,SSSXXX"}] <%thread> %-5level %-6logger{0} - %message%n" substituted for "${logPattern}"

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [AnalyticsAppender]

19:44:35,747 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [com.ubnt.service.trace.logerror.AnalyticsAppender]

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [java] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [javax] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [javax.jmdns] to OFF

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [sun] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [httpclient.wire] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [net.schmizz] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.codahale] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.tomcat] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.commons] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.catalina] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.hibernate.validator] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.mongodb] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.mongodb] to ERROR

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.springframework] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [de.javawi.jstun] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.ubnt] to INFO

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.ubiquiti] to INFO

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.amazonaws.internal] to WARN

19:44:35,963 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [springfox] to WARN

19:44:35,963 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [state_log] to Logger[state]

19:44:35,964 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [migration_log] to Logger[migration]

19:44:35,964 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [tasks] to DEBUG

19:44:35,965 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [tasks] to false

19:44:35,965 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [tasks_log] to Logger[tasks]

19:44:35,965 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [hotspot_log] to Logger[guest]

19:44:35,966 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [inform_request] to false

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [inform_request_log] to Logger[inform_request]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [startup_log] to Logger[startup]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [sdwan_log] to Logger[sdwan]

19:44:35,966 |-INFO in ch.qos.logback.classic.model.processor.RootLoggerModelHandler - Setting level of ROOT logger to INFO

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [server_log] to Logger[ROOT]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [InMemoryAppender] to Logger[ROOT]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [AnalyticsAppender] to Logger[ROOT]

19:44:35,966 |-INFO in ch.qos.logback.core.model.processor.DefaultProcessor@3fa247d1 - End of configuration.

19:44:35,967 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@2cb2fc20 - Registering current configuration as safe fallback point

19:44:35,967 |-INFO in ch.qos.logback.classic.util.ContextInitializer@23202fce - ch.qos.logback.classic.util.DefaultJoranConfigurator.configure() call lasted 433 milliseconds. ExecutionStatus=DO_NOT_INVOKE_NEXT_IF_ANY

Is everything working at this stage or not working?

10 hours ago, PeteAsking said:

Is everything working at this stage or not working?

Yes everything appears to be working. So my post might have been completely unnecessary.. was just curious about the errors.

  • Author
1 hour ago, bglawson42 said:

Yes everything appears to be working. So my post might have been completely unnecessary.. was just curious about the errors.

You could open an issue on Github, Im not 100% sure myself.

GitHub
No image preview

Issues · 11notes/docker-unifi

run Unifi Controller rootless. Contribute to 11notes/docker-unifi development by creating an account on GitHub.

Edited by PeteAsking

  • 2 weeks later...

I successfully upgraded to 11notes/unifi:10.1.89-unraid from 11notes/unifi:9.5.21-unraid earlier this week. Thanks so much for the unifi-controller-reborn app/docker container. I exhaust my abilities just doing the upgrade, and some of you guys out there code these things for the rest of us.

I do have one observation/question. When I go to the web GUI of my Unifi controller, now running version 10.1.89, I get the following message:

"UniFi Network Server will not support upcoming Network versions. Move to UniFi OS Server for a modern, supported platform with faster iteration and deeper platform capabilities."

Is the Unifi OS Server something that will eventually be available in an Unraid compatible docker? Assuming one of our awesome community members creates the docker container? I hope so.

Thanks,

Oilman

Edited by Oilman

  • Author
On 4/17/2026 at 1:31 AM, Oilman said:

I successfully upgraded to 11notes/unifi:10.1.89-unraid from 11notes/unifi:9.5.21-unraid earlier this week. Thanks so much for the unifi-controller-reborn app/docker container. I exhaust my abilities just doing the upgrade, and some of you guys out there code these things for the rest of us.

I do have one observation/question. When I go to the web GUI of my Unifi controller, now running version 10.1.89, I get the following message:

"UniFi Network Server will not support upcoming Network versions. Move to UniFi OS Server for a modern, supported platform with faster iteration and deeper platform capabilities."

Is the Unifi OS Server something that will eventually be available in an Unraid compatible docker? Assuming one of our awesome community members creates the docker container? I hope so.

Thanks,

Oilman

Seems like unifi have fully decided to kill off the network application so in the short term there is no way to upgrade anymore unfortunately.

So, is there any consensus yet on the best way to deploy the unifi os server? VM or the docker container maintained by @bmartino1 ? I'm looking to take the plunge soon, but I haven't decided what to go for.

7 minutes ago, strike said:

So, is there any consensus yet on the best way to deploy the unifi os server? VM or the docker container maintained by @bmartino1 ? I'm looking to take the plunge soon, but I haven't decided what to go for.

Per unified following their MSRP, they're claiming that the best way to do this is in a VM and via Debian.

I've only processed and only managing things based on the GitHub project from lemker, which I can confirm function that's intended.

All issues and problems that are complaints on this forum which is why I have the three posts anymore are literally user error system specific complications and problems of how they implement dockers.

Which has been proven by path, location and file permissions including paid limitations according to whatever Claude and the other person did which is not a fix for their secret problem.

But again without logs I can't assist or fix issues.

I have been maintaining this for a number of sites for different locations and can confirm that the docker project works just fine.

That said, it would be easier to maintain, update and configure if it was in a LXC/ virtual machine.

While I do have plans to put that into an LXC and make a template right now, that's a work in progress as I don't have times to go through the inconsistency as of as deployment.

And can only recommend if you want a full 100% stable. Go VM.

For the quick access, you need it to run now. Go Docker.

The beta template in the ca was the old original version. 5. That was not slated to not be ran as privileged.

After working with lemker and the docker project itself on GitHub, we made a version that did not require being privileged, but it's still a Debian system D docker and some Docker implementation are required and known. All I've been posted on this post already. All I can say is your results May vary based on the hardware in which you run it on.

  • Author
27 minutes ago, strike said:

So, is there any consensus yet on the best way to deploy the unifi os server? VM or the docker container maintained by @bmartino1 ? I'm looking to take the plunge soon, but I haven't decided what to go for.

My personal opinion is Unifi have made it pretty clear they only want their project run on a vm with their sanctioned method so if you deviate from that your doing so at your own risk. Its the unifi way or dont complain basically.

@bmartino1 @PeteAsking Thanks, appreciate your inputs. Honestly, I only use it for my access points at home, so I rarely need to access it unless it's for an update. I prefer docker, but I guess I could spin up a VM too. If it's like the network application where you don't need to have it running all the time, I guess a VM would do fine. Just turn it on when I need to update and leave it off when I don't need it. If my wifi works, I'm happy, all other network-related things are done on my pfsense box.

Is there any reason not to update to 10.3.55-unraid?

  • Author
On 5/3/2026 at 10:35 AM, jumperalex said:

Is there any reason not to update to 10.3.55-unraid?

I suggest moving to the VM version and no longer using this docker version as Unifi no longer support it.

Unfortunately a solution cant be safely and reliably made when unifi actively work against it.

Edited by PeteAsking

I suggest moving to the VM version and no longer using this docker version as Unifi no longer support it.

Unfortunately a solution cant be safely and reliably made when unifi actively work against it.

That's fair. But for now I'm sticking with Dockers. And FWIW I just bit the bullet and 10.3.55 loaded up and is running. We'll see if something bad happens since I threw a few weird errors like about memory and swap not being enabled [shrug].

I've upgraded my 11notes-unifi-reborn-docker to 10.3.58 three days ago (coming from 10.1.89). Worked like a charm (at least for my environment).

Edited by JayDee73

On 4/25/2026 at 9:47 PM, bmartino1 said:

Per unified following their MSRP, they're claiming that the best way to do this is in a VM and via Debian.

I've only processed and only managing things based on the GitHub project from lemker, which I can confirm function that's intended.

All issues and problems that are complaints on this forum which is why I have the three posts anymore are literally user error system specific complications and problems of how they implement dockers.

Which has been proven by path, location and file permissions including paid limitations according to whatever Claude and the other person did which is not a fix for their secret problem.

But again without logs I can't assist or fix issues.

I have been maintaining this for a number of sites for different locations and can confirm that the docker project works just fine.

That said, it would be easier to maintain, update and configure if it was in a LXC/ virtual machine.

While I do have plans to put that into an LXC and make a template right now, that's a work in progress as I don't have times to go through the inconsistency as of as deployment.

And can only recommend if you want a full 100% stable. Go VM.

For the quick access, you need it to run now. Go Docker.

The beta template in the ca was the old original version. 5. That was not slated to not be ran as privileged.

After working with lemker and the docker project itself on GitHub, we made a version that did not require being privileged, but it's still a Debian system D docker and some Docker implementation are required and known. All I've been posted on this post already. All I can say is your results May vary based on the hardware in which you run it on.

Is there any reason why you have deleted your support thread?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.