Tiny Tiny RSS: Community

Where is a log file for tt-rss daemon?

where is a log file for tt-rss daemon?

systemctl status tt-rss returns:

● tt-rss.service - Update the Tiny Tiny RSS subscribed syndication feeds
Loaded: loaded (/lib/systemd/system/tt-rss.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-06-27 07:34:30 MSK; 18min ago
Main PID: 3210 (php)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/tt-rss.service
└─3210 php /usr/share/tt-rss/www/update.php --daemon

Jun 27 07:34:30 ****** systemd[1]: Started Update the Tiny Tiny RSS subscribed syndication feeds.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

File /var/log/tt-rss.log does not exists.
Files /var/lib/tt-rss/update_daemon.lock and /var/lib/tt-rss/update_daemon.stamp are correct.

The update.php --force-updates showed access errors to /var/cache/tt-rss/* and recomendations. I’ve fixed it and restarted tt-rss daemon.

I have:

  • Tiny Tiny RSS v19.2 (088fcf8)
  • Ubuntu 18.04.2 LTS
  • Apache/2.4.29
  • PHP version: 7.2.19
  • mySQL 5.7.26

unless set otherwise (see --help) daemon logs to stdout.

The text logs on a Red Hat based system will be in /var/log/messages. On a Debian based system, they’ll be in /var/log/syslog. These are where systemd puts the logs (via journald) by default, when the service unit doesn’t tell it to use some other location.

If you want to see only the tt-rss messages, then do the following:

$ journalctl -f -u tt-rss.service

That’s the equivalent of running tail -f on the relevant log file and gripping for the service identifier (i.e.; what your service says its name is in the log).

If none of this is working for you, then you may meet with success doing this:

$ sudo grep -R tt-rss /var/log/*