mythbuntu-bugs team mailing list archive

[simguru <799663@xxxxxxxxxxxxxxxxxx>]

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

The jamu.py script referenced in this cron job has been moved to
/usr/share/mythtv/mythvideo/scripts/jamu.py. I included a small patch
that points the cron job to the new path. I keep updated regularly and
this error cropped up. I think somebody moved the jamu.py script without
updating this cron job.

** Patch added: "mythtv-backend jamu.py reloaction"
   https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/799663/+attachment/2180425/+files/cron.patch

-- 
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:
  New

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