[support] pducharme's Dockers support thread

[rlbdesigns]

I installed this docker and then had some issues with the setup. But deleted the docker and reinstalled it. But after reinstall it put me at the sign in screen not the setup and name NVR. How do I do a clean install.

Edited January 6, 2019 by rlbdesigns

[Gog]

On 1/6/2019 at 1:50 PM, rlbdesigns said:

I installed this docker and then had some issues with the setup. But deleted the docker and reinstalled it. But after reinstall it put me at the sign in screen not the setup and name NVR. How do I do a clean install.

delete the docker and also delete the appdata subdirectory for the docker

[mikeydk]

I just installed the Unifi controller docker, but how do I update it? The controller is currently at 5.9.29, but the docker is only at 5.6.37

[Pducharme]

On 1/24/2019 at 1:52 AM, mikeydk said:

I just installed the Unifi controller docker, but how do I update it? The controller is currently at 5.9.29, but the docker is only at 5.6.37

Please use the branch 5.9.29.  Since after 5.6.x, Ubiquiti is deprecating some stuff, I seperate it.  Please edit your Docker setting and use :5.9.29 instead of :latest .  also, be sure to add Port 8883 since it's an additional port for that version.

 

[fryfrog]

Quote

Please use the branch 5.9.29.  Since after 5.6.x, Ubiquiti is deprecating some stuff, I seperate it.  Please edit your Docker setting and use :5.9.29 instead of :latest .

I'd strongly suggest reversing that. *Most* people are going to want the latest version and `:latest` literally implies that. It should track the latest release. I'd create a tag for the last stable of the deprecated line, like `:5.6.x` or something. If you go the route you're suggesting, everyone will have to update their docker run line every time. And people are going to ask about this over and over and over and over.

[Spyderturbo007]

On 1/28/2019 at 10:01 AM, Pducharme said:

Please use the branch 5.9.29.  Since after 5.6.x, Ubiquiti is deprecating some stuff, I seperate it.  Please edit your Docker setting and use :5.9.29 instead of :latest .  also, be sure to add Port 8883 since it's an additional port for that version.

 

 

How do I go about using the branch so I can get the latest version?  I keep getting the 5.6.x version.

[Hoopster]

1 hour ago, Spyderturbo007 said:

 

How do I go about using the branch so I can get the latest version?  I keep getting the 5.6.x version.

Uhhh, he just told you what to do. Edit the docker settings and replace :latest with :5.9.29 in the repository name.

 

Ubiquiti has two branches of UniFi; LTS - long-term support (which is 5.6.x branch) and Stable (currently, the 5.9.x branch).  The ":latest" tag is going to pull from the LTS branch.  If you want the "Stable (often very unstable as it is is the current testing/development branch)" branch, you need to specify the branch release number as the repository tag as the author has indicated.

 

I use a different UniFi docker and it refers to the Ubiquiti "Stable" branch with the ":unstable" tag which is more accurate.  The ":latest" tag in that docker also pulls from the LTS branch.

 

Ubiquiti's latest releases in the "stable" branch are often very unstable and bleeding edge and cause lots of issues.  I have been running the 5.9.29 release for a couple of months now and it seem to be OK; however, I held off for several weeks before updating to the 5.9.x line until the problem reports in their forums settled down with the release of 5.9.29.

[mrossh13]

This docker completely stopped working for me a week ago. I've deleted the docker, deleted the directory, did a complete reinstall, and it states it can't reach the server on chrome. Any ideas would be welcomed.

[trurl]

15 minutes ago, mrossh13 said:

This docker completely stopped working for me a week ago. I've deleted the docker, deleted the directory, did a complete reinstall, and it states it can't reach the server on chrome. Any ideas would be welcomed.

You could start by telling us which docker you are even talking about, since more than one is supported in this thread.

[mrossh13]

Pducharme Unifi Video

[fryfrog]

What do you see in logs, either Docker's or Unifi Video's?

[mrossh13]

13 minutes ago, fryfrog said:

What do you see in logs, either Docker's or Unifi Video's?

I see the following in the docker log

 

2019-02-06 11:39:12.581354 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-02-06 11:39:12.651430 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-02-06 11:39:12.722212 [info] Setting permissions recursively on volume mappings...

 

I don't see anything in regards to that docker in the system log

 

[ElBurrito]

17 minutes ago, mrossh13 said:

I see the following in the docker log

 

2019-02-06 11:39:12.581354 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-02-06 11:39:12.651430 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-02-06 11:39:12.722212 [info] Setting permissions recursively on volume mappings...

 

I don't see anything in regards to that docker in the system log

 

My controller is stuck starting up and I am seeing the same thing as you. I found this in another log file, be curious to see if you are seeing the same thing.

Here are the errors I see:

/usr/lib/unifi-video/data/db/WiredTiger.wt: handle-open: open: Operation not permitted
Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 277

 

This chuck keeps repeating. Guessing the DB can't come up or something.

tail -f /var/log/unifi-video/mongod.log

2019-02-06T13:49:07.008-0600 I CONTROL  [main] ***** SERVER RESTARTED *****
2019-02-06T13:49:07.012-0600 I CONTROL  [initandlisten] MongoDB starting : pid=8183 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=cbc8a953dbae
2019-02-06T13:49:07.012-0600 I CONTROL  [initandlisten] db version v3.4.18
2019-02-06T13:49:07.012-0600 I CONTROL  [initandlisten] git version: 4410706bef6463369ea2f42399e9843903b31923
2019-02-06T13:49:07.012-0600 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2n  7 Dec 2017
2019-02-06T13:49:07.012-0600 I CONTROL  [initandlisten] allocator: tcmalloc
2019-02-06T13:49:07.012-0600 I CONTROL  [initandlisten] modules: none
2019-02-06T13:49:07.013-0600 I CONTROL  [initandlisten] build environment:
2019-02-06T13:49:07.013-0600 I CONTROL  [initandlisten]     distmod: ubuntu1604
2019-02-06T13:49:07.013-0600 I CONTROL  [initandlisten]     distarch: x86_64
2019-02-06T13:49:07.013-0600 I CONTROL  [initandlisten]     target_arch: x86_64
2019-02-06T13:49:07.013-0600 I CONTROL  [initandlisten] options: { net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", journal: { enabled: true }, mmapv1: { smallFiles: true } }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } }
2019-02-06T13:49:07.048-0600 I -        [initandlisten] Detected data files in /usr/lib/unifi-video/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-02-06T13:49:07.048-0600 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=15039M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),
2019-02-06T13:49:07.060-0600 E STORAGE  [initandlisten] WiredTiger error (1) [1549482547:60504][8183:0x14b2e30cf180], file:WiredTiger.wt, connection: /usr/lib/unifi-video/data/db/WiredTiger.wt: handle-open: open: Operation not permitted
2019-02-06T13:49:07.061-0600 I -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 277
2019-02-06T13:49:07.062-0600 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating
2019-02-06T13:49:07.062-0600 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2019-02-06T13:49:07.062-0600 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-7441.sock
2019-02-06T13:49:07.062-0600 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2019-02-06T13:49:07.062-0600 I CONTROL  [initandlisten] now exiting
2019-02-06T13:49:07.062-0600 I CONTROL  [initandlisten] shutting down with code:100

[stormshaker]

Looks like 3.10.1 has been approved for general release:

 

https://community.ubnt.com/t5/UniFi-Video-Blog/UniFi-Video-3-10-1-Full-Release/ba-p/2674717

 

Any chance you could update the docker?

 

Thanks,

James

 

 

[fryfrog]

@stormshaker, done but the github -> docker link up isn't working, so I'll ask @Pducharme to trigger it manually.

[spyd4r]

This broke my install because of the wiredTiger changes, which i understand.. but I can't even get this to start on a fresh install with 3.10.1...

 

 I deleted all my existing folders in relation to the container.. Still no go, trying to gather logs. 

 

 

it appears it's using an older mongo conf file which uses mmap_v1? and the mongo install is still 3.4 but unifi is 3.10.1

 

root@e50858fa7931:/var/log/unifi-video# dpkg --list | grep -i mongo
ii  mongodb-org-server           3.4.19                            amd64        MongoDB database server
ii  mongodb-org-shell            3.4.19                            amd64        MongoDB shell client
root@e50858fa7931:/var/log/unifi-video# dpkg --list | grep -i unifi
ii  unifi-video                  3.10.1                            amd64        Ubiquiti Networks UniFi Video controller

 

 

 

-----  END BACKTRACE  -----
2019-02-15T14:56:11.834-0500 I CONTROL  [main] ***** SERVER RESTARTED *****
2019-02-15T14:56:11.837-0500 I CONTROL  [initandlisten] MongoDB starting : pid=4189 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=e50858fa7931
2019-02-15T14:56:11.837-0500 I CONTROL  [initandlisten] db version v3.4.19
2019-02-15T14:56:11.837-0500 I CONTROL  [initandlisten] git version: a2d97db8fe449d15eb8e275bbf318491781472bf
2019-02-15T14:56:11.837-0500 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2n  7 Dec 2017
2019-02-15T14:56:11.838-0500 I CONTROL  [initandlisten] allocator: tcmalloc
2019-02-15T14:56:11.838-0500 I CONTROL  [initandlisten] modules: none
2019-02-15T14:56:11.838-0500 I CONTROL  [initandlisten] build environment:
2019-02-15T14:56:11.838-0500 I CONTROL  [initandlisten]     distmod: ubuntu1604
2019-02-15T14:56:11.838-0500 I CONTROL  [initandlisten]     distarch: x86_64
2019-02-15T14:56:11.838-0500 I CONTROL  [initandlisten]     target_arch: x86_64
2019-02-15T14:56:11.838-0500 I CONTROL  [initandlisten] options: { config: "/usr/lib/unifi-video/conf/mongodv3.0+.conf", net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, operationProfiling: { mode: "off", slowOpThresholdMs: 500 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", engine: "mmapv1", journal: { enabled: true }, mmapv1: { preallocDataFiles: true, smallFiles: true }, syncPeriodSecs: 60.0 }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } }
2019-02-15T14:56:11.863-0500 I JOURNAL  [initandlisten] journal dir=/usr/lib/unifi-video/data/db/journal
2019-02-15T14:56:11.863-0500 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
2019-02-15T14:56:11.864-0500 I CONTROL  [initandlisten] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes;  b=0x559a580de000 Invalid argument
2019-02-15T14:56:11.864-0500 I -        [initandlisten] Fatal Assertion 13515 at src/mongo/db/storage/mmap_v1/logfile.cpp 248
2019-02-15T14:56:11.864-0500 I -        [initandlisten]

***aborting after fassert() failure

2019-02-15T14:56:11.873-0500 F -        [initandlisten] Got signal: 6 (Aborted).

 0x559a548a27d1 0x559a548a19e9 0x559a548a1ecd 0x14f306a7a890 0x14f3066b5e97 0x14f3066b7801 0x559a53b369c5 0x559a54531370 0x559a54506084 0x559a54506675 0x559a5450d966 0x559a544ffb95 0x559a54475985 0x559a53b22dc3 0x559a53b42876 0x14f306698b97 0x559a53ba2a29

 

 

 

Edited February 15, 2019 by spyd4r

[fryfrog]

@spyd4r, what tag are you using? Both :beta and :testing have MongoDB 4.0. This will *only* run a db at featureversion 3.6 (or 4.0). You need to drop down to the db your existing db supports and upgrade it. In the master and beta branches (:testing and :beta), there are commit points that have 3.4, 3.6 and 4.0. And because the upgrade script was addded *before* those points, all you need to do is start up at each of those points. When you run the 3.4, it'll set your 3.2 db to 3.4 (if needed). When you run the 3.6, it'll set your 3.4 to 3.6 (if needed), finally when you hit the 4.0 image it'll upgrade your 3.6 to 4.0.

Or does 4.10.1 *require* mongodb 4.0 to work?

[stormshaker]

Hmm, the docker updated but I still have 3.9.12. There are no in-app updates available, either.

[fryfrog]

Ha, I picked and pushed all the *support* stuff... but never actually updated the version. Sorry!

[Pducharme]

Do i need to trigger annoter build@fryfrog?


Envoyé de mon iPad en utilisant Tapatalk

[fryfrog]

I think I need to research if 3.10.1 *requires* MongoDB 4.0 before I push the update to `:latest`.

[fryfrog]

@stormshaker: In the mean time, you're welcome to experiment by switching to `:testing` or `:beta`. *Right now*, they're what `:latest` would end up being if I pushed all the changes to it.

[stormshaker]

OK, I’ll do that, and report back.

[spyd4r]

4 hours ago, fryfrog said:

@spyd4r, what tag are you using? Both :beta and :testing have MongoDB 4.0. This will *only* run a db at featureversion 3.6 (or 4.0). You need to drop down to the db your existing db supports and upgrade it. In the master and beta branches (:testing and :beta), there are commit points that have 3.4, 3.6 and 4.0. And because the upgrade script was addded *before* those points, all you need to do is start up at each of those points. When you run the 3.4, it'll set your 3.2 db to 3.4 (if needed). When you run the 3.6, it'll set your 3.4 to 3.6 (if needed), finally when you hit the 4.0 image it'll upgrade your 3.6 to 4.0.

Or does 4.10.1 *require* mongodb 4.0 to work?

I used :beta on a fresh container initialization and it still didn't work correctly.. so i'm not sure. I'm don't think it needs 4.0 as I believe Unifi is still pushing 3.4 on the cloudkeys if i am not mistaken.

[stormshaker]

I switched from :latest to :beta and it stuck on Upgrading in the WebUI. /var/lib/unifi-video/logs/mongod.log says:

2019-02-16T13:04:35.783+1030 I CONTROL  [initandlisten] options: { config: "/usr/lib/unifi-video/conf/mongodv3.0+.conf", net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, operationProfiling: { mode: "off", slowOpThresholdMs: 500 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", engine: "mmapv1", journal: { enabled: true }, mmapv1: { preallocDataFiles: true, smallFiles: true }, syncPeriodSecs: 60.0 }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } }
2019-02-16T13:04:35.802+1030 I STORAGE  [initandlisten] exception in initAndListen: 28662 Cannot start server. Detected data files in /usr/lib/unifi-video/data/db created by the 'wiredTiger' storage engine, but the specified storage engine was 'mmapv1'., terminating
 

My install isn't critical, so I might try a fresh install on the :beta branch.