MongoDB

How to install MongoDB 4.0

	Note:
	All info is based on SME Server 9 only but I have just started to test on v10 - see notes below

Install Official Repository

This should work for every version of Koozali SME

You may need to change the mongodb version as required

db yum_repositories set mongodb repository \
               BaseURL https://repo.mongodb.org/yum/redhat/\$releasever/mongodb-org/4.0/\$basearch/ \
               EnableGroups no \
               GPGCheck yes \
               Name "MongoDB" \
               GPGKkey https://www.mongodb.org/static/pgp/server-4.0.asc \
               Visible no \
               status disabled

signal-event yum-modify

yum install mongodb-org --enablerepo=mongodb

If refuses to install because of no GPG Key you can change GPGCheck above from Yes to No and try yum install... again or

rpm --import https://www.mongodb.org/static/pgp/server-4.0.asc

yum install mongodb-org --enablerepo=mongodb --nogpgcheck

Start Mongo

	Warning:
	Please check additional notes below before trying this section

	Note:
	If you start mongo like this you will run mongo as root. When mongo later tries to start automatically it may fail because it will be started as the mongod user and won't be able to access the DB files.

/etc/init.d/mongod start

Add the symlinks to start automatically:

ln -s /etc/init.d/mongod /etc/rc.d/rc6.d/K03mongodb
ln -s /etc/init.d/mongod /etc/rc.d/rc7.d/S57mongodb

Optional: create symlink to use mongo or mongodb as service name

ln /etc/init.d/mongod /etc/init.d/mongodb

To ensure everything is all right:

signal-event post-upgrade
signal-event reboot

Additional Notes

Note - I need to test this again This is my initial observation.

As far as I can see, the link above to mongodb is not necessary.

It may need this to set on and off correctly in other service levels:

chkconfig mongod on

Create a service link in in rc7.d:

ln -s /etc/init.d/mongod /etc/rc.d/rc7.d/S57mongod

To use e-smith-service it will need a key:

config set mongod service status enabled

You should now be able to do:

service mongod start|stop|restart etc

Mongo should come up on boot.

Koozali SME v10

	Warning:
	Complete work in progress - here be Dragons!

Install

WIP

db yum_repositories set mongodb42 repository \
              BaseURL https://repo.mongodb.org/yum/redhat/\$releasever/mongodb-org/4.2/\$basearch/ \
              EnableGroups no \
              GPGCheck yes \
              Name "MongoDB" \
              GPGKey https://www.mongodb.org/static/pgp/server-4.2.asc \
              Visible no \
              status disabled

Use the above method to add the repo and then:

yum --enablerepo=mongodb install mongodb-org

We need a db config entry for SME to recognise it:

config set mongod service status enabled access private

We will need a file

mkdir -p /usr/lib/systemd/system/mongod.service.d

nano /usr/lib/systemd/system/mongod.service.d/50koozali.conf

Something like:

[Unit]
After=network.target network.service wan.service
[Install]
WantedBy=sme-server.target

Using keys

config setprop mongod service status enabled

Minimal config I use for Rocket.Chat

grep '^[[:blank:]]*[^[:blank:]#;]' /etc/mongod.conf

systemLog:
 verbosity: 0
 destination: file
 logAppend: true
 path: /var/log/mongodb/mongod.log
storage:
 dbPath: /var/lib/mongo
 journal:
   enabled: true
processManagement:
 fork: true  # fork and run in background
 pidFilePath: /var/run/mongodb/mongod.pid  # location of pidfile
 timeZoneInfo: /usr/share/zoneinfo
net:
 port: 27017
 bindIp: 127.0.0.1  # Enter 0.0.0.0,:: to bind to all IPv4 and IPv6 addresses or, alternatively, use the net.bindIpAll setting.

Enable replication for Rocket.Chat

replication:
 replSetName: rs0

Vaporise or reinitialise the database

	Warning:
	This will totally and utterly vaporise your data. Got a backup?? You have been warned

Remove the directory contents:

rm -rf /var/lib/mongo/*

Or remove the entire directory and recreate it with the correct ownership:

rm -rf /var/lib/mongo
mkdir -p /var/lib/mongo
chown -R mongod:mongod /var/lib/mongo

If you have a replicaset set in /etc/mongod.conf make sure you initiate it:

mongo --eval "printjson(rs.initiate())"

Contents