[mythtv-users] Upgrade 0.24->0.25 goes poorly.
Ross Boylan
RossBoylan at stanfordalumni.org
Sun May 13 16:57:19 UTC 2012
On Sun, 2012-05-13 at 11:13 -0500, Bill Meek wrote:
> On 05/12/2012 09:22 PM, Ross Boylan wrote:
> ...
> > /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
> > and I don't see much in any logs.
> ...
>
> Hi;
>
> Check your /etc/init.d/mythtv-backend file. It will tell you where your
> logs are going. It won't be the file you looked at above. Expect:
> --syslog sonething or --logpath somethingElse.
It is the file I looked at. Here are the key parts of the init.d file
DAEMON=/usr/bin/mythbackend
ARGS="--daemon --logpath /var/log/mythtv/mythbackend.log --pidfile $RUNDIR/$NAME.pid"
start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \
--chuid $USER --nicelevel $NICE --exec $DAEMON -- $ARGS
One reason I was trying to run mythbackend manually was so I could see
error messages.
>
> > 5. Even before the upgrade I got
> > Error parsing: /var/lib/mythtv/.mythtv/config.xml at line: 1 column: 1
> > on startup. That file is empty, though there is a config.xml~ file with
> > stuff in it.
>
> Copy a good config.xml file to the user's .mythtv directory whose running
> the backend. That may be root, or if you're using the --user switch, that
> user, most likely mythtv.
>
Is 0.25 more sensitive to this and 0.24?
Ross
> ...
> > Thanks for any help.
>
> Lots of stuff going on here, but that's where a start.
>
More information about the mythtv-users
mailing list