New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to start rocketchat-server (snap) on Ubuntu 18.04 - Start request repeated too quickly. #12288
Comments
Think you need to try and debug rocket starting to see what is going on. Something like this may help get more information (always worth a search on the interwebs first when you get an issue) https://askubuntu.com/questions/783979/how-do-i-debug-snaps There may be other links that will help you get a log of rocket starting |
I tried
|
Hmmm (I've never used snaps so just doing some basic searching which you could try too......) https://askubuntu.com/questions/784489/how-do-system-services-work-in-snaps My guess is there is something wrong with rocket being able to connect, either to the outside world or mongo or somesuch. If we read here we can see the interface names Ahhhh..... and just foudn this https://rocket.chat/docs/installation/manual-installation/ubuntu/snaps/#faq See the last section. |
I never used snap too. Rocket chat is my first snap use. But it is recommended install method on rocket.chat web, so I tried it. |
Have you checked Mongo is running as per the FAQs? Have you looked at the logs via this? (note this is a bug tracker, not really a support forum, so you need to do a bit of heavy lifting yourself here...... if you have not used snaps before it might help to read more about them etc) |
I reinstalled Ubuntu on my VPS - nothing change, still the same error. Mongo is not running. If I start it I have clean install of ubuntu 18.04.1 server. So there are no conflicts with other apps. If I would have old installation of debian(7,8)/ubuntu(14.04/16.04) or not standard configuration, I will understand problem. But on clean ubuntu server installation? There are logs (I cannot find more useful logs).:
|
Can you please go back and fill in some of the details from the bug template (you should ALWAYS do this whenever you report an issue as it saves a lot of time and questions) https://rocket.chat/docs/contributing/reporting-issues/ Particularly make a note of your hardware/processor as I believe there is a potential race condition on ARM though I am not sure that is relevant here. I'm pretty sure something went awry on your install and I think we probably need to get @geekgonecrazy to take a look as he seems to be the snap guru :-) |
Description:I have clean install of Ubuntu 18.04.1 and only core snap package installed. After install of snap rocket-server, everything is ok. But after I restart snap.rocketchat-server.rocketchat-server.service or reboot server, rocket-chat do not start. Multiple restart of service do not help. I reinstalled Ubuntu on my VPS - nothing change, still the same error. Mongo is not running. If I start it systemctl start snap.rocketchat-server.rocketchat-mongo.service, it fails. Steps to reproduce:
Expected behavior:Restart snap.rocketchat-server.rocketchat-server.service or reboot server do not break rocketchat-server :-) Actual behavior:After restart is not possible to start rocket.chat server again. Server Setup Information:
Additional contextUpgrade apt packages do not help. I have second VPS (1GB RAM, 20GB SSD) with Debian 9 and rocket.chat server works without any problem. VPS:
|
what do the logs show when you restart it that way? I'd recommend using: If so for sure check logs: https://rocket.chat/docs/installation/manual-installation/ubuntu/snaps/#how-can-i-view-the-logs |
@geekgonecrazy |
Yes if I had to guess I would say for some reason mongo isn't wanting to come up. So its logs will likely tell the true tale |
Sometime vendors customize Ubuntu in ways that can make it less stable.. That Cloud provider isn't listed here: https://partners.ubuntu.com/find-a-partner multipass launch -n rocket daily:18.04 (multipass is a command to get Ubuntu easily). I'd watch out for trying to restart the service before it's fully ready. Other than that, I'd suspect some sort of customization on the cloud... |
I installed Rocket.Chat snap 0.69.2 on Debian 9.5 (the same cloud - forpsicloud.cz) and it works great. I'm sorry, but I don't have time to trying Rocket.Chat on Ubuntu. So for me problem was "solved". |
i'll go ahead and close this out. @BryanQuigley yes I think it must be this. If they compile their own kernel snaps seem to never work exactly as expected on Ubuntu. Seen it caused by everything from missing squashfs to tweaked apparmor. |
I have the same issue here and think it is a simple timing issue. It only happens after a complete reboot of the server. If I come back to it and just do a simple So the solution here would be to tell the startup scripts to do the whole thing a bit slower, still have to figure out how this is possible with systemd, so if anyone has an idea, I am all ears. to clarify: `Sep 10 08:56:29 xxx rocketchat-server.rocketchat-mongo[2421]: 2019-09-10T08:56:29.796+0000 I REPL [ReplicationExecutor] Exited primary catch-up mode. Sep 10 08:56:31 xxx rocketchat-server.rocketchat-mongo[2421]: 2019-09-10T08:56:31.725+0000 I REPL [rsSync] transition to primary complete; database writes are now permitted `Sep 10 08:56:23 xxx systemd[1]: snap.rocketchat-server.rocketchat-server.service: Failed with result 'exit-code'. Sep 10 08:56:23 xxx systemd[1]: Failed to start Service for snap application rocketchat-server.rocketchat-server. |
Hi, I am facing this same issue in Ubuntu 18.04 (installed just fine in another server with 20.04). I don't know if related, but in my Ubuntu 18.04 server I already have a snap of Wekan which uses mongodb as well. |
I have clean install of Ubuntu 18.04.1 and only
core
snap package installed.After install of snap rocket-server, everything is ok. But after I restart
snap.rocketchat-server.rocketchat-server.service
or reboot server, rocket-chat do not start.Multiple restart of service do not help.
The text was updated successfully, but these errors were encountered: