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!
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
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.