Ok I found the FAQ where it says to delete the docker.img and recreate it and then reinstall the app throught the Community Application's Previous Apps section.

 

This is Greek to me since I have not touch Docker in a long time.  Can someone point me to how to delete the docker.img?  Do I do it at the command line?

 

Edit:  Never mind, I found in the release notes how to go about fixing the problem.  Thanks.

So I upgraded unRAID from V6.1.9 to 6.2.3.  Then I deleted the docker.img and reinstall UniFi from the Community App Previous Apps.

 

Now I have the newest Unifi running, but all my settings were lost.  Can someone verify that all host port docker settings are the same between Unifi V 5.07 and 5.2.9?

 

My main problem is that my AP is on a different subnet and now the controller cannot detect it.  With the previous version, the controller was able to detect my AP on the different subnet.  I do have the DHCP option 43 to inform the AP that the controller is on my unRAID server IP.

 

I can't understand why my controller does not detect my AP.  Do I need to reboot my AP?

Thank you for the UniFi Video docker. I'm loving that I can do this via a docker.

 

Quick question, when you go into Settings, does it show an IP address that makes no sense? My docker is http://unraidIP:7080/ and I successfully point my cameras to unraidIP. However, the IP showing up under Settings is 172.17.0.4. Is this basically an unused and non-configurable setting that simply doesn't matter because this is running as a docker? Nothing about my network uses the 172 subnet. I don't see where I can change this value either.

 

P.S. I'm using this for my docker icon, which can be adjusted in the docker's advanced settings... http://i.imgur.com/CJjSBdJ.png

Hi!

 

The 172.x.x.x IP range is the Internal Dockers IP.  It is normal to see it there.  It's the IP that the docker gets internally.

 

Glad it's useful for you, I maintain it for my own use, but why not sharing it !

 

Nice Icon!

Any idea why I get the error below when using the UniFi Video docker?

 

2017-01-14 13:34:51,354 ERROR Unable to locate appender ConsoleErrorAppender for logger uv.login

 

2017-01-14 13:34:51,355 ERROR Unable to locate appender ConsoleErrorAppender for logger uv.stream

 

OpenJDK 64-Bit Server VM warning: You have loaded library /usr/lib/unifi-video/lib/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'.

 

no, never saw that error before.  Are you on Unraid 6.2.4 or on an upcoming Beta of 6.3.x ?

no, never saw that error before.  Are you on Unraid 6.2.4 or on an upcoming Beta of 6.3.x ?

 

I'm on 6.2.4

Hi Pducharme, are you able to upload the UniFi Video Controller docker to v3.5.2?

Hello!

 

Just added this to my unraid server. After it's started, I navigate to the web interface and am presented with a login screen, but I should get a setup wizard.

 

I found the system.properties file and it is one line that reads "is_default=true"

 

Then restarted the app and still same thing.

 

Any help getting the setup wizard?

 

Thanks,

 

PS - am on unraid 6.2.4

Any idea why I get the error below when using the UniFi Video docker?

 

2017-01-14 13:34:51,354 ERROR Unable to locate appender ConsoleErrorAppender for logger uv.login

 

2017-01-14 13:34:51,355 ERROR Unable to locate appender ConsoleErrorAppender for logger uv.stream

 

OpenJDK 64-Bit Server VM warning: You have loaded library /usr/lib/unifi-video/lib/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'.

 

I see this error too

I seriously cannot get the Unifi-Video container to work. system.properties is never generated. So, I followed the instructions on the docker hub and put it in the unifi-video/videos file that gets generated by the container. I restart the program and its still not accepting any passwords.

 

Also, why is my recording path linked to /videos in the docker settings but when I navigate to the file structure "videos" is its own empty file and my recordings path is also its own file.

 

 

Can someone help me out here?

I seriously cannot get the Unifi-Video container to work. system.properties is never generated. So, I followed the instructions on the docker up and put it in the unifi-video/videos file that gets generated by the container. I restart the program and its still not accepted any passwords.

 

Also, why is my recording path linked to /videos in the docker settings but when I navigate to the file structure "videos" is its own empty file and my recordings path is also its own file.

 

 

Can someone help me out here?

 

You have to create the system.properties file and put it inside the unifi-video folder. Re-start the docker and then it will prompt you to create an account and setup the NVR

 

I'm having the same issue for the recorded video files. It's storing them in "/usr/lib/unifi-video/data/videos" when i specified in the docker i want them in "/mnt/cache/recordings/nvr"

 

Hopefully Pducharme can help here. Not sure what's going on

 

Thanks for the tip. So I just put the system.properties in the roof of the docker config file, not under "videos"? I'll try it today.

Thanks for the tip. So I just put the system.properties in the roof of the docker config file, not under "videos"? I'll try it today.

 

Correct.

Thank you! That worked!

 

Also figured out how to get my recording directory linked properly.

 

Just edit the docker and add a new path, set the container path to "/usr/lib/unifi-video/data/*your desired name*" (mine is "/usr/lib/unifi-video/data/recordings"). Link your host recording path to the container path. Voila! docker exec -it into the container to confirm that the path exists. Once that is done, login into NVR and changed your recording path to "/usr/lib/unifi-video/data/*your desired name*"

 

 

Hello!

 

Just added this to my unraid server. After it's started, I navigate to the web interface and am presented with a login screen, but I should get a setup wizard.

 

I found the system.properties file and it is one line that reads "is_default=true"

 

Then restarted the app and still same thing.

 

Any help getting the setup wizard?

 

Thanks,

 

PS - am on unraid 6.2.4

 

found system.properties file in unifi-video root and added "is_default=true" and amazing, it works!

UniFi Video Docker :  I updated the UniFi Video to latest version 3.6.0.

UniFi Controller :  I updated the UniFi Controller to latest version 4.5.9.

 

** NOTE **

 

Before upgrading your docker of UniFi Controller, save your parameters so you can restore at the first launch after the upgrade.

Any suggestion for cameras that don't record?

 

I have cam set to record all the time and still nothing. I've checked the folder maps. All seems good, but just no recording.

 

NEVERMIND!!! Found in the log that is showed the disk space to not be sufficient even though it should have had 20GB to play with. I changed free space allotment to the entire disk and it's recording now...

glad you found it because I had no idea!

FYI,

 

02.06.17 - UniFi - Update UniFi Controller to 5.4.11 version.

02.09.17 - UniFi-Video-Controller - Update UniFi-Video-Controller to 3.6.1.

 

** BACKUP YOUR SETTINGS BEFORE updating UniFi Docker.  You'll be able to restore your settings from the backup file.

Did anyone else get an access denied error putting system.properties in the video folder for unifi-video?

Having some trouble getting out of the gate on this one. Could use some assistance if anyone could be so kind to lend a hand?

 

Just reading through thread, it seems it's necessary to create system.properties, which I did. Once I restarted, some new data was written to that file. So seems like progress. However, when I open the webui, it still says "Update in Progress..." at the Unifi splash page. I've let it sit there for 10 minutes, restarted the docker a few times. No joy.

 

Don't know if it's helpful, but here are the contents of /unifi-vdeo and the contents of system.properties

 

root@unRAID:/mnt/user/appdata/unifi-video# ls -l

total 12

drwxr-xr-x 1 root root  96 Feb 16 19:34 db/

-rw-r--r-- 1 root root 2204 Feb 16 19:03 keystore

-rw-rw-rw- 1 root root  279 Feb 16 19:29 system.properties

-rw-r--r-- 1 root root  32 Feb 16 19:03 truststore

root@unRAID:/mnt/user/appdata/unifi-video# cat system.properties

# unifi-video v3.6.1

#Thu Feb 16 19:29:58 CST 2017

is_default=true

uuid=81b521b0-5f8c-4376-9b8c-2efcac4a00cf

# app.http.port = 7080

# app.https.port = 7443

# ems.liveflv.port = 6666

# ems.livews.port = 7445

# ems.livewss.port = 7446

# ems.rtmp.port = 1935

# ems.rtsp.port = 7447

 

 

Here is the server.log, looks to be a Mongodb problem? This just repeats over and over.

 

2017-02-16T19:38:34.237-0600 git version: nogitversion

2017-02-16T19:38:34.237-0600 OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016

- not using --noprealloc in mongodb

1487295514.241 2017-02-16 19:38:34.241/CST: INFO  MongoDb server starting, dbdir=/usr/lib/unifi-video/data/db, port=7441 in mongodb

1487295514.241 2017-02-16 19:38:34.241/CST: INFO  MongoDB server started, acquiring client connection in app-event-bus-0

1487295514.348 2017-02-16 19:38:34.348/CST: INFO  mongod has quit with rc: 14 in mongodb

1487295514.348 2017-02-16 19:38:34.348/CST: INFO  MongoDb server stopped in mongodb

 

Here is the Mongodb log,

 

2017-02-16T19:45:20.540-0600 [initandlisten] SEVERE: Got signal: 6 (Aborted).

Backtrace:0xedb3e9 0xeda3a5 0x2b0ae65ce4b0 0x2b0ae65ce428 0x2b0ae65d002a 0xe4a213 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2b0ae65b9830 0x61a2d9

bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9]

bin/mongod() [0xeda3a5]

/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x2b0ae65ce4b0]

/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x2b0ae65ce428]

/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x2b0ae65d002a]

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) [0x2b0ae65b9830]

bin/mongod(_start+0x29) [0x61a2d9]

2017-02-16T19:45:30.944-0600 ***** SERVER RESTARTED *****

2017-02-16T19:45:30.945-0600 [initandlisten] MongoDB starting : pid=272 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=553fd764528a

2017-02-16T19:45:30.945-0600 [initandlisten] db version v2.6.10

2017-02-16T19:45:30.945-0600 [initandlisten] git version: nogitversion

2017-02-16T19:45:30.945-0600 [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016

2017-02-16T19:45:30.945-0600 [initandlisten] build info: Linux lgw01-12 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 BOOST_LIB_VERSION=1_58

2017-02-16T19:45:30.945-0600 [initandlisten] allocator: tcmalloc

2017-02-16T19:45:30.945-0600 [initandlisten] options: { net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", journal: { enabled: true }, smallFiles: true }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } }

2017-02-16T19:45:30.962-0600 [initandlisten] journal dir=/usr/lib/unifi-video/data/db/journal

2017-02-16T19:45:30.962-0600 [initandlisten] recover : no journal files present, no recovery needed

2017-02-16T19:45:30.962-0600 [initandlisten] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes;  b=0x384a000 errno:22 Invalid argument

2017-02-16T19:45:30.962-0600 [initandlisten] Fatal Assertion 13515

2017-02-16T19:45:30.964-0600 [initandlisten] 0xedb3e9 0xe6fb3f 0xe4a1c1 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2b9099f49830 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) [0x2b9099f49830]

bin/mongod(_start+0x29) [0x61a2d9]

2017-02-16T19:45:30.964-0600 [initandlisten]

 

***aborting after fassert() failure

 

On 2/11/2017 at 11:48 PM, Pducharme said:

FYI,

 

02.06.17 - UniFi - Update UniFi Controller to 5.4.11 version.

02.09.17 - UniFi-Video-Controller - Update UniFi-Video-Controller to 3.6.1.

 

** BACKUP YOUR SETTINGS BEFORE updating UniFi Docker.  You'll be able to restore your settings from the backup file.

I got a container upgrade notice today, backed up, upgraded and restored as usual - noticed I'm on 5.5.5 unstable. Is there anyway to limit only stable releases?

I got a container upgrade notice today, backed up, upgraded and restored as usual - noticed I'm on 5.5.5 unstable. Is there anyway to limit only stable releases?

Damn it, I thought It was stable. Next time will check more, but not sure we can downgrade easily now...

I wont update it untill the 5.5.5 becomes stable release.


Envoyé de mon iPhone en utilisant Tapatalk

12 hours ago, Pducharme said:

 

Damn it, I thought It was stable. Next time will check more, but not sure we can downgrade easily now...

I wont update it untill the 5.5.5 becomes stable release.


Envoyé de mon iPhone en utilisant Tapatalk

 

Hey no worries!!! Thanks for the awesome work. I just thought I was going crazy when I couldn't find the release notes and then worried I did something! :-)