Question

Mastodon 1-Click droplet unable to find error logs

I’m following the Mastodon 1-click quickstart guide here: https://marketplace.digitalocean.com/apps/mastodon

The app is running and I can access it via the web browser, but I’m seeing some 500 errors. When I attempt to view the Mastodon logs to debug the 500 errors, I see no journal files. Am I missing something? How should I be accessing the logs for Mastodon?

# sudo journalctl -u mastodon-web
No journal files were found.
-- No entries --
Show comments

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.

Abhimanyu Selvan
DigitalOcean Employee
DigitalOcean Employee badge
December 21, 2022
Accepted Answer

Hey Andy,

It looks like journalctl cannot locate the journal files (usually in /var/log/journal. Can you restart the service using

systemctl restart systemd-journald.service

In case you want the logs to be persistent, you can edit the /etc/systemd/journald.conf file and change the Storage to persistent

[Journal]
Storage=persistent

Save and restart the service.

alexdo
Site Moderator
Site Moderator badge
December 21, 2022

Hello @andykaier

Since Mastodon is not managing its own log system it relies on each process to save its exit code or error accordingly.

You can check the /var/log/syslog as well as the journal log.

Regards