mythbuntu-bugs team mailing list archive

["Brian J. Murrell" <brian@xxxxxxxxxxxxxxx>]

On 11-06-24 11:47 AM, Thomas Mashos wrote:
> As I mentioned before, you need to update the pvr machine as those cron
> jobs don't/shouldn't exist anymore.

Updated this morning:

mythtv-frontend:
  Installed: 2:0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3
  Candidate: 2:0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3
...
mythtv-backend:
  Installed: 2:0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3
  Candidate: 2:0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3

and yet the cron jobs still exist:

$ dpkg -S /etc/cron.hourly/*
mythtv-backend: /etc/cron.hourly/mythtv-backend
mythtv-frontend: /etc/cron.hourly/mythtv-frontend
mythvideo: /etc/cron.hourly/mythvideo

> They aren't in the packaging

Sure they are:

$ dpkg -L mythtv-frontend | grep cron
/etc/cron.hourly/mythtv-frontend
/etc/cron.weekly/mythtv-frontend
/etc/cron.daily/mythtv-frontend
$ dpkg -L mythtv-backend | grep cron
/etc/cron.hourly/mythtv-backend
/etc/cron.weekly/mythtv-backend
/etc/cron.daily/mythtv-backend

And they are still returning errors as of ten minutes ago:

run-parts: /etc/cron.hourly/mythtv-backend exited with return code 2
run-parts: /etc/cron.hourly/mythtv-frontend exited with return code 1

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

Title:
  run-parts: /etc/cron.hourly/mythvideo exited with return code 1

Status in “mythtv” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: mythtv

  Once again, mythvideo's hourly cron job in the 0.24-fixes stream is
  exiting with an error:

  run-parts: /etc/cron.hourly/mythvideo exited with return code 1

  The tail end of my /var/log/mythtv/jamu.log reads:

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  The host "pvr" is in fact a MythTV backend so something is obviously
  wrong.

  On a slave backend machine (slave not actually running at this point)
  I am seeing:

  run-parts: /etc/cron.hourly/mythtv-backend exited with return code 2
  run-parts: /etc/cron.hourly/mythtv-frontend exited with return code 1

  When the mythtv-backend hourly cron job runs and exits with an error,
  the /var/log/mythtv/jamu.log on this host reports:

  /usr/bin/python: can't open file '/usr/share/doc/mythtv-
  backend/contrib/metadata/jamu.py': [Errno 2] No such file or directory

  When the mythtv-frontend hourly cron job runs and exits with an error,
  the /var/log/mythtv/jamu.log on this host reports:

  ! Error: Jamu must be run on a MythTV backend. Local host (pc) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Failed to connect to backend at 10.75.22.1:6543

  Which is correct.  So why is this job expecting the machine to be a
  backend when it's being run from the mythtv-frontend hourly cron job.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/799663/+subscriptions