It looks like the problem is the MySQL isn't up.
** Attachment added: mythbackend.log
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/886321/+attachment/4330715/+files/mythbackend.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
mikep554,
Yea looks like it's failing to start during boot because MySQL isn't
started yet. You can set it to wait for MySQL to start by altering
/etc/init/mythtv-backend.conf (should be line 6)
from
start on (local-filesystems and net-device-up IFACE!=lo and started udev-finish)
to
start on
** Changed in: mythtv (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug
I don't have my log's anymore I ended up breaking the backend even more
trying to fix it myself.
but what was going on is it couldn't connect to the mysql server it kept
saying failed password.
I changed the password on the frontend/backend/mysql allowed mysql
accesses to to the world (although
Ryan,
Please post your /var/log/mythtv/mythbackend.log file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go
mikep554,
It sounds like either your network isn't up when the backend tries to
start (which shouldn't actually be possible with our startup script) or
more likely, MySQL isn't up when the master backend tries to start. Can
you please post your /var/log/mythtv/mythbackend.log file?
--
You
So I got a fresh install of Mythbuntu 14.04 all up to date and I too am
having issues with the backend starting at boot
[ 27.361614] init: mythtv-backend main process (2006) terminated with status
130
[ 27.361628] init: mythtv-backend main process ended, respawning
[ 27.530461] init:
I believe I am also experiencing this issue. I have observed the same
behavior described by the previous posters. I would be happy to provide
any information that might assist in troubleshooting this issue to
determine the cause.
--
You received this bug notification because you are a member of
Just for additional clarification, mythtv-backend fails to start as part
of the normal upstart job during normal startup. However, I can start
mythtv-backend using the command sudo service mythtv-backend start and
it starts successfully and I am able to use myth on my remote systems
just fine.
In
It happens at boot and mythbackend never starts.
I'm going to try a removel and reinstall and try again. I'll post here
what I find after that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
I'm wondering if you can start it after boot via a
sudo service mythtv-backend restart
On Wed, Nov 5, 2014 at 9:26 AM, GeeMac htpc2...@live.com wrote:
It happens at boot and mythbackend never starts.
I'm going to try a removel and reinstall and try again. I'll post here
what I find after
Hi
Well after purging all that is Myth and reinstalling the backend, I
still get the same as in #35.
Here is the result:
sudo service mythtv-backend restart
stop: Unknown instance:
mythtv-backend start/running, process 3637
-
sudo service mythtv-backend start
The process name isn't mythtv-backend, it's mythbackend which is why that
kill command doesn't work. That said, checking that it is running by
killing it is a bad idea. Either do a 'ps aux' and grep the output or do a
'sudo service mythtv-backend status'
On Nov 5, 2014 2:46 PM, GeeMac
sudo service mythtv-backend status
mythtv-backend stop/waiting
Well I have just come up with another issue that reared its ugly head again. I
neglected to take notes on installing the driver dvb-fe-nxt2004.fw for my TV
card during the original Trrusty install and can't for the life of me
What is host 'gee'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go to:
yep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go to:
oops... The yep was for another post.
localhost or 127.0.0.1 in this case host= 'localhost'.
The backend is connecting correctly to database via localhost.
The default MySQL connection with mythbackend is usually:
DB name: mythconvrg
user:mythtv
pass:mythtv
port 3306.
I usually change the
I'm just wondering why it's trying to start a remote host 'gee'
On Sat, Nov 1, 2014 at 11:59 AM, GeeMac htpc2...@live.com wrote:
oops... The yep was for another post.
localhost or 127.0.0.1 in this case host= 'localhost'.
The backend is connecting correctly to database via localhost.
The
^Typo^
DB: mythconverg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go to:
Thomas,
If you would like, I can set up Teamviewer here and you can dive right into the
system. There is nothing shocking on the drive...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Does this only happen at boot? or does mythbackend never start?
On Sat, Nov 1, 2014 at 12:19 PM, GeeMac htpc2...@live.com wrote:
Thomas,
If you would like, I can set up Teamviewer here and you can dive right into
the system. There is nothing shocking on the drive...
--
You received this
Hello Thomas,
Sorry for the delay. I fell ill here so I am back now.
I am a hardware person so please bear with me. How shall I pull the job
information you need? Do you want the information from intctl.list and or the
initctl show-config?
Cheers
G
--
You received this bug notification
Please post the content of
/etc/init/mythtv-backend.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go to:
Here it is. I have not touched the settings since it was installed.
The conf file is at default.
/etc/init/mythtv-backend.conf
# MythTV Backend service
description MythTV Backend
author Mario Limonciello supe...@ubuntu.com
start on (local-filesystems
Odd. Can you also post
/var/log/upstart/mythtv-backend.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go to:
Just a quick note...
I had the same dmesg as in post #26 on this system with the backend running and
front end accessing it. That was when using 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Broken record in mythtv-backend.log
Im going to run the back end and set it up with MySQL and see if it still has
the issue. If so, I'll go into the database and see what is up there.
Cannot find (ping) database host gee on the network
Would you like to
I created the database for the backend using PHPMyAdmin and loaded the tables
in via the backend. That went pretty smooth as it usually does. I rebooted
the system and still got roughly the same message. Just the process numbers
were different.
I did not think setting up the database would
Ok, is there anything in /var/log/mythtv/mythbackend.log
On Oct 31, 2014 4:55 PM, GeeMac htpc2...@live.com wrote:
I created the database for the backend using PHPMyAdmin and loaded the
tables in via the backend. That went pretty smooth as it usually does. I
rebooted the system and still got
Any fix for this yet?
Roughly three years later and still we are having the same issues with MythTV
Backend / Upstart. Myth is now at version 0.27.4 and Ubuntu is at 13.10 (Saucy
Salamander) and 14.04 (Trusty Tahr)
Apparently this is an issue that got placed on the back burner since MythTV is
^^^ P.S. ^^^
Linux-x86_64 Ubuntu14.04 Trusty Tahr
On board GeForce 7050 PV / nForce 630a (GPU 0) latest drivers 304.123
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart
Can you paste your upstart job here?
On Oct 27, 2014 3:15 PM, GeeMac htpc2...@live.com wrote:
Any fix for this yet?
Roughly three years later and still we are having the same issues with
MythTV Backend / Upstart. Myth is now at version 0.27.4 and Ubuntu is at
13.10 (Saucy Salamander) and
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mythtv (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Finally managed to solve it.
After digging deep into the backend invocation and looking an strace
dump, it became clear that a DL depdency (libGL.so) could not be
resolved as this library is residing in /usr/lib/x86_64-linux-gnu/mesa
in my 11.10 installation. Adding a suitable LD_LIBRARY_PATH
Do you have the nvidia or fglrx drivers installed? Or did you ever?
Did you by chance ever install them by hand (NOT using packaged .deb's)
?
They do muck with alternate libGL.so files in alternate paths, so I
wonder if something went crazy at some point from those drivers that
might not have
Yes but as fglrx caused a kernel OOPS (cf. bug #883873), I ditched them
in favour of the radeon drivers that came with the X server (package
xserver-xorg-video-radon).
Upon closer inspection, the loader looks in the following places for the
library on my system (according to the strace-generated
Glancing through the source this is the only explicit reference I see to
code 127:
libs/libmythdb/exitcodes.h:#define GENERIC_EXIT_CMD_NOT_FOUND
127
libs/libmythdb/exitcodes.h:#define MYTHSYSTEM__EXIT__CMD_NOT_FOUND
GENERIC_EXIT_CMD_NOT_FOUND
libs/libmythtv/jobqueue.cpp:(result ==
Further observation: doesn't seem to be a timing problem / race
condition right after system init as this behaviour persists way beyond
boot stage, ie. is reproducible all along the way.
What would be of great help to track this down is what exit code 127
from the backend exactly means. Esp. as
This gets even stranger. After instrumentation, the .conf file looks
like this (just to be on the safe side...):
# MythTV Backend service
description MythTV Backend
author Mario Limonciello supe...@ubuntu.com
start on (local-filesystems and net-device-up IFACE!=lo and started
Can you attach your /etc/init/mythtv-backend.conf file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go to:
Straight from the repo update (I didn't change this):
description MythTV Backend
author Mario Limonciello supe...@ubuntu.com
start on (local-filesystems and net-device-up IFACE!=lo and started udev-finish)
stop on runlevel [016]
#expect fork
So with your problem you'll want to investigate
/var/log/mythtv/mythbackend.log and see why it's respawning too quickly.
It should hopefully list there for you.
** Changed in: mythtv (Ubuntu)
Status: Fix Released = Incomplete
--
You received this bug notification because you are a member
Thanks for pointing this out Thomas!
Unfortunately, the backend doesn't generate ANY logging information
before exiting. Without having looked into the code in detail, I suspect
the exit takes places before the logging is started. I took a quick shot
atthe source code of 0.24 and searched for a
Mario,
He mentioned that The backend log doesn't contain anything with this
timestamp as apparently it doesn't even get to the logging stage
Could the issue be with the pre-start script on his system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well to rule out the pre-start script, you can try adding logger
commands in the prestart script and start script sections to make sure
it logs to syslog when it's about to try something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Updated the backend from the mythbuntu repos as described.
Unfortunately, the issue still persists:
Dec 19 14:17:49 htpc kernel: [ 28.254623] init: mythtv-backend main process
(1315) terminated with status 127
Dec 19 14:17:49 htpc kernel: [ 28.254651] init: mythtv-backend main process
As this is not part of the ordinary oneiric package repos yet: where can
I download this package or when will it find its way into the normal
update repos?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please activate the mythtv updates repo by installing the mythbuntu-
repos package from http://mythbuntu.org/repos then update as usual
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
This bug was fixed in the package mythtv - 2:0.24.0+fixes.20111207
.40f3bae-0ubuntu1
---
mythtv (2:0.24.0+fixes.20111207.40f3bae-0ubuntu1) precise; urgency=low
[ Mario Limonciello ]
* debian/rules:
- Don't modify mythtv/VERSION at all during build. Only use
Has this fix found its way into the general update stream?
I'm running MythTV version:
v0.24.1-80-g1de0431
MythTV Branch: fixes/0.24
Network Protocol : 63
Library API : 0.24.20110505-1
I'm not sure if this is the fixed version - please confirm.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mythtv (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
I have the same problem, though what really puzzles me is that I never
used MythTV. It has been installed on my computer for a long time and is
now all of a sudden causing this problem doing upstart, meaning that it
takes around two minutes to boot all of a sudden. Now I removed all
packages
I believe this should be resolved with the latest changes to the -fixes
and -master packaging. Hasn't been uploaded yet though to precise and
no builds yet from autobuilds (waiting for another upstream change).
revno: 451
committer: Thomas Mashos tgm4...@ubuntu.com
branch nick: mythtv-fixes
** Branch linked: lp:mythtv/mythtv-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications about this bug go to:
Reinstallation didn't make any difference.
What is puzzling indeed is that the invocation in the upstart script
does NOT generate any log file AT ALL never mind the -v setting on the
command line. Only when I invoke it later manually in a terminal window
the first log entry is created. It seems
** Attachment added: mythtv-backend.conf
https://bugs.launchpad.net/bugs/886321/+attachment/2585546/+files/mythtv-backend.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
What happens if you just run
/usr/bin/mythbackend --user mythtv -v most,important
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage notifications
It's an upstart problem - running the backend from the command line
works like a charme.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886321
Title:
Upstart issue and mythbackend
To manage
58 matches
Mail list logo
