I did a fresh installation and followed the installation steps, but the addon doesn't start and I can't proceed with configuring the controller.
Full logs, with changed log level to "TRACE":
`[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
Add-on: UniFi Controller
Manage your UniFi network using a web browser
Add-on version: 1.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 6.3 (amd64 / qemux86-64)
Home Assistant Core: 2021.9.4
Home Assistant Supervisor: 2021.09.0
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to TRACE
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] unifi.sh: executing...
[08:24:10] TRACE: bashio::fs.directory_exists: /data/unifi/data
[08:24:10] TRACE: bashio::fs.directory_exists: /backup/unifi
[08:24:10] TRACE: bashio::fs.file_exists: /data/unifi/data/system.properties
[08:24:10] TRACE: bashio::fs.file_exists: /usr/lib/unifi/data/keystore
[08:24:10] TRACE: bashio::fs.file_exists: /data/keystore_reset
[cont-init.d] unifi.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[08:24:10] INFO: Starting the UniFi Controller...
[08:24:10] TRACE: bashio::config.has_value: memory_max
[08:24:10] TRACE: bashio::config: memory_max
[08:24:10] TRACE: bashio::jq: /data/options.json if (.memory_max == null) then
null
elif (.memory_max | type == "string") then
.memory_max // empty
elif (.memory_max | type == "boolean") then
.memory_max // false
elif (.memory_max | type == "array") then
if (.memory_max == []) then
empty
else
.memory_max[]
end
elif (.memory_max | type == "object") then
if (.memory_max == {}) then
empty
else
.memory_max
end
else
.memory_max
end
[08:24:10] TRACE: bashio::config.has_value: memory_init
[08:24:10] TRACE: bashio::config: memory_init
[08:24:10] TRACE: bashio::jq: /data/options.json if (.memory_init == null) then
null
elif (.memory_init | type == "string") then
.memory_init // empty
elif (.memory_init | type == "boolean") then
.memory_init // false
elif (.memory_init | type == "array") then
if (.memory_init == []) then
empty
else
.memory_init[]
end
elif (.memory_init | type == "object") then
if (.memory_init == {}) then
empty
else
.memory_init
end
else
.memory_init
end`
Expected behavior
I expected it to change from "Starting the UniFi Controller..." to something like "Controller started" and was accessible through web UI
Actual behavior
The logs just say "INFO: Starting the UniFi Controller..." and when I try to open web UI it just loads, then times out with error "ERR_CONNECTION_TIMED_OUT".
Steps to reproduce
Click "Install" for Unify Addon, click "Start" to start addon, go to "Logs"-tab of the addon or click on web UI.
Problem/Motivation
I did a fresh installation and followed the installation steps, but the addon doesn't start and I can't proceed with configuring the controller.
Full logs, with changed log level to "TRACE": `[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-banner.sh: executing...
Add-on: UniFi Controller Manage your UniFi network using a web browser
Add-on version: 1.0.0 You are running the latest version of this add-on. System: Home Assistant OS 6.3 (amd64 / qemux86-64) Home Assistant Core: 2021.9.4 Home Assistant Supervisor: 2021.09.0
Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.
[cont-init.d] 00-banner.sh: exited 0. [cont-init.d] 01-log-level.sh: executing... Log level is set to TRACE [cont-init.d] 01-log-level.sh: exited 0. [cont-init.d] unifi.sh: executing... [08:24:10] TRACE: bashio::fs.directory_exists: /data/unifi/data [08:24:10] TRACE: bashio::fs.directory_exists: /backup/unifi [08:24:10] TRACE: bashio::fs.file_exists: /data/unifi/data/system.properties [08:24:10] TRACE: bashio::fs.file_exists: /usr/lib/unifi/data/keystore [08:24:10] TRACE: bashio::fs.file_exists: /data/keystore_reset [cont-init.d] unifi.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [08:24:10] INFO: Starting the UniFi Controller... [08:24:10] TRACE: bashio::config.has_value: memory_max [08:24:10] TRACE: bashio::config: memory_max [08:24:10] TRACE: bashio::jq: /data/options.json if (.memory_max == null) then null elif (.memory_max | type == "string") then .memory_max // empty elif (.memory_max | type == "boolean") then .memory_max // false elif (.memory_max | type == "array") then if (.memory_max == []) then empty else .memory_max[] end elif (.memory_max | type == "object") then if (.memory_max == {}) then empty else .memory_max end else .memory_max end [08:24:10] TRACE: bashio::config.has_value: memory_init [08:24:10] TRACE: bashio::config: memory_init [08:24:10] TRACE: bashio::jq: /data/options.json if (.memory_init == null) then null elif (.memory_init | type == "string") then .memory_init // empty elif (.memory_init | type == "boolean") then .memory_init // false elif (.memory_init | type == "array") then if (.memory_init == []) then empty else .memory_init[] end elif (.memory_init | type == "object") then if (.memory_init == {}) then empty else .memory_init end else .memory_init end`
Expected behavior
I expected it to change from "Starting the UniFi Controller..." to something like "Controller started" and was accessible through web UI
Actual behavior
The logs just say "INFO: Starting the UniFi Controller..." and when I try to open web UI it just loads, then times out with error "ERR_CONNECTION_TIMED_OUT".
Steps to reproduce
Proposed changes