[mythtv-users] MythBE1 Backend Failed

[Barry Martin]

Hi Geoff!

As I stated in an earlier message, moved your reply from my thread
"FrontEnd will connect if feels like it" to this one as with help from
this forum got the third Frontend to consistently connect, tried to fix
a channel problem (KQIN RF 34.99 being used/selected instead of RF 34.1
[Virtual 36.1]).    Your suggestions were to go back to the Backend, and
since I managed to kill that off figured may as well move it over to
this thread.



> >> Does systemctl status mythbackend.service report that the backend
> is
> >> running?
> > Hmm: no, and before I go on some times this Frontend works/connects
> and
> > some times it doesn't.  The other Frontends don't seem to have a
> problem.
> > The response to the command was:
> >      Loaded : not-found (Reason: No such file or directory)
> >      Active: inactive (dead)
> OK, all the way back to basics.
> 1)      You need network services running on the master box. Looks
> like you 
> have that: I am presuming you are posting from that box, otherwise all
> bets are off!

Naaa!  I'm emailing from a system running Ubuntu 14.04!  I can face
forward and type instead of emailing with my knees jammed against the
desk drawers! <g>  Pseudo nerd-ville: real system to the front, monitor
for the Backend to my right, monitor for the 3rd Frontend that was ready
to go to that right.  Looooong HDMI cables and wireless keyboard!

Back to little more serious answer, the failed Backend (MythBE1) does
connect to other computers (just pinged the printer server), as well as
the outside world (Firefox connects to my usual home page).




> 2)      You need mysql running on a computer with the mythconverg
> database. 
> It may be mysqld, mysqld.service or mariadb.service depending on 
> Ubuntu/Fedora/obselete-any-of-the-above.


The Backend and Frontends are running 16.04.

The Backend is running/has installed mysql.service.  It doesn't find
anything with mysqld.servcie.  (Used the command "locate -w
'mysqld.service'".)

(BTW, I may give too much information some times to be sure I'm doing
things correctly.)




> Check on the "master" computer.
> You must be able to do a 'mysql -umythtv -pmythtv mythconverg' on that
> machine. (The "usual" setup parameters).


Bzzt! <g>  Also tried with 'sudo' just in case.  Both gave:
ERROR 2002 (HY200): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)

Know from previous weeks' fiddlings before I started posting that's a
problem with MySQL not being installed correctly, possibly something
with the repositories.  Found an uninstall/re-install sequence which
corrected.  At this point I haven't done that as it seems like it's not
the end-fix.




> And 'systemctl status mysqld.service' (or systemctl status 
> mariadb.service) should return something like:


systemctl status mysqld.service ==> 
barry at MythBE1:~$ systemctl status mysqld.service
● mysqld.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

[Bet we anticipated that from the previous test!]

Now FWIW based on the previous test I tried "systemctl status
mysql.service" (no 'd') and got this:

barry at MythBE1:~$ systemctl status mysql.service
● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor
preset: en
   Active: activating (start-post) (Result: exit-code) since Wed
2016-07-13 15:3
  Process: 12285 ExecStart=/usr/sbin/mysqld (code=exited,
status=1/FAILURE)
  Process: 12281 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
(code=exi
 Main PID: 12285 (code=exited, status=1/FAILURE);         : 12286
(mysql-systemd
   CGroup: /system.slice/mysql.service
           └─control
             ├─12286 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─12354 sleep 1

Jul 13 15:32:59 MythBE1 systemd[1]: Starting MySQL Community Server...
Jul 13 15:33:01 MythBE1 systemd[1]: mysql.service: Main process exited,
code=exi
lines 1-13/13 (END)




> If necessary try each of the ExecStartPre and ExecStart lines in 
> /lib/systemd/system/mariadb.service file and fix the errors 
> individually. You will often see permissions errors or missing folders
> on a just-installed box.
> This is a bit 'belt and suspenders' but I have the following in my 
> /etc/rc.d/rc.local file,
> The /etc/rc.d/rc.local file is 'chmod 777' and I have run 'systemctl 
> enable rc-local.service' to make systemd run the file.

<Snip>

OK, looks like the rest is something I need to test so will send this
off.  

Thanks for the tips!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160713/5342c8a8/attachment.html>