[mythtv-users] Mythbackend runs from command line, but not from init script (DVB issue?)
Phil Bridges
gravityhammer at gmail.com
Sun Aug 3 01:19:31 UTC 2008
On Sat, Aug 2, 2008 at 8:42 PM, Phil Bridges <gravityhammer at gmail.com> wrote:
> For some reason, the majority of my problems happen when the power
> goes out. This time, the power outage lasted longer than my UPS'
> batteries, and it didn't shut down.
>
> Anyway, I have a slave backend that refuses to start the backend
> process from the init script (on Gentoo):
>
> ebegin "Starting MythTV Backend"
> start-stop-daemon --start --quiet --chuid mythtv \
> --exec /usr/bin/mythbackend \
> --make-pidfile --pidfile /var/run/mythbackend.pid \
> --background -- --verbose ${MYTH_VERBOSE} \
> --logfile /var/log/mythtv/mythbackend.log
> eend $?
>
> The pertinent part of the backend log shows:
>
> 2008-08-02 20:40:32.222 TVRec(2): Start channel: 806.
> 2008-08-02 20:40:32.223 DVBChan(2:1): Opening DVB channel
> 2008-08-02 20:40:32.224 DVBChan(2:1) Error: Opening DVB frontend device failed.
> eno: No such file or directory (2)
> 2008-08-02 20:40:32.224 DVBChan(2:1): Closing DVB channel
> 2008-08-02 20:40:32.230 TVRec(2): ClearFlags(RecorderRunning,) -> 0x0
> 2008-08-02 20:40:32.231 MythEvent: RECORDING_LIST_CHANGE
>
> The weird thing, though, is that /usr/bin/mythbackend starts up fine
> (from eithe root account or mythtv account). The DVB device has been
> given 777 privileges, show it's not an access issue. Is there
> anything in particular I should look for here?
>
Ah - catastrophe averted. For some reason, I had a third mysql.txt
located in /etc/mythtv/.mythtv/ that was not set up with the master
backend address. Sheesh!
Now, I just have to figure out why the init script didn't look at
/home/mythtv/.mythtv/mysql.txt ...
More information about the mythtv-users
mailing list