[mythtv-users] mythtv-backend service stops

[Mike Perkins]

On 17/11/14 19:47, Bill Meek wrote:
> On 11/17/2014 01:14 PM, Roger Searle wrote:
> ...
>  > At this point I can get the FE to connect to the BE however the only way I
> can start the BE is as the root user, it is not starting
>> automatically.  If I start is as --user mythtv it will fail to run. Command
>> line output for both is below - I note a couple of things about this
>> when starting as "--user mythtv", the obvious thing being it complains about
>> the BackendServerIP (it is set as mentioned above), "no address
>> defined for host", where is this looking or where should this be set?  And the
>> testing network connectivity to 192.168.1.100 is actually my own
>> BE myth box, why is it testing against that?
>>
>> # starting backend as mythtv user:
>>
>> emmatodd at htpc:~$ sudo /usr/bin/mythbackend --syslog loval7 --user mythtv
>> [sudo] password for emmatodd:
> ...
>> 2014-11-18 07:59:09.365849 N  Using configuration directory =
>> /home/mythtv/.mythtv <<<<<<<<<<<<<<<<<<
> ...
>> No setting found for this machine's BackendServerIP.
>> Please run setup on this machine and modify the first page
>> of the general settings.
> ...
>>
>>
>>
>> # starting backend as root:
>>
>> emmatodd at htpc:~$ sudo /usr/bin/mythbackend
> ...
>> 2014-11-18 08:05:40.809876 N  Using configuration directory =
>> /home/emmatodd/.mythtv <<<<<<<<<<<<<<<<
> ...
>
> Note the "Using configuration directory" lines for both cases.
>
> In this case, when using sudo, the HOME directory is that of the
> user you're logged in as (emmatodd.)
>
> The config.xml files in both places should be the same. Try:
> this:
>
>       diff ~mythtv/.mythtv/config.xml ~emmatodd/.mythtv/config.xml
>
> The 1st would be used by the BE when started with --user mythtv and
> the 2nd when user emmatodd starts the frontend.
>
> You could put the 2 config.xml files at pastebin.com (or wherever
> you like to paste things), an put a link to it here, if the above
> doesn't help.
>
Actually I would add that in neither of the OP's examples should sudo have been 
used. The exec is stored in /usr/bin, therefore it doesn't need sudo to be 
runnable by any user.

Doing that will almost certainly give you different results.

-- 

Mike Perkins