Hi,
I’m curious to see why some sidekiq jobs are failling, but I can’t find sidekiq.log in /log. How can I enable this?
The user bartv asks how to enable Sidekiq logging, noting that the sidekiq.log file is missing from the /log directory on a DigitalOcean one-click install. zogstrip clarifies that Sidekiq logs should be accessible via the /logs endpoint in the web interface, not as a file in the filesystem. bartv confirms they were looking in the wrong location, and zogstrip provides the correct method, which bartv acknowledges with gratitude.
Hi,
I’m curious to see why some sidekiq jobs are failling, but I can’t find sidekiq.log in /log. How can I enable this?
All errors should be in /logs. Even sidekiq ones.
Yeah that’s what I understood so far, but they’re neither in log/rails nor in logs/var-log (see below). I’m on a DigitalOcean ‘one-click’ install - perhaps they didn’t enable the sidekiq logging? Is there something in app.yml or another template that I can check?
root@discourse-s-6vcpu-16gb-ams3-01-app:/var/www/discourse/log# ls -l
total 0
lrwxrwxrwx 1 discourse root 39 Apr 22 07:02 production_errors.log -> /shared/log/rails/production_errors.log
lrwxrwxrwx 1 discourse root 32 Apr 22 07:02 production.log -> /shared/log/rails/production.log
lrwxrwxrwx 1 discourse root 36 Apr 22 07:02 unicorn.stderr.log -> /shared/log/rails/unicorn.stderr.log
lrwxrwxrwx 1 discourse root 36 Apr 22 07:02 unicorn.stdout.log -> /shared/log/rails/unicorn.stdout.log
root@discourse-s-6vcpu-16gb-ams3-01-app:/var/www/discourse/log#
I didn’t mean the logs directory at the root of your filesystem but the URI (eg. https://your.discourse/logs) ![]()
Ahhhhhhhhhh! Thanks!