By Andy Kaier
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 --
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!
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.
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.
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
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
