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