[support] pducharme's Dockers support thread

[fryfrog]

Sorry about that, I updated beta awhile ago and then pushed it to master, but totally forgot to push it to release and then tag it.

[Ockingshay]

I bit the bullet and updated through the docker.

 

First time i me I trashed it by restarting too soon, so I left it half an hour to install the database. After another length of time the program started fine and I’m on the latest version. 

Edited September 3, 2018 by Ockingshay

[Ockingshay]

1 hour ago, fryfrog said:

Sorry about that, I updated beta awhile ago and then pushed it to master, but totally forgot to push it to release and then tag it.

Looking back at your posts you seems to be part of maintaining this docker? Will you be offering ongoing support for it?

 

many thanks if you are

[fryfrog]

I have been supporting as I can, like I do for a number of other projects.

[David Bott]

Hi...Yes, it would be great to know if this docker will be updated.  Thanks. 

[fryfrog]

It is updated, do you not see the update?

[David Bott]

Sorry to say no. It shows I am on 3.9.7 and on the Docker screen it reads it is Up To Date.

[fryfrog]

You know Docker containers don't update themselves, right? You need to `docker pull` them and restart, or what ever the work flow is in unRAID for doing that. Check out https://hub.docker.com/r/pducharme/unifi-video-controller/ where you can look at the Dockerfile and Build Details and see that it is up to date. My own personal instance is also 3.9.8, so I know it is working.

Good luck!

[David Bott]

Hummm....I know when a my UnRAID see's there is an updated docker it tells me and I click on Update.  Thats all we need to do, we do not need to hunt for an update for once it hits the repository it tells us.  So not sure why this would be any different because this was installed from the repository. Therefore if there's an update, we were expected to show up as an update.  So not sure where it is or why we would not be alerted to update if the Docker package was updated.

 

Thanks

[Squid]

2 minutes ago, David Bott said:

we do not need to hunt for an update for once it hits the repository it tells us

You do have to Check For Updates or have it do that on a schedule, or have CA AutoUpdate installed to install for you automatically.   It's not that "once it hits the repository"

[David Bott]

Yes, it is active.  All my others will show Update and did so actually yesterday.  So I know it is working as it should be. 

 

The interesting thing however, just as an FYI, I just pressed check for updates and it did find it.  So not sure how ofter they are checked, but until I press that, it did not show an update even though last night I had updates for the other dockers waiting.

 

Thanks

[Squid]

2 minutes ago, David Bott said:

So not sure how ofter they are checked,

 

4 minutes ago, David Bott said:

even though last night I had updates for the other dockers waiting

Assuming your other apps are from LSIO, they were actually updated August 31st.

[David Bott]

Yup, it is set for one a week. So likely it was not updated yet when it last ran.    But the docker update ran just fine, so all good good now.  Thanks guys!

[spyd4r]

would it be possible to have someone update the beta branch to include the new unifi video 3.9.9-beta2? I tried in my clone of the branch but kept having issues i couldn't solve with the patch.

Edited September 24, 2018 by spyd4r

[fryfrog]

Done.

It looks like they did some fiddling w/ their unifi-video bash script because I had to re-create the patch we apply to it. Please let us know if it doesn't work! It *builds*, but I'm not gonna test it on my setup!

[spyd4r]

fryfrog, thanks for the last update.. can you try updating the beta branch to the new 3.10 beta 1?

 

https://community.ubnt.com/t5/UniFi-Video-Beta/UniFi-Video-3-10-0-Beta-1-Release/m-p/2513135#M19784

[fryfrog]

Will do!

[fryfrog]

Done, I also updated it to use mongodb 3.6... so hopefully that works!

[Diode663]

I keep hanging when upgrading to 3.10 beta 1.  On the website it just shows updating forever.   Looking over at the beta forums it seems to be a common problem.

[fryfrog]

You're probably going to have to dig in and see what is what. In one of the beta images, I updated mongodb to 3.6 and that don't fly w/o updating the db itself to be compatible. Mine was at 3.2 features, so it failed. I reverted that and added some stuff to bring db to 3.4.

Look at startup output, look at logs, see what is going on.

[fryfrog]

FWIW, it was very obvious in the logs. My instance was starting mongodb up over and over and over and over.

[Diode663]

I am afraid I have no experience with mogodb.  I looked at the logs and as you said mongo was just in a restart loop.

 

[fryfrog]

Saying what? Mine was saying something about needing 3.4 features on 3.6. Is it possible your db is even older?

You can flip back to the 3.9.9 docker and make changes to the db.

 

You can docker exec into the container and run mongo --quiet --eval "db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )" localhost:7441 to see what version it is set to.

mongo --quiet --eval 'db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )' localhost:7441

 

Will set it to 3.4.

But so would the latest beta, have you pulled recently?

[Diode663]

It just said that the connection timed out.  I tried the first command but it comes up as mongo not found.

 

Is it possible i just didnt wait long enough for the DB to convert?  The docker log didnt really give me any indication that something was actually happening.

 

I was on the previous beta and pulled down new docker about an hour ago and it seemed to be stuck on upgrading maybe I will try it again since i tried to go back to the latest branch and broke everything.

[Diode663]

I pulled the latest beta and this is what the error log shows:

 

1538543889.216 2018-10-03 01:18:09.216/EDT: ERROR  [uv.db.svc] Failed to acquire client connection Interrupted while waiting to connect in MongoDb-Connecting
1538543899.217 2018-10-03 01:18:19.217/EDT: ERROR  [uv.db.svc] Failed to acquire client connection Timed out after 10000 ms while waiting to connect. Client view of cluster state is {type=Unknown, servers=[{address=127.0.0.1:7441, type=Unknown, state=Connecting, exception={com.mongodb.MongoException$Network: Exception opening the socket}, caused by {java.net.ConnectException: Connection refused (Connection refused)}}] in MongoDb-Connecting

 

This is from the mongo log:

 

2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten] MongoDB starting : pid=4628 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=8ff897d7fbb2
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten] db version v3.4.17
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten] git version: 7c14a47868643bb691a507a92fe25541f998eca4
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2n  7 Dec 2017
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten] allocator: tcmalloc
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten] modules: none
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten] build environment:
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten]     distmod: ubuntu1604
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten]     distarch: x86_64
2018-10-03T01:18:22.710-0400 I CONTROL  [initandlisten]     target_arch: x86_64
2018-10-03T01:18:22.710-0400 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" } }
2018-10-03T01:18:22.743-0400 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
2018-10-03T01:18:22.743-0400 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2018-10-03T01:18:22.743-0400 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-7441.sock
2018-10-03T01:18:22.743-0400 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2018-10-03T01:18:22.743-0400 I CONTROL  [initandlisten] now exiting
2018-10-03T01:18:22.743-0400 I CONTROL  [initandlisten] shutting down with code:100

 

It looks like the old db was stored as wiredtiger but it isnt converting it.