As far as I know, it is not running in multiple instances although I have no idea what that really means. Perhaps some of you Chat+ gurus can help with this.
Error: Rocket.Chat requires oplog tailing when running in multiple instances
Please make sure your MongoDB is on ReplicaSet mode and MONGO_OPLOG_URL environment variable is defined correctly on the application server
Geeks, making the world a better place |
OK, it states Running Instances 4
So, how do I run only one instance? What is an instance?
Geeks, making the world a better place |
OK, it states Running Instances 4
So, how do I run only one instance? What is an instance?
Is your server a quad core?
It may be the software is multi-threaded and is using all the cores. Just a guess. I have not looked into it or its configuration.
https://www.deanbassett.com |
GG, from past experience; with previous Chat+ installs I've done.
- Start with a chat called "chat1"
- Later you decide to drop that one and use "chat2"
- Something happens to chat2 so you start another database named "chat3"
Even though you stopped the chat server and started it with another database, the other "instances" are still open, hence giving more than one running.
Please try this...
https://docs.mongodb.com/manual/tutorial/manage-mongodb-processes/
Read the part about stopping the instances from inside mongod
To ensure a clean shutdown, always shutdown mongod instances using one of the following methods:
ManOfTeal.COM a Proud UNA site, six years running strong! |
GG, from past experience; with previous Chat+ installs I've done.
- Start with a chat called "chat1"
- Later you decide to drop that one and use "chat2"
- Something happens to chat2 so you start another database named "chat3"
Even though you stopped the chat server and started it with another database, the other "instances" are still open, hence giving more than one running.
Please try this...
https://docs.mongodb.com/manual/tutorial/manage-mongodb-processes/
Read the part about stopping the instances from inside mongod
To ensure a clean shutdown, always shutdown mongod instances using one of the following methods:
This is what I have done, I have made sure that any other chat installed was shut down. I wish this server didn't have that bloody PLESK mess on it but it does. I was thinking I should check the pids to see what is running on the system.
I reinstalled Chat+ using a new directory and a new database. That got me into the chat admin since the old one had the oauth entered wrong and form login was turned off.
Today using the mongo shell, I went in to delete any database from the old; I would issue the command, it would return OK but when I used show dbs, it would be listed. So I shut down mongo, I uninstalled mongo, then I went and manually removed the databases. Then I reinstalled mongo and then started chat+; same thing. I get the four instances; does that mean four instances of Chat+ is using the same database? Or does that mean something else? Anyway, I got into the admin after first starting chat+ and I put everything back in for oauth but when going to chat+ and using the oauth button it just a white page.
I need to know that error about instances and Rocket Chat did not make much sense to me; I mean I went to see about removing rooms; no way it seems to do that from the admin; I have to run a script of some sort? Where would one do that? I know one thing, I am not putting this mess on my server; I will tell users flash or just don't chat.
Geeks, making the world a better place |
Newton, I did go to the link you gave. However, this message appears inside of Chat+ with a link to a page on Rocket Chat about how to set up for multiple instances. Since the message is from Chat+ (Rocket Chat) then I would think this is something to do with Chat+ and not mongo. Geeks, making the world a better place |
I just did a show dbs; there are only two databases, the one for the chat and local. I assume local is a database that mongo uses to keep up with certain things; like users etc. Geeks, making the world a better place |
However, this message appears inside of Chat+ with a link to a page on Rocket Chat about how to set up for multiple instances.
Right, but looking at your start.sh or whatever you're using not only does it start the chat+ but the database as well.
export ROOT_URL=https://chat.manofteal.com:3000
export MONGO_URL=mongodb://localhost:27017/mot27
Those are mine. In the past, I would just rename mot27 to something else and that caused what you're seeing.
I had to completely start my whole server install because I couldn't resolve it how you're trying to.
Lucky for me I had my whole years worth of chat backed up.
Afterthought, maybe you could try different port other than 27017.
ManOfTeal.COM a Proud UNA site, six years running strong! |
However, this message appears inside of Chat+ with a link to a page on Rocket Chat about how to set up for multiple instances.
Right, but looking at your start.sh or whatever you're using not only does it start the chat+ but the database as well.
export ROOT_URL=https://chat.manofteal.com:3000
export MONGO_URL=mongodb://localhost:27017/mot27
Those are mine. In the past, I would just rename mot27 to something else and that caused what you're seeing.
I had to completely start my whole server install because I couldn't resolve it how you're trying to.
Lucky for me I had my whole years worth of chat backed up.
Afterthought, maybe you could try different port other than 27017.
This is the start.sh on the server. The asterisk to hide personal information about the site.
export ROOT_URL=https://chat.*******.com/ export MONGO_URL=mongodb://localhost:27017/chat********* export ADMIN_EMAIL=************** export ADMIN_PASS=*************** export PORT=3001
LOG=chat.log
node main.js 2>&1 > $LOG &
I noticed you are specifying the port in the ROOT_URL; I didn't think that was necessary when using the subdomain.
Geeks, making the world a better place |
I did some more checking on my setup.
My mot27 data is located in the root of my server.
I use Ubuntu so - whereis mot27 - gave me the location.
Enter the directory and open this file.
michael@ns1:~/mot27$ nano instances.metadata.json
ManOfTeal.COM a Proud UNA site, six years running strong! |
I added the port but I don't think that changed anything. I need to see if I can get a regular non-admin test account on the site. Still seeing the instances 4 in the admin of chat. Geeks, making the world a better place |
This server is a CentOS or variant of RedHat. l wish I knew more about the instances 4 thing. Maybe one of the Boonex people will come in tomorrow. I am going to see about some other things.
Thanks Newton (and Deano) for your help.
Geeks, making the world a better place |
OK, the instances was that there were four main.js nodes running on the system. I looked up the pids and then killed all main.js on the system. So now I understand what they meant by instances. Searching the Rocket.Chat documentation I couldn't find this. Geeks, making the world a better place |
We can close this thread. I will post a new thread on the current problem. Geeks, making the world a better place |