I was working with rocket chat for more than a year, using the snap version. suddenly for no reason it gave 502 error. checked the rocketchat-server status and showed:
May 12 22:00:33 ip-172-31-30-219 rocketchat-server.rocketchat-server[3258]: Mongo is not available, can't st
I read in some posts that it could be due to inproper rocketchat update due to skipping multiple mongo versions (i don’t have another mongo on same server) and tried to
snap revert rocketchat-server
Now the mongo is up but rocket chat is just loaded and not active for no reason:
● snap.rocketchat-server.rocketchat-server.service - Service for snap application rocketchat-server.rocketchat-server
Loaded: loaded (/etc/systemd/system/snap.rocketchat-server.rocketchat-server.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2020-05-12 22:24:18 UTC; 5s ago
Process: 6173 ExecStart=/usr/bin/snap run rocketchat-server (code=exited, status=0/SUCCESS)
Main PID: 6173 (code=exited, status=0/SUCCESS)
May 12 22:24:18 ip-172-31-30-219 systemd[1]: Started Service for snap application rocketchat-server.rocketchat-server.
Any help please. or a way to backup the data to restore it on a new server?
I’m having the same exact issue that started yesterday. PLEASE HELP!
My issue fix was very crazy, due to some bug in Rocket.Chat that some people noticed, that services aren’t being started in order (or at least validating on each other while starting), so the crazy fix was i kept restarting both snap.rocketchat-server.rocketchat-server.service and snap.rocketchat-server.rocketchat-mongo.service in a random order, till they are all up. Or just try to first make sure mongo is up, then try to “restart” server service.
We have been talking about that issue in that thread but no permanent fix showed up!!
Thanks for the quick reply Mohammed!
I’m not sure this is my issue, but I’ll give it a try!
I had a similar issue a few months back and found that rolling back the MongoDB fixed the issue. However I can’t find that post and don’t remember how to do it again.
A little more info Mohammed. The server was working just fine then suddenly stopped (without a reboot). After performing a reboot in an attempt to get it working again, I am still unable to get rocket chat to become “active”.
That was the same case we faced, no one was even working on the server back then, just auto-update on rocket chat (a forced update) on mongo caused suddenly that bug to show up and everything became down (502). Tried to roll back, tried to launch another instance …etc all had to auto-update again and causing the issue again (as if infinite closed loop). Try to give restarting services a try (crazy silly solution) but it worked with us. Then you can try to make the delay in service start (sleep 10sec) for example.
If nothing worked with you, you can try to contact their support on https://desk.rocket.chat/portal/en/signin, they may be able to guide you.