Recently, I deployed a django project using this tutorial.
When I use sudo journalctl -u gunicorn to check gunicorn logs I always get “No entries”. This happens even when the application has errors.
usr@ubuntu:~/api$
usr@ubuntu:~/api$ sudo journalctl -u gunicorn
[sudo] password for user:
-- 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!
I tried the same the other day and got no idea why it wouldn’t work, but what I did manage to find was the logs are in /var/logs/ and then you have access to read all of them and I recall seeing one in there for gunicorn.
Sorry wish I could be a little more accurate but don’t have my terminal open at moment, but i hope this helps.
This is still an issue on all of my droplets, starting recently. There is a fix, which is to restart systemd-journald.
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.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.