Mastodon is not launching after upgrading to Yunohost 12. mastodon-web and mastodon-sidekiq cannot load. Mastodon-streaming is running fine, at least if the Yunohost Web Portal Administration page can be trusted. I have attempted to "restart" the services via the the Web Portland, Yunohost command, and Debian command line. Mastodon was working just fine before the upgrade. I really don't want to have to uninstall and reinstall Mastodon, as I'm worried about losing all the data that is already stored on this server.
Context
Hardware: VPS
YunoHost version: 12.0.6
I have access to my server: Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
If yes, please explain: Mastodon is setup to use object storage on MinIO server separate from Yunohost for Mastodon media
Using, or trying to install package version/branch: 4.2.12~ynh1
Steps to reproduce
Upgrade Yunohost from Version 11 to Version 12, Mastodon will stop working.
Expected behavior
After upgrade Mastodon will continue to work or at least spit out usable logs that could be helpful.
Logs
See this issue for more information: The logs listed here are exactly the same as my own. And the tootctl error log mentioned is also the same as mine.
Describe the bug
Mastodon is not launching after upgrading to Yunohost 12. mastodon-web and mastodon-sidekiq cannot load. Mastodon-streaming is running fine, at least if the Yunohost Web Portal Administration page can be trusted. I have attempted to "restart" the services via the the Web Portland, Yunohost command, and Debian command line. Mastodon was working just fine before the upgrade. I really don't want to have to uninstall and reinstall Mastodon, as I'm worried about losing all the data that is already stored on this server.
Context
Steps to reproduce
Upgrade Yunohost from Version 11 to Version 12, Mastodon will stop working.
Expected behavior
After upgrade Mastodon will continue to work or at least spit out usable logs that could be helpful.
Logs
See this issue for more information: The logs listed here are exactly the same as my own. And the tootctl error log mentioned is also the same as mine.