Unifi 5.7 on Ubuntu 18.04

scottalanmiller

There is a pretty simple fix. Just do this...

systemctl stop unifi
systemctl stop mongodb
mv /usr/bin/mongod mongod.bin

Then create a new /usr/bin/mongod with these contents:

#!/bin/bash
cleaned_args=$(echo $* | sed -e 's/--nohttpinterface//')
exec /usr/bin/mongod.bin ${cleaned_args}

And then run:

chmod +x /usr/bin/mongod
systemctl start mongodb
systemctl start unifi

And voila.

JaredBusch

Ubiquiti clearly tells you not to use MongoDB 3.6

0_1527656680581_675bef0f-787d-4881-8e33-2e999958fd65-image.png

scottalanmiller

@jaredbusch works great with the simple change, though.

JaredBusch

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch works great with the simple change, though.

Then you might want to submit it to [email protected] or post on their forums.

scottalanmiller

@jaredbusch said in Unifi 5.7 on Ubuntu 18.04:

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch works great with the simple change, though.

Then you might want to submit it to [email protected] or post on their forums.

They have the info on their forums too, just not easy to find. It's a configuration issue with 3.6, not an issue with 3.6 itself. Part of the defaults, I believe, were changed so you just have to change how MongoDB 3.6 starts and the Unifi is perfectly happy with it and you get a modern Ubuntu, fully managed and faster MongoDB for it all, too

DustinB3403

I was going to post this over the long weekend as I was doing a distribution update and had the same issue.

Once I saw Ubiquity said to not use 3.6 I just reverted to 17.04

PenguinWrangler

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch said in Unifi 5.7 on Ubuntu 18.04:

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch works great with the simple change, though.

Then you might want to submit it to [email protected] or post on their forums.

They have the info on their forums too, just not easy to find. It's a configuration issue with 3.6, not an issue with 3.6 itself. Part of the defaults, I believe, were changed so you just have to change how MongoDB 3.6 starts and the Unifi is perfectly happy with it and you get a modern Ubuntu, fully managed and faster MongoDB for it all, too

Not easy to find info in UBNT forums? Wow never heard of that! They need a better way to get important info to the users. I don't know how many times there was an easy solution to a problem I had but I had to DIG through their forums to find it. Not a simple search but dig and read post after post till I found the right one.

JaredBusch

@penguinwrangler said in Unifi 5.7 on Ubuntu 18.04:

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch said in Unifi 5.7 on Ubuntu 18.04:

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch works great with the simple change, though.

Then you might want to submit it to [email protected] or post on their forums.

They have the info on their forums too, just not easy to find. It's a configuration issue with 3.6, not an issue with 3.6 itself. Part of the defaults, I believe, were changed so you just have to change how MongoDB 3.6 starts and the Unifi is perfectly happy with it and you get a modern Ubuntu, fully managed and faster MongoDB for it all, too

Not easy to find info in UBNT forums? Wow never heard of that! They need a better way to get important info to the users. I don't know how many times there was an easy solution to a problem I had but I had to DIG through their forums to find it. Not a simple search but dig and read post after post till I found the right one.

This was right in the release note highlighted in red. How much more clear do you want?

BRRABill

@jaredbusch said in Unifi 5.7 on Ubuntu 18.04:

@penguinwrangler said in Unifi 5.7 on Ubuntu 18.04:

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch said in Unifi 5.7 on Ubuntu 18.04:

@scottalanmiller said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch works great with the simple change, though.

Then you might want to submit it to [email protected] or post on their forums.

They have the info on their forums too, just not easy to find. It's a configuration issue with 3.6, not an issue with 3.6 itself. Part of the defaults, I believe, were changed so you just have to change how MongoDB 3.6 starts and the Unifi is perfectly happy with it and you get a modern Ubuntu, fully managed and faster MongoDB for it all, too

Not easy to find info in UBNT forums? Wow never heard of that! They need a better way to get important info to the users. I don't know how many times there was an easy solution to a problem I had but I had to DIG through their forums to find it. Not a simple search but dig and read post after post till I found the right one.

This was right in the release note highlighted in red. How much more clear do you want?

What are the options?

krisleslie

@jaredbusch if they give me a brew of coffee I'd read it

scottalanmiller

@dustinb3403 said in Unifi 5.7 on Ubuntu 18.04:

I was going to post this over the long weekend as I was doing a distribution update and had the same issue.

Once I saw Ubiquity said to not use 3.6 I just reverted to 17.04

I thought 17.10 was still 3.4 as well. Maybe not.

dbeato

This worked but make sure that when you say to do this:

mv /usr/bin/mongod mongod.bin

Be sure to be on the /usr/bin folder when doing so or do the following

mv /usr/bin/mongod /usr/bin/mongod.bin

JaredBusch

@dbeato said in Unifi 5.7 on Ubuntu 18.04:

This worked but make sure that when you say to do this:
mv /usr/bin/mongod mongod.bin
Be sure to be on the /usr/bin folder when doing so or do the following
mv /usr/bin/mongod /usr/bin/mongod.bin

I know what you are trying to say, but saying it like that is clear as mud..

dbeato

@jaredbusch said in Unifi 5.7 on Ubuntu 18.04:

@dbeato said in Unifi 5.7 on Ubuntu 18.04:
This worked but make sure that when you say to do this:
mv /usr/bin/mongod mongod.bin
Be sure to be on the /usr/bin folder when doing so or do the following
mv /usr/bin/mongod /usr/bin/mongod.bin
I know what you are trying to say, but saying it like that is clear as mud..

What can I say or add to make it clearer?

JaredBusch

@dbeato said in Unifi 5.7 on Ubuntu 18.04:

@jaredbusch said in Unifi 5.7 on Ubuntu 18.04:
@dbeato said in Unifi 5.7 on Ubuntu 18.04:
This worked but make sure that when you say to do this:
mv /usr/bin/mongod mongod.bin
Be sure to be on the /usr/bin folder when doing so or do the following
mv /usr/bin/mongod /usr/bin/mongod.bin
I know what you are trying to say, but saying it like that is clear as mud..
What can I say or add to make it clearer?

this is a basic file move command. the source and destination are always relative to your pwd.

It is totally poor form to discuss file source and destinations without clearly stating where to start, or explicitly noting them.

You also used the word "on" instead of "in" and did not syntax highlight what you are talking about.

Now based on the OP, and the lack of telling a user to be in the /usr/bin folder, the assumed intention here is to move and rename the existing /usr/bin/mongod to ~/mongod.bin

You are unclearly trying to state that you simply need to rename mongod to mongod.bin while keeping it in the /usr/bin/ folder.

@scottalanmiller needs to clarify his intent in the OP.

dbeato

Reason for me to revisit this post was due to the following Ubiquiti forum post
https://community.ubnt.com/t5/UniFi-Wireless/Unifi-controller-on-Ubuntu-18-04/td-p/2331657

CCWTech

Scott, why did you go with Ubuntu vs. Fedora? (Asking for a friend)

dbeato

@ccwtech said in Unifi 5.7 on Ubuntu 18.04:

Scott, why did you go with Ubuntu vs. Fedora? (Asking for a friend)

There are no official Unifi installers for RHEL or Fedora distributions.

CCWTech

Sorry, I meant Debian not Fedora.

JaredBusch

@ccwtech said in Unifi 5.7 on Ubuntu 18.04:

Sorry, I meant Debian not Fedora.

Because Ubuntu is steaming dog poo?

Solved Unifi 5.7 on Ubuntu 18.04