mythbuntu-bugs team mailing list archive

[Greg <1402782@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I receive the following error during logrotate via cron.daily:

/etc/cron.daily/logrotate:
error: stat of /var/log/mythtv/mythtranscode.log failed: No such file or directory

I suggest that the config file /etc/logrotate.d/mythtv-transcode-utils should include the option 'missingok' to resolve this error.
Note that the missingok option is included in similar configs such as /etc/logrotate.d/mythtv-backend
(MythTV/packaging/blob/master/deb/debian/mythtv-transcode-utils.logrotate)

This bug is noted in the comment of
https://bugs.launchpad.net/mythbuntu/+bug/982162, but it seems that bug
was closed after resolving only the mythtv-backend config file.

I am using version 0.27.0+fixes.20

** Affects: mythbuntu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1402782

Title:
  keyword missingok is missing in mythtv-transcode-utils logrotate
  config

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  New

Bug description:
  I receive the following error during logrotate via cron.daily:

  /etc/cron.daily/logrotate:
  error: stat of /var/log/mythtv/mythtranscode.log failed: No such file or directory

  I suggest that the config file /etc/logrotate.d/mythtv-transcode-utils should include the option 'missingok' to resolve this error.
  Note that the missingok option is included in similar configs such as /etc/logrotate.d/mythtv-backend
  (MythTV/packaging/blob/master/deb/debian/mythtv-transcode-utils.logrotate)

  This bug is noted in the comment of
  https://bugs.launchpad.net/mythbuntu/+bug/982162, but it seems that
  bug was closed after resolving only the mythtv-backend config file.

  I am using version 0.27.0+fixes.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1402782/+subscriptions