UniFi Controller stucks on startup

ViktorDa commented 5 years ago

Hi,

I'm trying to launch the UniFi Controller addon but it get's stuck on "UniFi Controller is starting up... Please wait a moment" and it never starts (I have had it running for a couple of days now).

I have extended the log to debug but I can't find anything relevant to my troubleshooting.

Have anyone seen this before? Have anyone solved it? Are there any other logs to check for information?

Running version 0.40 of UniFi controller and 0.81.6 HA.

hassio

hassio.txt

addons-assistant[bot] commented 5 years ago

:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

howlofthesun commented 5 years ago

I'm having the same issue. UniFi Controller - 0.4.0 HassOS - 1.12 ha - 0.81.6

varzaman commented 5 years ago

I'm also getting the same issue.

Fresh install of everything.

UniFi Controller v0.4.0 HassOS: 1.12 HA:0.81.6

Nothing in the logs that say anything about an issue.

TheMClaeys commented 5 years ago

Hi, I am having the same issue. If I can provide more debug logs, I would gladly help so please inform me how. This is the log from inside Home Assistant. Debug log.txt I run hassio on a Debian system and it actually worked great, it even autoupdated to version 0.4.0 and still ran. I had to turn my server off to move it to another location and to move some cables and it did't start anymore since that. I have access via SSH to my system, but then I have the Hassio commands, if debugging is needed further I can always attach a monitor to my server and do debugging on there (I can handle some Linux, but I think it runs in docker so I might need some help with that).

TheMClaeys commented 5 years ago

Hi, I can't provide any debugging logs anymore as the update to 0.82.1 fixed the issue for me. The controller boots again without issues, so it looks like it was more a Home Assistant issue then a Unify issue. Only sad that the logs never showed why it wasn't working, that could have brought up the issue sooner.

mnefk commented 5 years ago

I freshly installed everything and it hangs at startup with the following tested scenario:

UniFi Controller v.0.40 HassOS: 1.13, 2.4 HA: 0.84.4, 0.84.5, 0.84.6

Infrastructure Details

ESXi 6.7 Update 1 VM Settings:

NW E1000e
Disk IDE / Master
Firmware EFI
GuestOS: Other 4.x Linux 64Bit

tested HassOS

No issues logged as i can see..

Config

{
  "log_level": "debug",
  "ssl": false,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

Output

[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... 
-----------------------------------------------------------
 Hass.io Add-on: UniFi Controller v0.4.0
 Manage your UniFi network using a web browser
 From: Community Hass.io Add-ons
 By: Franck Nijhof <frenck@addons.community>
-----------------------------------------------------------
 amd64 / HassOS 1.13 / HA 0.84.6 / SU 141 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
DEBUG: Requested API resource: http://hassio/supervisor/ping
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {}}
DEBUG: Requested API resource: http://hassio/addons/self/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "UniFi Controller", "slug": "a0d7b954_unifi", "description": "Manage your UniFi network using a web browser", "long_description": "# Community Hass.io Add-ons: UniFi Controller\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\n[![Support my work on Patreon][patreon-shield]][patreon]\n\nThe UniFi Controller allows you to manage your UniFi network\nusing a web browser.\n\n## About\n\nThis add-on runs Ubiquiti Networks' UniFi Controller software, which allows\nyou to manage your UniFi network via the web browser. The add-on provides a\nsingle-click installation and run solution for Hass.io, allowing users to get\ntheir network up, running, and updated, easily.\n\nThis add-on supports all Hass.io supported architectures, including the\nRaspberry Pi.\n\n[Click here for the full documentation][docs]\n\n![UniFi Controller][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: https://img.shields.io/discord/478094546522079232.svg\n[discord]: https://discord.me/hassioaddons\n[docs]: https://github.com/hassio-addons/addon-unifi/blob/v0.4.0/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: https://community.home-assistant.io/t/community-hass-io-add-on-unifi-controller/56297?u=frenck\n[maintenance-shield]: https://img.shields.io/maintenance/yes/2018.svg\n[patreon-shield]: https://www.frenck.nl/images/patreon.png\n[patreon]: https://www.patreon.com/frenck\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-experimental-yellow.svg\n[release-shield]: https://img.shields.io/badge/version-v0.4.0-blue.svg\n[release]: https://github.com/hassio-addons/addon-unifi/tree/v0.4.0\n[screenshot]: https://github.com/hassio-addons/addon-unifi/raw/master/images/screenshot.jpg", "version": "0.4.0", "auto_update": true, "repository": "a0d7b954", "last_version": "0.4.0", "state": "started", "protected": true, "rating": 5, "boot": "auto", "options": {"log_level": "debug", "ssl": false, "certfile": "fullchain.pem", "keyfile": "privkey.pem"}, "arch": ["aarch64", "amd64", "armhf", "i386"], "machine": ["intel-nuc", "odroid-c2", "odroid-xu", "orangepi-prime", "qemux86", "qemux86-64", "qemuarm", "qemuarm-64", "raspberrypi", "raspberrypi2", "raspberrypi3", "raspberrypi3-64", "tinker"], "url": "https://community.home-assistant.io/t/community-hass-io-add-on-unifi-controller/56297?u=frenck", "detached": false, "available": true, "build": false, "network": {"1900/udp": 1900, "3478/udp": 3478, "6789/tcp": 6789, "8080/tcp": 8080, "8443/tcp": 8443, "8843/tcp": 8843, "8880/tcp": 8880, "10001/udp": 10001}, "host_network": false, "host_pid": false, "host_ipc": false, "host_dbus": false, "privileged": [], "full_access": false, "apparmor": "default", "devices": null, "icon": true, "logo": true, "changelog": true, "webui": "https://[HOST]:8443", "stdin": false, "hassio_api": true, "hassio_role": "default", "auth_api": false, "homeassistant_api": false, "gpio": false, "devicetree": false, "docker_api": false, "audio": false, "audio_input": null, "audio_output": null, "services": [], "discovery": []}}
DEBUG: Filtering response using: .version
DEBUG: Requested API resource: http://hassio/addons/self/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "UniFi Controller", "slug": "a0d7b954_unifi", "description": "Manage your UniFi network using a web browser", "long_description": "# Community Hass.io Add-ons: UniFi Controller\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\n[![Support my work on Patreon][patreon-shield]][patreon]\n\nThe UniFi Controller allows you to manage your UniFi network\nusing a web browser.\n\n## About\n\nThis add-on runs Ubiquiti Networks' UniFi Controller software, which allows\nyou to manage your UniFi network via the web browser. The add-on provides a\nsingle-click installation and run solution for Hass.io, allowing users to get\ntheir network up, running, and updated, easily.\n\nThis add-on supports all Hass.io supported architectures, including the\nRaspberry Pi.\n\n[Click here for the full documentation][docs]\n\n![UniFi Controller][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: https://img.shields.io/discord/478094546522079232.svg\n[discord]: https://discord.me/hassioaddons\n[docs]: https://github.com/hassio-addons/addon-unifi/blob/v0.4.0/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: https://community.home-assistant.io/t/community-hass-io-add-on-unifi-controller/56297?u=frenck\n[maintenance-shield]: https://img.shields.io/maintenance/yes/2018.svg\n[patreon-shield]: https://www.frenck.nl/images/patreon.png\n[patreon]: https://www.patreon.com/frenck\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-experimental-yellow.svg\n[release-shield]: https://img.shields.io/badge/version-v0.4.0-blue.svg\n[release]: https://github.com/hassio-addons/addon-unifi/tree/v0.4.0\n[screenshot]: https://github.com/hassio-addons/addon-unifi/raw/master/images/screenshot.jpg", "version": "0.4.0", "auto_update": true, "repository": "a0d7b954", "last_version": "0.4.0", "state": "started", "protected": true, "rating": 5, "boot": "auto", "options": {"log_level": "debug", "ssl": false, "certfile": "fullchain.pem", "keyfile": "privkey.pem"}, "arch": ["aarch64", "amd64", "armhf", "i386"], "machine": ["intel-nuc", "odroid-c2", "odroid-xu", "orangepi-prime", "qemux86", "qemux86-64", "qemuarm", "qemuarm-64", "raspberrypi", "raspberrypi2", "raspberrypi3", "raspberrypi3-64", "tinker"], "url": "https://community.home-assistant.io/t/community-hass-io-add-on-unifi-controller/56297?u=frenck", "detached": false, "available": true, "build": false, "network": {"1900/udp": 1900, "3478/udp": 3478, "6789/tcp": 6789, "8080/tcp": 8080, "8443/tcp": 8443, "8843/tcp": 8843, "8880/tcp": 8880, "10001/udp": 10001}, "host_network": false, "host_pid": false, "host_ipc": false, "host_dbus": false, "privileged": [], "full_access": false, "apparmor": "default", "devices": null, "icon": true, "logo": true, "changelog": true, "webui": "https://[HOST]:8443", "stdin": false, "hassio_api": true, "hassio_role": "default", "auth_api": false, "homeassistant_api": false, "gpio": false, "devicetree": false, "docker_api": false, "audio": false, "audio_input": null, "audio_output": null, "services": [], "discovery": []}}
DEBUG: Filtering response using: .last_version
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 50-persist-data.sh: executing... 
[cont-init.d] 50-persist-data.sh: exited 0.
[cont-init.d] 60-ssl.sh: executing... 
[cont-init.d] 60-ssl.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
INFO: Starting the UniFi Controller
[services.d] done.

mnefk commented 5 years ago

Okay it seems to be a problem with hassos OVA Files. Tested all above stated + .vhdx on a hyper-v

When i install an Ubuntu 18.04 with docker and Hass.io it worked with HA 83.3 > updated to 84.6 and it worked also.

pvizeli commented 5 years ago

Could be a missing kernel module/options?

frenck commented 5 years ago

Hard to tell @pvizeli, since, well, no output anywhere.

Godtoh commented 5 years ago

Same issue here. However, after installing, it will run the first and only time before configuring. When the wizard has been completed it won't start up again. After the wizard I noticed it wouldn't scan for devices anymore in the controller itself. Therefore I tried to restart it without succeeding.

Running: Hostname hassio System HassOS 1.13 Deployment production Running at Rpi 3b +

Reproduce: Uninstall Unifi Install Unifi Launch Unifi Follow Wizard and guide https://community.home-assistant.io/t/community-hass-io-add-on-unifi-controller/56297?u=frenck Restart Stuck at starting

Website shows the Information symbol with the text: "UniFi Controller is starting up..."

After configuring it gets stuck.

I tried stop and start without configuring (following the guide) and then I could restart it.

Got this message at first run after install: OpenJDK Client VM warning: You have loaded library /usr/lib/unifi/lib/native/Linux/armv7/libubnt_webrtc_jni.so which might have disabled stack guard. The VM will try to fix the stack guard now. It's highly recommended that you fix the library with 'execstack -c ', or link it with '-z noexecstack'.

Config { "log_level": "info", "ssl": false, "certfile": "fullchain.pem", "keyfile": "privkey.pem" }

Log

[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... 
-----------------------------------------------------------
 Hass.io Add-on: UniFi Controller v0.4.0
 Manage your UniFi network using a web browser
 From: Community Hass.io Add-ons
 By: Franck Nijhof <frenck@addons.community>
-----------------------------------------------------------
 armhf / HassOS 1.13 / HA 0.84.6 / SU 141 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 50-persist-data.sh: executing... 
[cont-init.d] 50-persist-data.sh: exited 0.
[cont-init.d] 60-ssl.sh: executing... 
[cont-init.d] 60-ssl.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting the UniFi Controller
OpenJDK Client VM warning: You have loaded library /usr/lib/unifi/lib/native/Linux/armv7/libubnt_webrtc_jni.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.

NoxHarmonium commented 5 years ago

I am getting the same issue.

HassOS 1.13 Hass.io supervisor 141 HA 0.84.6 Deployment production Raspberry Pi 3b+

It starts up the first time. Then once I restore from a backup it restarts and is on the "UniFi Controller is starting up..." screen forever. I tried all day yesterday to get it working. Strangely enough, I restarted the controller this morning and it started working. Then I after another restart it got stuck again. There was no difference in the logs between restarts. I haven't posted the logs because it is the same as above, even at debug level. Let me know if I can extract some more logs for you.

pvizeli commented 5 years ago

AppArmor? Do you see any things inside dmesg?

EDIT: After chatting with Frenk, that doesn't help...

NoxHarmonium commented 5 years ago

I don't think there is anything in dmesg that looks like the culprit. It looks like its just messages about the docker networking getting configured when the container boots. However, I'm not good at reading iptables audit messages so I'll post it here anyway.

This is the output of dmesg after trying to start the configured controller again (it doesn't start):

[189787.197414] hassio: port 4(veth4aacdcb) entered blocking state
[189787.199027] hassio: port 4(veth4aacdcb) entered disabled state
[189787.200746] device veth4aacdcb entered promiscuous mode
[189787.202549] kauditd_printk_skb: 65 callbacks suppressed
[189787.202555] audit: type=1700 audit(1546513809.301:1295): dev=veth4aacdcb prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[189787.208830] audit: type=1300 audit(1546513809.301:1295): arch=40000028 syscall=290 per=800000 success=yes exit=40 a0=c a1=13644630 a2=28 a3=0 items=0 ppid=1 pid=322 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" key=(null)
[189787.211148] IPv6: ADDRCONF(NETDEV_UP): veth4aacdcb: link is not ready
[189787.216563] audit: type=1327 audit(1546513809.301:1295): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D73746F726167652D6472697665723D6F7665726C617932002D2D6C6F672D6472697665723D6A6F75726E616C64
[189787.274075] audit: type=1325 audit(1546513809.381:1296): table=nat family=2 entries=21
[189787.277265] audit: type=1300 audit(1546513809.381:1296): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=6181f8 items=0 ppid=322 pid=19216 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" key=(null)
[189787.284066] audit: type=1327 audit(1546513809.381:1296): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4100444F434B4552002D7000756470002D6400302F30002D2D64706F7274003130303031002D6A00444E4154002D2D746F2D64657374696E6174696F6E003137322E33302E33332E323A31303030310000002D690068617373696F
[189787.297320] audit: type=1325 audit(1546513809.401:1297): table=filter family=2 entries=33
[189787.300904] audit: type=1300 audit(1546513809.401:1297): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=1c5beb0 items=0 ppid=322 pid=19218 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" key=(null)
[189787.308719] audit: type=1327 audit(1546513809.401:1297): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4100444F434B45520000002D690068617373696F002D6F0068617373696F002D7000756470002D64003137322E33302E33332E32002D2D64706F7274003130303031002D6A00414343455054
[189787.319978] audit: type=1325 audit(1546513809.421:1298): table=nat family=2 entries=22
[189789.561416] eth0: renamed from vetha09061d
[189789.614577] IPv6: ADDRCONF(NETDEV_CHANGE): veth4aacdcb: link becomes ready
[189789.618386] hassio: port 4(veth4aacdcb) entered blocking state
[189789.621965] hassio: port 4(veth4aacdcb) entered forwarding state

Then I uninstall and re-install the add-on which clears out the config. This lets it boot although just to the configuration wizard. Once I set up the config it will restart and not boot again. The output from dmesg when it boots up the first time is:

[189955.111500] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[189955.115196] brcmfmac: power management disabled
[190271.090456] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[190271.093830] brcmfmac: power management disabled
[190365.832255] kauditd_printk_skb: 95 callbacks suppressed
[190365.832262] audit: type=1325 audit(1546514387.933:1330): table=nat family=2 entries=37
[190365.842546] audit: type=1300 audit(1546514387.933:1330): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=2ef0d8 items=0 ppid=322 pid=22047 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" key=(null)
[190365.854594] audit: type=1327 audit(1546514387.933:1330): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4400444F434B4552002D7000756470002D6400302F30002D2D64706F7274003130303031002D6A00444E4154002D2D746F2D64657374696E6174696F6E003137322E33302E33332E323A31303030310000002D690068617373696F
[190365.863585] audit: type=1325 audit(1546514387.963:1331): table=filter family=2 entries=41
[190365.867030] audit: type=1300 audit(1546514387.963:1331): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=181dd80 items=0 ppid=322 pid=22049 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" key=(null)
[190365.874228] audit: type=1327 audit(1546514387.963:1331): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4400444F434B45520000002D690068617373696F002D6F0068617373696F002D7000756470002D64003137322E33302E33332E32002D2D64706F7274003130303031002D6A00414343455054
[190365.886273] audit: type=1325 audit(1546514387.983:1332): table=nat family=2 entries=36
[190365.889943] audit: type=1300 audit(1546514387.983:1332): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=1dc3e98 items=0 ppid=322 pid=22051 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" key=(null)
[190365.898331] audit: type=1327 audit(1546514387.983:1332): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4400504F5354524F5554494E47002D7000756470002D73003137322E33302E33332E32002D64003137322E33302E33332E32002D2D64706F7274003130303031002D6A004D415351554552414445
[190365.918524] audit: type=1325 audit(1546514388.013:1333): table=nat family=2 entries=35
[190366.427286] hassio: port 4(veth4aacdcb) entered disabled state
[190366.429307] vetha09061d: renamed from eth0
[190366.557294] hassio: port 4(veth4aacdcb) entered disabled state
[190366.560974] device veth4aacdcb left promiscuous mode
[190366.563435] hassio: port 4(veth4aacdcb) entered disabled state
[190398.421595] hassio: port 4(vetha4cd93a) entered blocking state
[190398.423636] hassio: port 4(vetha4cd93a) entered disabled state
[190398.426530] device vetha4cd93a entered promiscuous mode
[190398.428367] kauditd_printk_skb: 65 callbacks suppressed
[190398.428371] audit: type=1700 audit(1546514420.523:1355): dev=vetha4cd93a prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[190398.429021] IPv6: ADDRCONF(NETDEV_UP): vetha4cd93a: link is not ready
[190398.435433] audit: type=1300 audit(1546514420.523:1355): arch=40000028 syscall=290 per=800000 success=yes exit=40 a0=c a1=132c5b00 a2=28 a3=0 items=0 ppid=1 pid=322 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" key=(null)
[190398.442180] audit: type=1327 audit(1546514420.523:1355): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D73746F726167652D6472697665723D6F7665726C617932002D2D6C6F672D6472697665723D6A6F75726E616C64
[190398.488699] audit: type=1325 audit(1546514420.583:1356): table=nat family=2 entries=21
[190398.491988] audit: type=1300 audit(1546514420.583:1356): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=d5a1f8 items=0 ppid=322 pid=22115 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" key=(null)
[190398.498694] audit: type=1327 audit(1546514420.583:1356): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4100444F434B4552002D7000756470002D6400302F30002D2D64706F7274003130303031002D6A00444E4154002D2D746F2D64657374696E6174696F6E003137322E33302E33332E323A31303030310000002D690068617373696F
[190398.513339] audit: type=1325 audit(1546514420.613:1357): table=filter family=2 entries=33
[190398.516859] audit: type=1300 audit(1546514420.613:1357): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=158eeb0 items=0 ppid=322 pid=22117 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" key=(null)
[190398.524650] audit: type=1327 audit(1546514420.613:1357): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4100444F434B45520000002D690068617373696F002D6F0068617373696F002D7000756470002D64003137322E33302E33332E32002D2D64706F7274003130303031002D6A00414343455054
[190398.536897] audit: type=1325 audit(1546514420.633:1358): table=nat family=2 entries=22
[190400.813584] eth0: renamed from veth5c5d1f5
[190400.852232] IPv6: ADDRCONF(NETDEV_CHANGE): vetha4cd93a: link becomes ready
[190400.856049] hassio: port 4(vetha4cd93a) entered blocking state
[190400.859727] hassio: port 4(vetha4cd93a) entered forwarding state

I hope it helps!

Edit: Oops I just saw your edit after I posted!

NoxHarmonium commented 5 years ago

In the interest of full disclosure, I'll also note that I override port 1900/udp to port 1901 because another service is apparently holding onto port 1900.

Edit: Ah it looks like it is deCONZ. When I stop it I can use port 1900 again. Edit 2: Disabling deCONZ and using port 1900 doesn't seem to fix the issue.

frenck commented 5 years ago

We've found an HA project member that was able to reproduce the issue. We are going to see if we can find out what is causing this.

pvizeli commented 5 years ago

deCONZ use UPnP and maybe this add-on also? I think they need to run on the host network. Otherwise, UPnP doesn't work correctly.

The official deCONZ add-on is correctly set up as host network add-on.

frenck commented 5 years ago

uPNP can actually be removed from the add-on, since it has no function for the supported AP's.

Nevertheless, @NoxHarmonium Already concluded that that was not the issue.

mjrider commented 5 years ago

small debug session on my broken install, conclusions:

the mongod logfile is not shown in the addon output
same for the /data/unifi/logs/server.log
mongodb cannot startup

unifi complains in the log that mongod crashes mongod complains that it cannot initialize the db due to not enough space in disk, this was not true but is a mongodb issue.

adding unifi.db.extraargs=--smallfiles in /data/unifi/data/system.properties let mongodb start without preallocating ±3gb of diskspace and unifi starts normaly after this

frenck commented 5 years ago

Nice @mjrider, thank you very much.

I'm going to test / experiment locally on how this influences currently working installations.
See if the UniFi server log can be redirected to Hass.io add-on log output

pvizeli commented 5 years ago

Good work

jgoffaux commented 5 years ago

Good morning, everyone,

I encountered the same problem that I was able to solve. At first glance the MongoDB database does not start.

1°/ Check of the consistency of the DB :

mongod --dbpath /usr/lib/unifi/data/db --port 27117 --repair

2°/ Start MongoDB

systemctl start mongodb

3°/ Restart Unifi

systemctl restart unifi

For my part, that was enough.

frenck commented 5 years ago

@jgoffaux This is the Hass.io add-on we are talking about, those commands you list won't work on this add-on. Nevertheless, thank you for your input.

Levdbas commented 5 years ago

Can anyone point me in the right direction how to add

unifi.db.extraargs=--smallfiles in /data/unifi/data/system.properties

I'm running hassio and can't find the unifi folder. Probably because of the docker setup? I'm kinda stuck here :(

mnefk commented 5 years ago

@levdbas Just wait and frenck will fix it if he has the time

frenck commented 5 years ago

@Levdbas That needs fixing on our end and is not something you can change. The main issue is providing a migration path for our existing users. This requires testing to guarantee it goes smooth.

Thank you for your patience.

PrivatePuffin commented 5 years ago

Same issue here, luckily before my ubiquity equipment comes in, so i'll be a patient little user @frenck

delikat commented 5 years ago

Same issue here.

frenck commented 5 years ago

I've fixed this in the current code base and will be part of the next release.

addons-assistant[bot] commented 5 years ago

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

hassio-addons / addon-unifi

UniFi Controller stucks on startup #11