Mastodon broken after applying suggested package upgrades

Hey there, I was able to sucessfully deploy Mastodon with the 1 click app in a few minutes. However after I logged in via SSH and applied the suggested package upgrades, the site broke. I see this in the logs:

Unable to load application: LoadError: cannot open shared object file: No such file or directory - /home/mastodon/live/vendor/bundle/ruby/3.0.0/gems/idn-ruby-0.1.4/lib/

bundler: failed to load command: puma (/home/mastodon/live/vendor/bundle/ruby/3.0.0/bin/puma)

/home/mastodon/live/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require’: cannot open shared object file: No such file or directory - /home/mastodon/live/vendor/b>

It seems that the upgrade removed the library and I have not been able to reload it. I get messages saying that the package is already up to date, but it is not in that directory.

Any help is appreciated

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Site Moderator
Site Moderator badge
February 1, 2023
Accepted Answer

Hello @mrroyce

You can check if the file is present here - /usr/lib64/

And then create a symlink

ln -sf /usr/lib64/ /usr/lib64/

You can also try to create another symlink or manually create the missing directory which is mentioned in the error - No such file or directory

Hope that this helps!