search

jacobalberty / unifi-docker

Unifi Docker files
MIT License
2.14k stars 454 forks source link

container crashing when trying to initialize from backup #428

Closed tim-oe closed 2 years ago

tim-oe commented 3 years ago

Host operating system

Ubuntu 20.04.2 LTS

Example: Debian stretch or Open Media Vault 3

What tag are you using

latest

from server.log [2021-04-04T20:50:46,133] INFO system - UniFi 6.1.71 (build atag_6.1.71_15061 - release/release) is started

What complete docker command or docker-compose.yml do you use to launch the container (omitting sensitive values)?

version: "3.7" services: unifi: image: jacobalberty/unifi:latest container_name: "unifi" restart: always volumes:

What do you expect to happen?

when first starting new container, should be able to initialize the controller with a backup file

What actually happens?

docker instance crashes with the following output

Attaching to unifi unifi | [2021-04-04 20:48:51,300] Starting unifi controller service. unifi | [2021-04-04 20:48:51,302] WARNING: Running UniFi in insecure (root) mode unifi | 2021-04-04 20:48:51,619 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND unifi | WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) unifi | 2021-04-04 20:48:51,807 main ERROR Unable to locate appender "InMemoryAppender" for logger config "root" unifi | org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called unifi | Exception in thread "Thread-15" java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext unifi | at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:177) unifi | at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1123) unifi | at com.ubnt.service.ooOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.Ö00000(Unknown Source) unifi | at com.ubnt.ace.Launcher$2.run(Unknown Source) unifi | [2021-04-04 20:50:42,247] WARN: unifi service process ended without being signaled? Check for errors in /unifi/log.

from server.log [2021-04-04T20:50:46,133] INFO system - BASE dir:/usr/lib/unifi [2021-04-04T20:50:46,158] INFO system - Current System IP: 172.19.0.2 [2021-04-04T20:50:46,158] INFO system - Hostname: a9107d3cdf90 [2021-04-04T20:50:46,158] INFO system - ubic.env: prod [2021-04-04T20:50:46,385] INFO db - waiting for db connection... [2021-04-04T20:50:47,886] INFO db - Connecting to mongodb://localhost:27117 [2021-04-04T20:50:50,446] INFO db - setting mongodb features compatibility version to 3.6 [2021-04-04T20:51:05,196] INFO db - Connecting to mongodb://localhost:27117 [2021-04-04T20:51:07,650] INFO productinfo - Using controller channel=RELEASE, firmware channel=RELEASE. Available controller channels=[RELEASE], available firmware channels=[RELEASE]. SSO is disabled. [2021-04-04T20:51:07,950] INFO webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v2.9.1 - Gladiator - (built for Debian-8.2.0-x86_64 on 2020-02-05T23:33:19.000) OpenSSL version: 1.1.1d usrsctp version: v0.1.2 compiled on machine: Linux debian-8-2-0-64 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07-14) x86_64 GNU/Linux [2021-04-04T20:51:08,395] INFO sdn - Removed fingerbank token [2021-04-04T20:51:08,464] INFO remote - Directory '/usr/lib/unifi/logs/remote' present [2021-04-04T20:51:08,472] INFO remote - started remote log server [2021-04-04T20:52:00,023] INFO schedule - Not forcing multicast block on any SSIDs since none had >= 100 clients in last hour [2021-04-04T20:52:00,023] WARN schedule - No gateway device was detected so we cannot enable multicast block

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.