[support] pducharme's Dockers support thread


Recommended Posts

I would also like to know how to change the recording location to a single hard drive in my array.  I added a location inside the docker setup, however there is not place to change it in the Unifi Video web gui.  Any help would be greatly appreciated and thank you in advance.

Link to comment

You can, it is just very well hidden. If you've fed a *new* path into your docker container to use, Settings -> System Configuration -> Recording Path. Mine is currently set to `/usr/lib/unifi-video/data/videos` which I believe is the default.

 


                              -v /data/unifi-video/data:/var/lib/unifi-video \
                              -v /data/unifi-video/videos:/usr/lib/unifi-video/data/videos \
                              -v /data/unifi-video/logs:/var/log/unifi-video \

 

You can *also* just feed a different path into the docker container. You'd want to *stop* it, move the data from the *old* location to the *new* location, change the paths in your run and then start it back up.

Link to comment

@fryfrog

So if I understand you correctly, if I wanted just the recording to be placed on a single drive (share) on my array then it is something hidden inside the Unifi Video web gui?  I was hoping to have the "program files" remain on the cache drive and have the recorded video on a single drive (share).  I hope I am making sense here, but if you need any further info let me know.

Thanks

Link to comment

I'm afraid I don't use Unraid, so I can't really help you on that end. But this is Docker, so anything you want to do... you have to feed into it. The run command will have a series of arguments that tell you about where the various external files (config, videos, logs) are stored. It is a map that says "here in real life" and "here inside the docker". You can shuffle that around as you see fit, as long as you maintain the *contents* of those directories and point them properly.

For example, if right now you have `/data/videos` as where the videos live and the mapping from real -> docker `/data/videos` -> `/usr/lib/unifi-video/data/videos`, on the outside you can move `/data/videos` to `/whatever/the/hell/you/want` as long as you copy the contents there (so unifi-video doesn't suddenly miss its file) and fix the map. So in the above post, it'd look like `-v /whatever/the/hell/you/want:/usr/lib/unifi-video/data/videos`. See? This would be I think the "docker" way of fixing this and honestly, the simplest.

You *could* actually pass in a new path like `-v /whatever/the/hell/you/want:/this/is/inside` and *inside* the unifi-video app's settings, change the recordings path to `/this/is/inside`. I don't think this is as elegant and clean, but it would work. The downside is that if you wipe your unifi-video, you'll have to remember you did this when you re-set it up.

Link to comment
  • 4 weeks later...

Hello @Pducharme I was wondering if you planed to update these plugins to support the latest betas, and curent stable clients. As betas frequently require updates, especially with UBNT. As of today...

 

Unifi Controller

Stable is at 5.6.29

beta is at 5.7.11

 

Unifi Video

Stable 3.8.5

Beta 3.9.0 Beta 6

 

Would it be possible to update the betas? I will be moving over from the small NVR Unifi sells & their cloud key to my beefy unraid server, but I wont be able to use controller beta versions that are months out of date. With that said, I greatly appreciate you doing what you are doing for the unraid & ubnt community. You may also want to join the ubnt discord too! They post a lot of updates, as some big features have came to Unifi recently, like IPV6, IDS/IPS, and this month we will see 5.8.X as promised by the UBNT staff. Thanks in advance. 

 

Link to comment
1 hour ago, CiSCOTM said:

Hello @Pducharme I was wondering if you planed to update these plugins to support the latest betas, and curent stable clients. As betas frequently require updates, especially with UBNT. As of today...

 

Unifi Controller

Stable is at 5.6.29

beta is at 5.7.11

 

Unifi Video

Stable 3.8.5

Beta 3.9.0 Beta 6

 

Would it be possible to update the betas? I will be moving over from the small NVR Unifi sells & their cloud key to my beefy unraid server, but I wont be able to use controller beta versions that are months out of date. With that said, I greatly appreciate you doing what you are doing for the unraid & ubnt community. You may also want to join the ubnt discord too! They post a lot of updates, as some big features have came to Unifi recently, like IPV6, IDS/IPS, and this month we will see 5.8.X as promised by the UBNT staff. Thanks in advance. 

 

 

Hi @CiSCOTM,  I just updated the Dockerfile for UniFi Video (BETA) to v3.9.0 Beta 6.  I'm already on 3.8.5 on the stable branch (master branch).   I'll also update the UniFi Controller shortly.

 

Please note it take some time at docker.com to compile the new docker build (currently in build for UniFi Video 3.9.0b6... ).

 

** EDIT **

I completed the UniFi Controller too, to the versions you mentioned.  

 

Thanks,

 

Edited by Pducharme
Link to comment
20 minutes ago, Pducharme said:

 

Hi @CiSCOTM,  I just updated the Dockerfile for UniFi Video (BETA) to v3.9.0 Beta 6.  I'm already on 3.8.5 on the stable branch (master branch).   I'll also update the UniFi Controller shortly.

 

Please note it take some time at docker.com to compile the new docker build (currently in build for UniFi Video 3.9.0b6... ).

 

** EDIT **

I completed the UniFi Controller too, to the versions you mentioned.  

 

Thanks,

 

Awesome! Thank you so much!! Cant wait to get everything running on my unraid server from the cloud key! Will copy over the update that runs on the CK at 4 am and test in the AM.

Link to comment

Two times my unRAID server have lost power due to some reason. Every time the configuration for this docker was reset.

When I try to access the docker I get a brand new installation screen.. soo I have to do everything all over again.. Not a delight..

So what can be done about this? Last time it happened I set up to create a DAILY backup of the configuration so that it could be pulled from the docker image and used for a restore.. No luck there either.

 

[2017-12-19 04:00:00,002] <schedule-backup> INFO  system - [server backup] started
[2017-12-19 04:00:00,005] <schedule-backup> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-19 04:00:00,045] <schedule-backup> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-19 04:00:00,291] <schedule-backup> INFO  system - [server backup] end

2017-12-19 21:39:25,308] <launcher> INFO  system - ======================================================================
[2017-12-19 21:39:25,310] <launcher> INFO  system - UniFi 5.5.24 (build atag_5.5.24_9806 - release) is started
[2017-12-19 21:39:25,310] <launcher> INFO  system - ======================================================================
[2017-12-19 21:39:25,317] <launcher> INFO  system - BASE dir:/usr/lib/unifi
[2017-12-19 21:39:25,322] <launcher> INFO  system - Current System IP: 172.17.0.1
[2017-12-19 21:39:25,322] <launcher> INFO  system - Hostname: nas
[2017-12-19 21:39:27,532] <launcher> INFO  db     - waiting for db connection...
[2017-12-19 21:39:28,032] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-19 21:39:33,093] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-19 21:39:33,194] <launcher> INFO  webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v1.0.24 - Gladiator - (built for
Debian-7.0.5-x86_64 on 2017-07-24T01:36:16.000) OpenSSL version: 1.0.2k usrsctp version: d350f4ec3e9bc0ed compiled on machine: Linux debian-7-0-5-64 3.2.0-4-a
md64 #1 SMP Debian 3.2.68-1+deb7u6 x86_64 GNU/Linux
[2017-12-19 21:39:33,401] <inform-1> INFO  inform - from [40:1a:c8:c6:11:10](sw-st-he-ap-ap01, U7PG2, 3.9.3.7537): state=UNKNOWN, ext/stun_ip=10.0.0.8, dev_ip
=10.0.0.8, up=252090
[2017-12-19 21:39:33,409] <inform-1> INFO  dev    -    [state] dev[40:1a:c8:c6:11:10] UNKNOWN->CONNECTED, state_expire=0
[2017-12-19 21:39:33,420] <inform-1> INFO  event  - [event] AP[40:1a:c8:c6:11:100] was connected
[2017-12-19 21:39:33,423] <inform-1> INFO  inform - <<< [setparam] dev[40:1a:c8:c6:11:10]: [blocked_sta, _type, server_time_in_utc]
[2017-12-19 21:39:35,029] <inform-2> INFO  inform - from [40:1a:c8:c6:11:10](sw-st-he-ap-ap01, U7PG2, 3.9.3.7537): state=CONNECTED, ext/stun_ip=10.0.0.8, dev_
ip=10.0.0.8, up=252092
[2017-12-19 21:39:35,267] <inform-3> INFO  inform - from [40:1a:c8:c6:11:10](sw-st-he-ap-ap01, U7PG2, 3.9.3.7537): state=CONNECTED, ext/stun_ip=10.0.0.8, dev_
ip=10.0.0.8, up=252092
[2017-12-19 21:39:35,935] <inform-4> INFO  inform - from [f6:9a:b4:a3:a2:c5](sw-st-he-ap-sw01, US8P60, 3.9.6.7613): state=UNKNOWN, ext/stun_ip=10.0.0.16, dev_
ip=10.0.0.16, up=251751
[2017-12-19 21:39:35,936] <inform-4> INFO  dev    -    [state] dev[f6:9a:b4:a3:a2:c5] UNKNOWN->CONNECTED, state_expire=0
[2017-12-19 21:39:35,939] <inform-4> INFO  event  - [event] Switch[f6:9a:b4:a3:a2:c5] was connected
[2017-12-19 21:39:35,941] <inform-4> INFO  inform - <<< [setparam] dev[f6:9a:b4:a3:a2:c5]: [blocked_sta, _type, server_time_in_utc]
[2017-12-19 21:39:36,663] <discover> INFO  dev    -    [state] dev[a6:9c:a4:c3:c2:a5] UNKNOWN->ADOPTING, state_expire=1513716006
[2017-12-19 21:39:36,663] <discover> INFO  dev    -    [Try Adopt] dev[a6:9c:a4:c3:c2:a5], dev_ip=10.0.0.1, url=http://10.0.0.200:8080/inform
[2017-12-19 21:39:38,173] <inform-5> INFO  inform - from [a6:9c:a4:c3:c2:a5](sw-st-he-ap-fw01, UGW3, 4.4.12.5032482): state=ADOPTING, ext/stun_ip=10.0.0.1, de
v_ip=37.123.143.57, up=253287
[2017-12-19 21:39:38,180] <inform-5> INFO  dev    - saveDeviceAttr(): device[a6:9c:a4:c3:c2:a5][ip]=37.123.143.57 (orig=10.0.0.1)
[2017-12-19 21:39:38,184] <inform-5> INFO  dev    -    [state] dev[a6:9c:a4:c3:c2:a5] ADOPTING->CONNECTED, state_expire=0
[2017-12-19 21:39:38,185] <inform-5> INFO  event  - [event] Gateway[a6:9c:a4:c3:c2:a5] was connected
[2017-12-19 21:39:38,187] <inform-5> INFO  inform - <<< [setparam] dev[a6:9c:a4:c3:c2:a5]: [blocked_sta, _type, server_time_in_utc]
[2017-12-19 21:39:38,188] <ssh> INFO  event  - [event] Gateway[a6:9c:a4:c3:c2:a5] was automatically readopted  

[2017-12-19 21:40:07,778] <db-server> WARN  system - process is interupted: bin/mongod
[2017-12-19 21:40:07,778] <db-server> INFO  db     - DbServer stopped
[2017-12-19 21:40:36,707] <launcher> INFO  system - ======================================================================
[2017-12-19 21:40:36,707] <launcher> INFO  system - UniFi 5.5.24 (build atag_5.5.24_9806 - release) is started
[2017-12-19 21:40:36,707] <launcher> INFO  system - ======================================================================
[2017-12-19 21:40:36,712] <launcher> INFO  system - BASE dir:/usr/lib/unifi
[2017-12-19 21:40:36,715] <launcher> INFO  system - Current System IP: 172.17.0.1
[2017-12-19 21:40:36,715] <launcher> INFO  system - Hostname: nas
[2017-12-19 21:40:39,111] <launcher> INFO  db     - waiting for db connection...
[2017-12-19 21:40:39,611] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-19 21:40:42,188] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-19 21:40:42,284] <launcher> INFO  webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v1.0.24 - Gladiator - (built for
Debian-7.0.5-x86_64 on 2017-07-24T01:36:16.000) OpenSSL version: 1.0.2k usrsctp version: d350f4ec3e9bc0ed compiled on machine: Linux debian-7-0-5-64 3.2.0-4-a
md64 #1 SMP Debian 3.2.68-1+deb7u6 x86_64 GNU/Linux
[2017-12-19 21:40:44,368] <inform-1> INFO  inform - from [40:1a:c8:c6:11:10](sw-st-he-ap-ap01, U7PG2, 3.9.3.7537): state=UNKNOWN, ext/stun_ip=10.0.0.8, dev_ip
=10.0.0.8, up=252161
[2017-12-19 21:40:44,376] <inform-1> INFO  dev    -    [state] dev[40:1a:c8:c6:11:10] UNKNOWN->CONNECTED, state_expire=0
[2017-12-19 21:40:44,388] <inform-1> INFO  event  - [event] AP[40:1a:c8:c6:11:10] was connected
[2017-12-19 21:40:44,391] <inform-1> INFO  inform - <<< [setparam] dev[40:1a:c8:c6:11:10]: [blocked_sta, _type, server_time_in_utc]
[2017-12-19 21:40:45,680] <inform-2> INFO  inform - from [a6:9c:a4:c3:c2:a5](sw-st-he-ap-fw01, UGW3, 4.4.12.5032482): state=UNKNOWN, ext/stun_ip=10.0.0.1, dev
_ip=37.123.143.57, up=253354
[2017-12-19 21:40:45,682] <inform-2> INFO  dev    - saveDeviceAttr(): device[a6:9c:a4:c3:c2:a5][serial]=F09FC217CCA5 (orig=null)
[2017-12-19 21:40:45,689] <inform-2> INFO  dev    -    [state] dev[a6:9c:a4:c3:c2:a5] UNKNOWN->CONNECTED, state_expire=0
[2017-12-19 21:40:45,701] <inform-2> INFO  event  - [event] Gateway[a6:9c:a4:c3:c2:a5] was connected
[2017-12-19 21:40:45,704] <inform-2> INFO  inform - <<< [setparam] dev[a6:9c:a4:c3:c2:a5]: [blocked_sta, _type, server_time_in_utc]
[2017-12-19 21:40:45,812] <inform-3> INFO  inform - from [40:1a:c8:c6:11:10](sw-st-he-ap-ap01, U7PG2, 3.9.3.7537): state=CONNECTED, ext/stun_ip=10.0.0.8, dev_
ip=10.0.0.8, up=252163
[2017-12-19 21:40:45,840] <inform-6> INFO  inform - from [a6:9c:a4:c3:c2:a5](sw-st-he-ap-fw01, UGW3, 4.4.12.5032482): state=CONNECTED, ext/stun_ip=10.0.0.1, d
ev_ip=37.123.143.57, up=253355
[2017-12-19 21:40:46,165] <inform-5> INFO  inform - from [40:1a:c8:c6:11:10](sw-st-he-ap-ap01, U7PG2, 3.9.3.7537): state=CONNECTED, ext/stun_ip=10.0.0.8, dev_
ip=10.0.0.8, up=252163
[2017-12-19 21:40:46,416] <inform-4> INFO  inform - from [a6:9c:a4:c3:c2:a5](sw-st-he-ap-fw01, UGW3, 4.4.12.5032482): state=CONNECTED, ext/stun_ip=10.0.0.1, d
ev_ip=37.123.143.57, up=253355
[2017-12-19 21:40:50,210] <inform-7> INFO  inform - from [f6:9a:b4:a3:a2:c5](sw-st-he-ap-sw01, US8P60, 3.9.6.7613): state=UNKNOWN, ext/stun_ip=10.0.0.16, dev_
ip=10.0.0.16, up=251826
[2017-12-19 21:40:50,211] <inform-7> INFO  dev    -    [state] dev[f6:9a:b4:a3:a2:c5] UNKNOWN->CONNECTED, state_expire=0
[2017-12-19 21:40:50,213] <inform-7> INFO  event  - [event] Switch[f6:9a:b4:a3:a2:c5] was connected
[2017-12-19 21:40:50,214] <inform-7> INFO  inform - <<< [setparam] dev[a6:9c:a4:c3:c2:a5]: [blocked_sta, _type, server_time_in_utc]
                                                                 
[2017-12-20 04:00:00,018] <schedule-backup> INFO  system - [server backup] started
[2017-12-20 04:00:00,037] <schedule-backup> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-20 04:00:00,090] <schedule-backup> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-20 04:00:00,475] <schedule-backup> INFO  system - [server backup] end  
             
[2017-12-21 04:00:00,005] <schedule-backup> INFO  system - [server backup] started
[2017-12-21 04:00:00,037] <schedule-backup> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-21 04:00:00,092] <schedule-backup> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-21 04:00:00,422] <schedule-backup> INFO  system - [server backup] end  
  
[2017-12-22 00:53:27,728] <db-server> WARN  system - process is interupted: bin/mongod
[2017-12-22 00:53:27,728] <db-server> INFO  db     - DbServer stopped
[2017-12-22 00:53:32,423] <launcher> INFO  system - *** Running for the first time, creating identity ***
[2017-12-22 00:53:32,424] <launcher> INFO  system - UUID: 7468169e-966d-4c58-af22-28ab714580cd
[2017-12-22 00:53:32,425] <launcher> INFO  system - ======================================================================
[2017-12-22 00:53:32,425] <launcher> INFO  system - UniFi 5.6.26 (build atag_5.6.26_10236 - release) is started
[2017-12-22 00:53:32,425] <launcher> INFO  system - ======================================================================
[2017-12-22 00:53:32,427] <launcher> INFO  system - BASE dir:/usr/lib/unifi
[2017-12-22 00:53:32,430] <launcher> INFO  system - Current System IP: 172.17.0.1
[2017-12-22 00:53:32,430] <launcher> INFO  system - Hostname: nas
[2017-12-22 00:53:32,431] <launcher> INFO  system - Valid keystore is missing. Generating one ...
[2017-12-22 00:53:32,432] <launcher> INFO  system - Generating Certificate[UniFi]... please wait...
[2017-12-22 00:53:32,716] <launcher> INFO  system - Certificate[UniFi] generated!
[2017-12-22 00:53:33,261] <launcher> INFO  db     - waiting for db connection...
[2017-12-22 00:53:33,761] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-22 00:53:36,120] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-22 00:53:36,285] <launcher> INFO  webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v1.0.27 - Gladiator - (built for Debian-7.0.5-x86_64 on 2017-10-27T00:06:39.000) OpenSSL version: 1.0.2l usrsctp version: a37b2e8937e80109 compiled on machine: Linux debian-7-0-5-64 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u6 x86_64 GNU/Linux

[2017-12-22 08:27:24,672] <launcher> INFO  system - ======================================================================
[2017-12-22 08:27:24,689] <launcher> INFO  system - UniFi 5.6.26 (build atag_5.6.26_10236 - release) is started
[2017-12-22 08:27:24,689] <launcher> INFO  system - ======================================================================
[2017-12-22 08:27:24,693] <launcher> INFO  system - BASE dir:/usr/lib/unifi
[2017-12-22 08:27:24,706] <launcher> INFO  system - Current System IP: 172.17.0.1
[2017-12-22 08:27:24,706] <launcher> INFO  system - Hostname: nas
[2017-12-22 08:27:27,229] <launcher> INFO  db     - waiting for db connection...
[2017-12-22 08:27:27,730] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-22 08:27:30,764] <launcher> INFO  db     - *** Factory Default *** Database exists. Drop it
[2017-12-22 08:27:30,818] <launcher> INFO  db     - waiting for db connection...
[2017-12-22 08:27:32,187] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-22 08:27:32,190] <launcher> INFO  stat   - *** Factory Default *** Stat Database exists. Drop it
[2017-12-22 08:27:32,944] <launcher> INFO  webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v1.0.27 - Gladiator - (built for Debian-7.0.5-x86_64 on 2017-10-27T00:06:39.000) OpenSSL version: 1.0.2l usrsctp version: a37b2e8937e80109 compiled on machine: Linux debian-7-0-5-64 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u6 x86_64 GNU/Linux
[2017-12-22 08:28:32,973] <check-network-interfaces> INFO  system - Interface changed. 3 found: [{ "ip" : "192.168.122.1" , "name" : "virbr0"}, { "ip" : "172.17.0.1" , "name" : "docker0"}, { "ip" : "10.0.0.200" , "name" : "br0"}]
[2017-12-22 08:32:38,466] <db-server> WARN  system - process is interupted: bin/mongod
[2017-12-22 08:32:38,466] <db-server> INFO  db     - DbServer stopped
[2017-12-22 08:33:33,240] <launcher> INFO  system - *** Running for the first time, creating identity ***
[2017-12-22 08:33:33,241] <launcher> INFO  system - UUID: 6a516e98-cff5-403e-ad97-e9800a1a826e
[2017-12-22 08:33:33,242] <launcher> INFO  system - ======================================================================
[2017-12-22 08:33:33,242] <launcher> INFO  system - UniFi 5.6.26 (build atag_5.6.26_10236 - release) is started
[2017-12-22 08:33:33,242] <launcher> INFO  system - ======================================================================
[2017-12-22 08:33:33,243] <launcher> INFO  system - BASE dir:/usr/lib/unifi
[2017-12-22 08:33:33,246] <launcher> INFO  system - Current System IP: 192.168.122.1
[2017-12-22 08:33:33,246] <launcher> INFO  system - Hostname: nas
[2017-12-22 08:33:33,248] <launcher> INFO  system - Valid keystore is missing. Generating one ...
[2017-12-22 08:33:33,248] <launcher> INFO  system - Generating Certificate[UniFi]... please wait...
[2017-12-22 08:33:33,455] <launcher> INFO  system - Certificate[UniFi] generated!
[2017-12-22 08:33:33,969] <launcher> INFO  db     - waiting for db connection...
[2017-12-22 08:33:34,469] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-22 08:33:37,225] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-12-22 08:33:37,433] <launcher> INFO  webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v1.0.27 - Gladiator - (built for Debian-7.0.5-x86_64 on 2017-10-27T00:06:39.000) OpenSSL version: 1.0.2l usrsctp version: a37b2e8937e80109 compiled on machine: Linux debian-7-0-5-64 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u6 x86_64 GNU/Linux

 

/usr/lib/unifi shows the following:

root@nas:/usr/bin# ls -l /usr/lib/unifi/
total 8
drwxr-xr-x 1 root  root   56 Dec 21 23:46 bin
lrwxrwxrwx 1 unifi root   14 Dec 22 08:08 data -> /var/lib/unifi
drwx------ 1 root  root  106 Dec 22 07:34 data.RMy4as2V
drwx------ 1 root  root  144 Dec 22 08:21 db
drwxr-xr-x 1 root  root   16 Dec 21 23:45 dl
drwxr-xr-x 1 root  root 2606 Dec 21 23:46 lib
lrwxrwxrwx 1 unifi root   14 Dec 22 08:08 logs -> /var/log/unifi
drwx------ 1 root  root   20 Dec 22 07:33 logs.LjYeMPjw
drwx------ 1 root  root   66 Dec 22 08:21 run
drwx------ 1 root  root   66 Dec 22 07:33 run.gEBoakb5
drwxr-xr-x 1 root  root    8 Dec 21 23:45 webapps

So it looks like the old config is still there. The question is.. how do get it back.

Unfortunately, I am not able to find any backup files:

 

root@nas:/usr/bin# ls -l /usr/lib/unifi/data.RMy4as2V/backup/autobackup/
total 0
root@nas:/usr/bin# ls -l /usr/lib/unifi/data/backup/autobackup/
total 0

And I am not able to simply do a /etc/init.d/mongod stop, because it will automatically start again.

I did try and do it all in a one liner with the following result:

 

root@nas:/usr/bin# /etc/init.d/mongodb stop && ./mongod --dbpath /usr/lib/unifi/data.RMy4as2V/db --port 27117 --unixSocketPrefix /usr/lib/unifi/run.gEBoakb5
 * Stopping database mongodb
   ...done.
2017-12-22T08:19:20.224+0000 [initandlisten] MongoDB starting : pid=1026 port=27117 dbpath=/usr/lib/unifi/data.RMy4as2V/db 64-bit host=nas
2017-12-22T08:19:20.224+0000 [initandlisten] db version v2.6.10
2017-12-22T08:19:20.224+0000 [initandlisten] git version: nogitversion
2017-12-22T08:19:20.224+0000 [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
2017-12-22T08:19:20.224+0000 [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-12-22T08:19:20.224+0000 [initandlisten] allocator: tcmalloc
2017-12-22T08:19:20.224+0000 [initandlisten] options: { net: { port: 27117, unixDomainSocket: { pathPrefix: "/usr/lib/unifi/run.gEBoakb5" } }, storage: { dbPath: "/usr/lib/unifi/data.RMy4as2V/db" } }
2017-12-22T08:19:20.235+0000 [initandlisten] journal dir=/usr/lib/unifi/data.RMy4as2V/db/journal
2017-12-22T08:19:20.235+0000 [initandlisten] recover begin
2017-12-22T08:19:20.235+0000 [initandlisten] info no lsn file in journal/ directory
2017-12-22T08:19:20.235+0000 [initandlisten] recover lsn: 0
2017-12-22T08:19:20.235+0000 [initandlisten] recover /usr/lib/unifi/data.RMy4as2V/db/journal/j._0
2017-12-22T08:19:20.236+0000 [initandlisten] recover create file /usr/lib/unifi/data.RMy4as2V/db/local.ns 16MB
2017-12-22T08:19:20.300+0000 [initandlisten] recover create file /usr/lib/unifi/data.RMy4as2V/db/local.0 64MB
2017-12-22T08:19:20.523+0000 [initandlisten] recover create file /usr/lib/unifi/data.RMy4as2V/db/ace.ns 16MB
2017-12-22T08:19:20.588+0000 [initandlisten] recover create file /usr/lib/unifi/data.RMy4as2V/db/ace.0 64MB
2017-12-22T08:19:20.822+0000 [initandlisten] recover create file /usr/lib/unifi/data.RMy4as2V/db/ace_stat.ns 16MB
2017-12-22T08:19:20.899+0000 [initandlisten] recover create file /usr/lib/unifi/data.RMy4as2V/db/ace_stat.0 64MB
2017-12-22T08:19:21.151+0000 [initandlisten] recover cleaning up
2017-12-22T08:19:21.151+0000 [initandlisten] removeJournalFiles
2017-12-22T08:19:21.159+0000 [initandlisten] recover done
2017-12-22T08:19:22.091+0000 [initandlisten] ERROR: listen(): bind() failed errno:98 Address already in use for socket: 0.0.0.0:27117
2017-12-22T08:19:22.091+0000 [initandlisten] ERROR:   addr already in use
2017-12-22T08:19:22.092+0000 [initandlisten] now exiting
2017-12-22T08:19:22.092+0000 [initandlisten] dbexit:
2017-12-22T08:19:22.092+0000 [initandlisten] shutdown: going to close listening sockets...
2017-12-22T08:19:22.092+0000 [initandlisten] shutdown: going to flush diaglog...
2017-12-22T08:19:22.092+0000 [initandlisten] shutdown: going to close sockets...
2017-12-22T08:19:22.092+0000 [initandlisten] shutdown: waiting for fs preallocator...
2017-12-22T08:19:22.092+0000 [initandlisten] shutdown: lock for final commit...
2017-12-22T08:19:22.092+0000 [initandlisten] shutdown: final commit...
2017-12-22T08:19:22.122+0000 [initandlisten] shutdown: closing all files...
2017-12-22T08:19:22.123+0000 [initandlisten] closeAllFiles() finished
2017-12-22T08:19:22.123+0000 [initandlisten] journalCleanup...
2017-12-22T08:19:22.123+0000 [initandlisten] removeJournalFiles
2017-12-22T08:19:22.131+0000 [initandlisten] shutdown: removing fs lock...
2017-12-22T08:19:22.131+0000 [initandlisten] dbexit: really exiting now

I am not sure if I didn't set the permission right or if it was just that I used && instead of ; so it had to wait for it to finish, or that the script that sense mongodb going down is just very fast.

 

Any advice?

  • Upvote 1
Link to comment

A question about the UniFi Controller docker if I may.

 

I've just purchased a USG and Pro access point. Totally new to Unify stuff so took it slowly. Installed Docker. Ran through set-up of Controller software. Followed UniFi instructions to SSH on to the USG and change the IP address to be on the same subnet as my Unraid server. Adopted the USG. Disconnected old router. Adopted access point. All great and working brilliantly.

 

Then I was an idiot.

 

Saw in Unraid there was a docker upgrade. Hit Upgrade. Upon returning to the controller software it appeared to be a fresh install? Wanted me to run set-up again or restore from backup. Backup? I am an idiot - no backup yet. Ok, can "transfer" to new controller using admin login/password. Idiot 2™. Safari auto-fill has screwed up my admin password so it wasn't accepted. Ok. Factory reset of both USG and Access Point. Re-install of docker. Would it adopt? Course not. After two hours SSHing in to USG, changing IP and trying to adopt I eventually restored my old router and followed the instruction AGAIN right from the beginning. Adoption fine. Hurrah. Absolutely no idea why my old router was needed, assume routing wasn't correct without it.

 

Made a backup. Quite a few actually.

 

So my question (see, there is one eventually) is What is the recommended update process for the UniFi controller docker? Is it backup -> update -> restore or should the controller remember its settings?

 

I'd just like not to go through this again! 

 

Ps. Thanks for the docker. It's excellent. It's just this user who was an idiot.

Link to comment
38 minutes ago, page3 said:

So my question (see, there is one eventually) is What is the recommended update process for the UniFi controller docker? Is it backup -> update -> restore or should the controller remember its settings?

 

Yes, backup, then upgrade docker, then at the wizard, chose restore.

Link to comment
20 hours ago, Pducharme said:

 

Yes, backup, then upgrade docker, then at the wizard, chose restore.

 

Excellent. Thank you.

 

One more question if I may.

 

I have automatic backups ON. The backup goes to a backup location within the docker (see below). The docker currently maps:

/var/lib/unifi -> /mnt/cache/appdata/unifi/

I thought I could simply add a new route for the backup to expose an external location to the docker, eg:

/usr/lib/unifi/data/backup/autobackup -> /mnt/cache/appdata/unifi/autobackup

(note the /usr rather than /var)

 

The /var/lib/unifi seem to contain the server.log only. The /usr/lib/unifi seems to contain everything else!

 

When starting the docker with the new path added, the UniFi controller had lost all my settings. Removing this mapping fixed things, but obviously auto backups are back to being within the docker image.

 

I believe the question was asked back in April (by lchichiarelli) but I can't find what the resolution was.

 

ps. Happy Christmas!

Edited by page3
Link to comment
  • 2 weeks later...
  • 2 weeks later...

Hi,

 

I've managed to get `pducharme/unifi-video-controller` setup along with my cameras connected to the NVR. However, one thing i'm struggling with is that the controller appears to pick up the wrong IP address:

 

5a5a4062b94fa_2018-01-13at17_15.png.377806b982a8e5bba8222e9928d244db.png

 

I have tried with various types of Network Type configured, but can't appear to get it to use the correct one (which should be 192.168.1.5). This means that since the NVR is assigned to my account, i'm unable to connect to it remotely.

 

Any help would be appreciated, thanks in advance

Ian

Link to comment

Unifi Video 3.9.0 was made available a few weeks ago, so under advanced, I removed the :beta from the docker repository and updated the docker.  Everything seems to be working fine, except it shows as not unavailable in the docker tab.  Any ideas?

 

 

 

 

Screen Shot 2018-01-13 at 12.35.16 PM.png

Edited by luisv
Link to comment
  • 2 weeks later...
  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.