The problem was that for some reason backend IP address was changed to
something else than localhost, but the problem was solved once I changed
it to 127.0.0.1 again in backend setup. I just don't have an idea what
could have changed it back to local netwoek addresss and why, cause I
did not.
--
The service name is 'mythtv-backend' not mythbackend
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1038508
Title:
mythbackend won't start if no network is available
Status in Mythbuntu, U
I don't know. I am using 14.04, but I have enabled MythTV updates
repository for version 0.27, and Mythbuntu updates repository and
installed updates.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net
So it doesn't work in 14.10?
On Thu, Dec 4, 2014 at 6:54 AM, Jarno Suni wrote:
> I did the trick told in #1. It worked first in 14.04, but not anymore
> even if /etc/init/mythtv-backend.conf is still same. As for #7, "service
> mythbackend start" don't work either: "mythbackend: unrecognized
> se
I did the trick told in #1. It worked first in 14.04, but not anymore
even if /etc/init/mythtv-backend.conf is still same. As for #7, "service
mythbackend start" don't work either: "mythbackend: unrecognized
service" What is wrong?
--
You received this bug notification because you are a member of
** Changed in: mythbuntu
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1038508
Title:
mythbackend won't start if no network is available
Status in Mythbu
I wouldn't fiddle with MySQL as any upgrade would probably overwrite
settings. I setup the following workaround in /etc/rc.local instead:
*
if ! pgrep mythbackend &> /dev/null; then
service mythbackend start
fi
exit 0
***
Thanks again for your help and advice
Antonio
It's also worth noting that if the backend is brought up with no
network, the backend will be externally inaccessible until it is
restarted
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/10385
In that upstart file, there is no reason the backend shouldn't be
starting without network connectivity (as you can see from the start on
line, we're only depending on local-filesystems and udev-finish).
What do you have set in mythtv-setup for the IP address? Is it possible
that MySQL isn't start
This happens to me by loosely supposing typos ;-) Alas there is no such
line yet:
*
# MythTV Backend service
description "MythTV Backend"
author "Mario Limonciello "
start on (local-filesystems and started udev-finish)
stop on runlevel [016]
That is not /etc/init/mythtv-backend.conf
Please look at /etc/init/mythtv-backend.conf (which is the upstart
script) and not /etc/init.d/mythtv-backend (which is the convenience
script for things that still try to do things the old way)
--
You received this bug notification because you are a mem
No such line in my /etc/init.d/mythtv-backend (please see attachment).
** Attachment added: "mythtv-backend script"
https://bugs.launchpad.net/mythbuntu/+bug/1038508/+attachment/3267242/+files/mythtv-backend
--
You received this bug notification because you are a member of Mythbuntu
Bug Team
This is by design, as most Mythbuntu machines will have/need a network
connection in order to fully function. In the odd case (such as yours)
when you want to start the backend without a network connection you can
edit the backend service (at /etc/init/mythtv-backend.conf) and remove
'net-device-up
13 matches
Mail list logo
