[mythtv-users] Failed Cron Job mythtv-status

[Stephen Worthington]

On Fri, 18 Oct 2013 11:53:37 -0400, you wrote:

>This morning, I've been getting littered with failed cron messages...
>
>Hey, /var/run/motd.mythtv-status already exists
>-rw-r--r-- 1 root root 112 Oct 18 11:41 /var/run/motd
>-rw-r--r-- 1 root root 112 Oct 18 10:31 /var/run/motd.mythtv-status
>-rw-r--r-- 1 root root 112 Oct 18 11:41 /var/run/motd.orig
>root      6747  6746  0 11:50 ?        00:00:00 /bin/sh -c [ -x
>/etc/init.d/mythtv-status ] && /etc/init.d/mythtv-status reload > /dev/null
>root      6748  6747  0 11:50 ?        00:00:00 /bin/sh
>/etc/init.d/mythtv-status reload
>root      6751  6748  0 11:50 ?        00:00:00 grep mythtv-status
>cat: /var/run/motd.new: No such file or directory
>
>Mythbuntu 12.04, Mythtv 0.27, most current release from mythbuntu repos.  I
>installed mythtv-status about 2 weeks ago, and never had this message
>before.  As I said, it just started popping up this morning.
>
>Anyone have any advice as to what's going on?
>
>Thanks!

It is a bug in mythtv-status.  It happens when mythbackend is shut
down and mythtv-status tries to talk to it.  It will keep on doing
those messages periodically until you do this to fix it:

  rm /var/run/motd.mythtv-status

That will fix it until mythbackend is stopped again.  I also added
that command to /etc/rc.local:

# Temporary fix for a bug in mythtv-status.
if [ -e /var/run/motd.mythtv-status ] ; then
        rm /var/run/motd.mythtv-status
fi

Mythtv-status can try to talk to mythbackend after it has been shut
down, but before mythtv-status is shut down, or before mythbackend has
started fully on startup, resulting in this problem happening on a
reboot.

Whenever mythbackend gets updated, there is a fair chance of this
happening, if there is long enough between it getting shut down for
the update and it being restarted again.