May 07 16:50:53 hostname systemd: : Start request repeated too quickly. May 07 16:50:53 hostname systemd: Stopped Service for snap application rocketchat-server.rocketchat-mongo. May 07 16:50:53 hostname systemd: : Scheduled restart job, restart counter is at 5. May 07 16:50:53 hostname systemd: : Service hold-off time over, scheduling restart. Main PID: 16485 (code=exited, status=1/FAILURE) Process: 16485 ExecStart=/usr/bin/snap run rocketchat-server.rocketchat-mongo (code=exited, status=1/FAILURE) Loaded: loaded (/etc/systemd/system/ enabled vendor preset: enabled)Īctive: failed (Result: exit-code) since Thu 16:50:53 EDT 1s ago Produces: - Service for snap application rocketchat-server.rocketchat-mongo
Rocket chat snap update update#
Update 1: (forgot to attach mongod status) I then restarted everything but received the same error message. In response, I attempted changing permissions of the common directory (only temporarily) with: sudo chmod -R 777 /mnt/mountpoint/rocketchat-server-data/common May 07 15:28:17 hostname rocketchat-server.rocketchat-server: Mongo is not available, can't start. May 07 15:28:17 hostname systemd: Started Service for snap application rocketchat-server.rocketchat-server. May 07 15:28:17 hostname systemd: Stopped Service for snap application rocketchat-server.rocketchat-server. May 07 15:28:17 hostname systemd: : Scheduled restart job, restart counter is at 7.
May 07 15:28:17 hostname systemd: : Service hold-off time over, scheduling restart. May 07 15:28:16 hostname systemd: : Failed with result 'exit-code'. May 07 15:28:16 hostname systemd: : Main process exited, code=exited, status=1/FAILURE Please make sure Mongo has started successfully: sudo systemctl status -mongo to view logs: sudo journalctl -u -mongo However, upon starting everything, RocketChat is unable to connect to mongodb: May 07 15:28:16 hostname rocketchat-server.rocketchat-server: Was unable to connect to Mongo. Start mongodb and Rocket.Chat sudo service -mongo start Replace Snap common directory with sym link to it's new location on the external drive sudo ln -s /mnt/mountpoint/rocketchat-server-data/common /var/snap/rocketchat-server/common Move common directory from Snap directory to the external drive sudo mv /var/snap/rocketchat-server/common /mnt/mountpoint/rocketchat-server-data/common Sudo service -mongo stopĬreate directory on external drive to hold Rocket.Chat data sudo mkdir /mnt/mountpoint/rocketchat-server-data Stop Rocket.Chat and mongodb sudo service -server stop Sudo service -server startĪllow removable media sudo snap connect rocketchat-server:removable-media So far this is what I have tried:īackup Rocket.Chat sudo service -server stop
I would like to move the data (but not the entire snap) to another hard drive. For example you can have your favorite Git cloud repository send a message to you-or to a channel-when someone makes a commit or a merge request, or a CI/CD automated build completes or bombs out.I have Rocket.Chat running on Ubuntu 18.04.4 LTS through Snap.
Most of these collaborative tools accept plug-ins and work hard to foster an ecosystem of integration partners. Typically these are called rooms or channels. RELATED: The Best Open Source Alternatives to SlackĪll these collaborative chat tools let you segregate conversations by whatever categories make sense to you, such as teams, projects, or topics. The immediacy of the communication simply cannot be replicated using email. The ability to share images, documents, and video clips enhances the standard text message format and is key to the efficient collaboration that these tools can bring. Used properly, these enterprise messaging platforms encourage and simplify collaboration within-and between-departments and teams.Įasy and fast communication between team members can only be a good thing. It’s easy to dismiss tools like Slack, Microsoft Teams, and Rocket.Chat as nothing more than instant messenger clients.
0 kommentar(er)
