[mythtv-users] Upgrade 0.24->0.25 goes poorly.

[Bill Meek]

On 05/13/2012 11:57 AM, Ross Boylan wrote:
> 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.
...
>> 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

--logpath must point to a directory, not a file. I understand from your original
post that --help didn't help, so: http://www.mythtv.org/wiki/Logging#File_Logging.
In other words:  --logpath /var/log/mythtv.

>> 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?

I remember seeing posts on this list saying that config.xml had been zeroed.
And I've had it happen to me too.

-- 
Bill