Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40512 - [tt-rss] systemd service improvement

Attached to Project: Community Packages
Opened by Stefan Tatschner (rumpelsepp) - Friday, 23 May 2014, 19:44 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Friday, 07 November 2014, 12:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The current systemd service file fills the journal with a lot of garbage:

Mai 23 21:34:19 archvm php[1713]: [19:34:19/9246] => 2014-05-23 19:04:00.023782, 5 2
Mai 23 21:34:19 archvm php[1713]: [19:34:19/9246] Base feed: http://rss.golem.de/rss.php?feed=RSS2.0
Mai 23 21:34:16 archvm php[1713]: [19:34:16/9246] => 2014-05-23 19:03:57.097203, 20 2
Mai 23 21:34:16 archvm php[1713]: [19:34:16/9246] Base feed: https://www.schneier.com/blog/atom.xml
Mai 23 21:34:14 archvm php[1713]: [19:34:14/9246] => 2014-05-23 19:03:53.869982, 6 2
Mai 23 21:34:14 archvm php[1713]: [19:34:14/9246] Base feed: http://derstandard.at/?page=rss&ressort=web
Mai 23 21:34:14 archvm php[1713]: [19:34:14/9246] => 2014-05-23 19:03:49.296718, 11 2
Mai 23 21:34:14 archvm php[1713]: [19:34:14/9246] Base feed: http://news.google.de/news?pz=1&cf=all&ned=de&hl=de&topic=s&output=rss
Mai 23 21:34:13 archvm php[1713]: [19:34:13/9246] => 2014-05-23 19:03:48.079975, 10 2
Mai 23 21:34:13 archvm php[1713]: [19:34:13/9246] Base feed: http://news.google.de/news?pz=1&cf=all&ned=de&hl=de&output=rss
Mai 23 21:34:12 archvm php[1713]: [19:34:12/9246] => 2014-05-23 19:03:47.213212, 3 2
Mai 23 21:34:12 archvm php[1713]: [19:34:12/9246] Base feed: http://tt-rss.org/releases.rss
Mai 23 21:34:12 archvm php[1713]: [19:34:12/9246] Scheduled 7 feeds to update...
Mai 23 21:34:12 archvm php[1713]: [19:34:12/9246] Lock: update.lock
...
Mai 23 21:32:12 archvm php[1713]: [19:32:12/1713] Sleeping for 120 seconds...
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] Cleaned 2 cached tags.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] Purged 0 orphaned posts.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] Feedbrowser updated, 2 feeds processed.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] Removing old error log entries...
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] Removed 0 old lock files.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] cache/upload: removed 0 files.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] cache/export: removed 0 files.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] cache/images: removed 0 files.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] cache/simplepie: removed 0 files.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] All done.
Mai 23 21:32:12 archvm php[1713]: [19:32:12/9130] Sending digests, batch of max 15 users, headline limit = 1000
Mai 23 21:32:11 archvm php[1713]: [19:32:11/9130] => 2014-05-23 19:01:46.569363, 7 2
Mai 23 21:32:11 archvm php[1713]: [19:32:11/9130] Base feed: http://www.heise.de/developer/rss/news-atom.xml
Mai 23 21:32:03 archvm php[1713]: [19:32:03/9130] => 2014-05-23 19:01:45.563239, 9 2
Mai 23 21:32:03 archvm php[1713]: [19:32:03/9130] Base feed: http://www.heise.de/newsticker/heise-atom.xml
Mai 23 21:32:03 archvm php[1713]: [19:32:03/9130] Scheduled 2 feeds to update...
Mai 23 21:32:03 archvm php[1713]: [19:32:03/9130] Lock: update.lock


Maybe we can add this to suppress these messages?

StandardOutput=null
StandardError=syslog

Reference: http://tt-rss.org/forum/viewtopic.php?f=1&t=1106#p6570
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Friday, 07 November 2014, 12:08 GMT
Reason for closing:  Implemented
Comment by Steve (kwirkie) - Sunday, 19 October 2014, 13:50 GMT
Having recently upgraded to 1.13-1 from 1-12-1, there is nothing logged for this service, making it difficult to monitor activity and spot issues. Not sure if default setting of disabling the logging is the correct approach. I note the bug reporter has the update period set to 2 minutes, which is why this probably seems spammy in there journal; rather than reasonable update period of 20-30 minutes.
Comment by Stefan Tatschner (rumpelsepp) - Sunday, 19 October 2014, 15:18 GMT
I use the defaults. In the webinterface there is configured an update time of 30 minutes.
Comment by Bartłomiej Piotrowski (Barthalion) - Friday, 07 November 2014, 12:08 GMT
Regardless what I set for update time, journal is still getting flooded by messages posted in the report.

Loading...