[Support] Linuxserver.io - Unifi

[saarg]

Was the update pushed already?  I'm still showing no new updates and i'm on 5.3.10 controller.

 

Is there a way I can manually update the docker on my side as I can download the updates via Ubnt?

 

image will be updated on friday as part of our regular weekly image refresh schedule.

 

Thanks. Update came through and working fine.

 

Did you push the check for updates button?

[mickeykool]

EDIT - I ended up removing the docker and reinstalling it.  Restored my config and now its 5.4.9.

 

Yes and it says no new updates.

 

I'm getting app updates but seems updates not working in docker?  I see previous post says the latest unifi update is 5.4.9.

 

posted the update log....

 

Pulling image: pducharme/unifi:latest

IMAGE ID [latest]: Pulling from pducharme/unifi.

Status: Image is up to date for pducharme/unifi:latest

 

TOTAL DATA PULLED: 0 B

 

Stopping container: UniFi

Successfully stopped container 'UniFi'

 

Removing container: UniFi

Successfully removed container 'UniFi'

 

Command:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="UniFi" --net="host" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -e "TCP_PORT_8081"="8081" -e "TCP_PORT_8082"="8082" -e "TCP_PORT_8443"="8443" -e "TCP_PORT_8843"="8843" -e "TCP_PORT_8880"="8880" -v "/mnt/cache/appdata/unifi/":"/var/lib/unifi":rw pducharme/unifi

3a3f1eb64da1eb3176139dd3663fee5aa9429472383ab52d3412fe85d2a4e15f

 

The command finished successfully!

[saarg]

EDIT - I ended up removing the docker and reinstalling it.  Restored my config and now its 5.4.9.

 

Yes and it says no new updates.

 

I'm getting app updates but seems updates not working in docker?  I see previous post says the latest unifi update is 5.4.9.

 

posted the update log....

 

Pulling image: pducharme/unifi:latest

IMAGE ID [latest]: Pulling from pducharme/unifi.

Status: Image is up to date for pducharme/unifi:latest

 

TOTAL DATA PULLED: 0 B

 

Stopping container: UniFi

Successfully stopped container 'UniFi'

 

Removing container: UniFi

Successfully removed container 'UniFi'

 

Command:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="UniFi" --net="host" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -e "TCP_PORT_8081"="8081" -e "TCP_PORT_8082"="8082" -e "TCP_PORT_8443"="8443" -e "TCP_PORT_8843"="8843" -e "TCP_PORT_8880"="8880" -v "/mnt/cache/appdata/unifi/":"/var/lib/unifi":rw pducharme/unifi

3a3f1eb64da1eb3176139dd3663fee5aa9429472383ab52d3412fe85d2a4e15f

 

The command finished successfully!

 

You're not using our version, so why are you posting in our thread?

[mickeykool]

 

You're not using our version, so why are you posting in our thread?

 

Well when i first starting using Docker i think the older unifi was only one on "app store" which is why I downloaded it.  Till today i deleted the docker and searched the App store and I see 2 unifi apps, so i downloaded your app.  Sorry for confusion. 

 

Everything is working now. 

[hernandito]

Hi,

 

I just got a brand new AP... the Pro version. I installed the Docker and no luck, I am also getting:

 

[services.d] starting services
[services.d] done.
OpenJDK 64-Bit Server VM warning: You have loaded library /usr/lib/unifi/lib/native/Linux/amd64/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'.
OpenJDK 64-Bit Server VM warning: You have loaded library /usr/lib/unifi/lib/native/Linux/amd64/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'.

 

It will not detect my new AP device. I tried installing the Windows version, and it does detect the device. I did NOT set it up in Windows though.

 

Did anyone ever manage to solve this? I tried a reset of the AP and same result. But if anyone knows the trick, please share.

 

Thanks,

 

H.

[Dimtar]

I literally did this like 3 days ago, the Docker wouldn't find the AP until I set it to host mode. I set it back after I adopted the AP and everything has worked fine from there.

[hernandito]

I literally did this like 3 days ago, the Docker wouldn't find the AP until I set it to host mode. I set it back after I adopted the AP and everything has worked fine from there.

 

Thank you Dimtar.... it worked perfectly. I set back to Bridge mode after configuring the AP and it showed the AP as disconnected. I guess I will leave it on Host mode. I hope that is OK.

 

Thanks again!!

 

 

H.

[JonathanM]

 

It's not related to bridge mode. The AP doesn't know where the controller is unless you have your DHCP server specifically set up to issue the controller address as an option in the lease. Normally you would use the UniFi discovery tool to find the AP and tell it the IP of the controller, but the UniFi dockers don't have the discovery tool as it is a separate app.

 

To get the AP to show up in the controller so it can be adopted and provisioned, do the following:

 

Determine the IP the AP was leased

SSH to that IP

Login as ubnt / ubnt

mca-cli

set-inform http://address:port/inform (where address is IP of controller and port is the port you are using for inform, default is 8080)

 

Once you run the set inform command it should show in the controller. As soon as you click adopt you need to run the set inform command a second time on the AP.

 

EDIT: Syntax correction

[hernandito]

 

It's not related to bridge mode. The AP doesn't know where the controller is unless you have your DHCP server specifically set up to issue the controller address as an option in the lease. Normally you would use the UniFi discovery tool to find the AP and tell it the IP of the controller, but the UniFi dockers don't have the discovery tool as it is a separate app.

 

To get the AP to show up in the controller so it can be adopted and provisioned, do the following:

 

Determine the IP the AP was leased

SSH to that IP

Login as ubnt / ubnt

mca-cli

set-inform http://address:port/inform (where address is IP of controller and port is the port you are using for inform, default is 8080)

 

Once you run the set inform command it should show in the controller. As soon as you click adopt you need to run the set inform command a second time on the AP.

 

EDIT: Syntax correction

 

Thank you Jonathan.... this did not work. First time I was able to do this, It never mentioned the "adopt" thing. It was just plain connected. When I went back to host mode, the same thing after running the commands above. I am ONLY using the AP with my Dlink router. I do not have anything else Unifi other than the single AP.

 

Thanks,

 

H.

[Dimtar]

I literally did this like 3 days ago, the Docker wouldn't find the AP until I set it to host mode. I set it back after I adopted the AP and everything has worked fine from there.

 

Thank you Dimtar.... it worked perfectly. I set back to Bridge mode after configuring the AP and it showed the AP as disconnected. I guess I will leave it on Host mode. I hope that is OK.

 

Thanks again!!

 

 

H.

 

I think in theory running host mode is ok but just less ideal? Glad you got connected.

[wayner]

Hi, I need help configuring the Unifi Controller docker.  I am new to unRAID but I have been running the Unifi controller for a couple of years under Windows.  I am currently running 3.2.7 on a 32 bit Windows 7 installation with five APs.

 

In my current Unifi system.properties file there are only the following lines that aren't commented out:

is_default=false
unifi.http.port=8888
uuid=9512799f-7e23-4d29-b013-3XXXXXXXX

When I look at the default system.properties it shows:

# each unifi instance requires a set of ports:
#
# unifi.http.port=8080     # device inform
# unifi.https.port=8443    # controller UI / API
# portal.http.port=8880    # portal redirect port for HTTP
# portal.https.port=8843   # portal redirect port for HTTPs
# unifi.db.port=27117      # local-bound port for DB server

So am I correct in assuming that in the docker setup Host Port 1 maps to unifi.http.port, Host Port 2 maps to portal.http.port, Host Port 3 maps to unifi.https.port, Host Port 4 maps to portal.https.port and Host Port 5 maps to unifi.db.port?

 

Is this documented anywhere?

 

For my existing Win based controller I access my controller via a web browser at port 8443 although I always get complaints about certificates.  If I try to access at http - 8888 it seems to redirect to https - port 8443.

 

So, what settings should I enter for the ports in the docker config?  I can't use 8080 as that is already being used by the SageTV docker contain for its web UI.  So should I continue to use 8888, assuming that it doesn't conflict with anything else on docker?

 

So once I get all of this setup then what is the process?  Do I forget them on my Windows controller and adopt them on my Docker Controller?

 

I don't know if this makes a difference but I have my Access Points set up as static IPs of 192.168.1.2-6 rather than use DHCP.

[CHBMB]

Just use the template and leave everything as default.  We set it up to work out the box.

[wayner]

Just use the template and leave everything as default.  We set it up to work out the box.

But I am already using port 8080 for something else.  Won't that cause contention for that port since that is one of the defaults for the ports?

 

When I go to tower:8080 it hits my SageTV web UI.  If I install this docker with defaults I am pretty sure that tower:8080 may now try to go to the Unifi web UI.

[CHBMB]

Just use the template and leave everything as default.  We set it up to work out the box.

But I am already using port 8080 for something else.  Won't that cause contention for that port since that is one of the defaults for the ports?

 

When I go to tower:8080 it hits my SageTV web UI.  If I install this docker with defaults I am pretty sure that tower:8080 may now try to go to the Unifi web UI.

 

You can try changing just the host port on Unifi then.  But Unifi may not like that, I don't know, I don't use it.  If at all possible I would change the host port for SageTV.

[hernandito]

Just use the template and leave everything as default.  We set it up to work out the box.

But I am already using port 8080 for something else.  Won't that cause contention for that port since that is one of the defaults for the ports?

 

When I go to tower:8080 it hits my SageTV web UI.  If I install this docker with defaults I am pretty sure that tower:8080 may now try to go to the Unifi web UI.

 

I also used 8080 and 8081 in other dockers. In unifi, I changed to 8580 and 8581 and had no issues other than the bridge mode issue discussed a few posts above. Port 8443 gave me trouble changing. Hopefully this one is not used on something else.

 

 

[dalben]

It's not related to bridge mode. The AP doesn't know where the controller is unless you have your DHCP server specifically set up to issue the controller address as an option in the lease. Normally you would use the UniFi discovery tool to find the AP and tell it the IP of the controller, but the UniFi dockers don't have the discovery tool as it is a separate app.

 

To get the AP to show up in the controller so it can be adopted and provisioned, do the following:

 

Determine the IP the AP was leased

SSH to that IP

Login as ubnt / ubnt

mca-cli

set-inform http://address:port/inform (where address is IP of controller and port is the port you are using for inform, default is 8080)

 

Once you run the set inform command it should show in the controller. As soon as you click adopt you need to run the set inform command a second time on the AP.

 

Thanks you.  After three hours or so thinking I can do it on my own, I found this post and got it up in minutes

[Cstolworthy]

I just recently installed the Unifi docker via unraid.  However whenever I have tried to access the Web UI, it would never respond. To ensure a cleaner state, I removed the container entirely and deleted the data directory. I then re-setup a container (didn't user the my-unifi option available in the interface, and went with defaults on everything except data directory.). I have attached the log files from that run to this post.

 

From what I can gather, Mongo is failing to start which makes the controller fail to boot. This is where things start to die:

 

2017-02-01T23:18:18.577-0800 [initandlisten] journal dir=/usr/lib/unifi/data/db/journal
2017-02-01T23:18:18.578-0800 [initandlisten] recover : no journal files present, no recovery needed
2017-02-01T23:18:18.578-0800 [initandlisten] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes;  b=0x3846000 errno:22 Invalid argument
2017-02-01T23:18:18.578-0800 [initandlisten] Fatal Assertion 13515
2017-02-01T23:18:18.580-0800 [initandlisten] 0xedb3e9 0xe6fb3f 0xe4a1c1 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2ba0ddfd3830 0x61a2d9 
bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9]
bin/mongod(_ZN5mongo10logContextEPKc+0x21f) [0xe6fb3f]
bin/mongod(_ZN5mongo13fassertFailedEi+0x71) [0xe4a1c1]
bin/mongod(_ZN5mongo7LogFile17synchronousAppendEPKvm+0x29b) [0xe7039b]
bin/mongod(_ZN5mongo3dur20_preallocateIsFasterEv+0x22a) [0x8869fa]
bin/mongod(_ZN5mongo3dur19preallocateIsFasterEv+0x2a) [0x886f3a]
bin/mongod(_ZN5mongo3dur16preallocateFilesEv+0x966) [0x88ea86]
bin/mongod(_ZN5mongo3dur7startupEv+0x74) [0x87d184]
bin/mongod(_ZN5mongo14_initAndListenEi+0x76f) [0x61f92f]
bin/mongod(_ZN5mongo13initAndListenEi+0x23) [0x620903]
bin/mongod(main+0x23c) [0x5e943c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x2ba0ddfd3830]
bin/mongod(_start+0x29) [0x61a2d9]
2017-02-01T23:18:18.580-0800 [initandlisten] 

 

After this, it throws one more exception(below) before restarting the process:

 

***aborting after fassert() failure


2017-02-01T23:18:22.703-0800 [initandlisten] SEVERE: Got signal: 6 (Aborted).
Backtrace:0xedb3e9 0xeda3a5 0x2ade19e344b0 0x2ade19e34428 0x2ade19e3602a 0xe4a213 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2ade19e1f830 0x61a2d9 
bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9]
bin/mongod() [0xeda3a5]
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x2ade19e344b0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x2ade19e34428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x2ade19e3602a]
bin/mongod(_ZN5mongo13fassertFailedEi+0xc3) [0xe4a213]
bin/mongod(_ZN5mongo7LogFile17synchronousAppendEPKvm+0x29b) [0xe7039b]
bin/mongod(_ZN5mongo3dur20_preallocateIsFasterEv+0x22a) [0x8869fa]
bin/mongod(_ZN5mongo3dur19preallocateIsFasterEv+0x2a) [0x886f3a]
bin/mongod(_ZN5mongo3dur16preallocateFilesEv+0x966) [0x88ea86]
bin/mongod(_ZN5mongo3dur7startupEv+0x74) [0x87d184]
bin/mongod(_ZN5mongo14_initAndListenEi+0x76f) [0x61f92f]
bin/mongod(_ZN5mongo13initAndListenEi+0x23) [0x620903]
bin/mongod(main+0x23c) [0x5e943c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x2ade19e1f830]
bin/mongod(_start+0x29) [0x61a2d9]

 

Let me know if there is anything else I can provide.

Thanks!

mongod.txt

server.txt

[saarg]

I just recently installed the Unifi docker via unraid.  However whenever I have tried to access the Web UI, it would never respond. To ensure a cleaner state, I removed the container entirely and deleted the data directory. I then re-setup a container (didn't user the my-unifi option available in the interface, and went with defaults on everything except data directory.). I have attached the log files from that run to this post.

 

From what I can gather, Mongo is failing to start which makes the controller fail to boot. This is where things start to die:

 

2017-02-01T23:18:18.577-0800 [initandlisten] journal dir=/usr/lib/unifi/data/db/journal
2017-02-01T23:18:18.578-0800 [initandlisten] recover : no journal files present, no recovery needed
2017-02-01T23:18:18.578-0800 [initandlisten] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes;  b=0x3846000 errno:22 Invalid argument
2017-02-01T23:18:18.578-0800 [initandlisten] Fatal Assertion 13515
2017-02-01T23:18:18.580-0800 [initandlisten] 0xedb3e9 0xe6fb3f 0xe4a1c1 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2ba0ddfd3830 0x61a2d9 
bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9]
bin/mongod(_ZN5mongo10logContextEPKc+0x21f) [0xe6fb3f]
bin/mongod(_ZN5mongo13fassertFailedEi+0x71) [0xe4a1c1]
bin/mongod(_ZN5mongo7LogFile17synchronousAppendEPKvm+0x29b) [0xe7039b]
bin/mongod(_ZN5mongo3dur20_preallocateIsFasterEv+0x22a) [0x8869fa]
bin/mongod(_ZN5mongo3dur19preallocateIsFasterEv+0x2a) [0x886f3a]
bin/mongod(_ZN5mongo3dur16preallocateFilesEv+0x966) [0x88ea86]
bin/mongod(_ZN5mongo3dur7startupEv+0x74) [0x87d184]
bin/mongod(_ZN5mongo14_initAndListenEi+0x76f) [0x61f92f]
bin/mongod(_ZN5mongo13initAndListenEi+0x23) [0x620903]
bin/mongod(main+0x23c) [0x5e943c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x2ba0ddfd3830]
bin/mongod(_start+0x29) [0x61a2d9]
2017-02-01T23:18:18.580-0800 [initandlisten] 

 

After this, it throws one more exception(below) before restarting the process:

 

***aborting after fassert() failure


2017-02-01T23:18:22.703-0800 [initandlisten] SEVERE: Got signal: 6 (Aborted).
Backtrace:0xedb3e9 0xeda3a5 0x2ade19e344b0 0x2ade19e34428 0x2ade19e3602a 0xe4a213 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2ade19e1f830 0x61a2d9 
bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9]
bin/mongod() [0xeda3a5]
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x2ade19e344b0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x2ade19e34428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x2ade19e3602a]
bin/mongod(_ZN5mongo13fassertFailedEi+0xc3) [0xe4a213]
bin/mongod(_ZN5mongo7LogFile17synchronousAppendEPKvm+0x29b) [0xe7039b]
bin/mongod(_ZN5mongo3dur20_preallocateIsFasterEv+0x22a) [0x8869fa]
bin/mongod(_ZN5mongo3dur19preallocateIsFasterEv+0x2a) [0x886f3a]
bin/mongod(_ZN5mongo3dur16preallocateFilesEv+0x966) [0x88ea86]
bin/mongod(_ZN5mongo3dur7startupEv+0x74) [0x87d184]
bin/mongod(_ZN5mongo14_initAndListenEi+0x76f) [0x61f92f]
bin/mongod(_ZN5mongo13initAndListenEi+0x23) [0x620903]
bin/mongod(main+0x23c) [0x5e943c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x2ade19e1f830]
bin/mongod(_start+0x29) [0x61a2d9]

 

Let me know if there is anything else I can provide.

Thanks!

 

I have no problem here.

Could you post your run command? Just do a change somewhere, then change it back and hit apply. Then you should have the run command.

[Cstolworthy]

The run command is:

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="unifi" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8080:8080/tcp -p 8081:8081/tcp -p 8443:8443/tcp -p 8843:8843/tcp -p 8880:8880/tcp -v "/mnt/user/appdata/unifi/config/":"/config":rw linuxserver/unifi
5a11219372e77d33f4313fc86afbbb608333d70324a10308329d869c2d798019

[saarg]

The run command is:

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="unifi" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8080:8080/tcp -p 8081:8081/tcp -p 8443:8443/tcp -p 8843:8843/tcp -p 8880:8880/tcp -v "/mnt/user/appdata/unifi/config/":"/config":rw linuxserver/unifi
5a11219372e77d33f4313fc86afbbb608333d70324a10308329d869c2d798019

 

Do you have any of the ports used for other containers? Push the deployed ports text and check.

Could you try using /mnt/cache/appdata instead of /mnt/user/appdata if you have a cache disk. If you don't, use one of the array disks.

[Cstolworthy]

Do you have any of the ports used for other containers? Push the deployed ports text and check.

Could you try using /mnt/cache/appdata instead of /mnt/user/appdata if you have a cache disk. If you don't, use one of the array disks.

 

Interesting, I changed the data drive to the cache drive and everything started working fine.

[saarg]

Do you have any of the ports used for other containers? Push the deployed ports text and check.

Could you try using /mnt/cache/appdata instead of /mnt/user/appdata if you have a cache disk. If you don't, use one of the array disks.

 

Interesting, I changed the data drive to the cache drive and everything started working fine.

 

Probably got something to do with hard linking files. I didn't get the same error here, but I didn't try to use a fresh appdata folder when testing both cache and user.

[Vynce]

Any idea why the latest build downgraded from 5.4.9 to 5.3.11?

[StevenD]

Any idea why the latest build downgraded from 5.4.9 to 5.3.11?

 

Holy crap!  Thank you for pointing that out.  Now i know why my US-16-XGs dropped out of the controller.

[mickeykool]

Any idea why the latest build downgraded from 5.4.9 to 5.3.11?

 

I noticed this too.