[mythtv-users] MythBE1 Backend Failed

[Barry Martin]

Hi Mike!

First, thank you (and others) for the response - busy weekend and other
excuses for not replying promptly.

> I might be heading in a different direction to the others. But I would
> be interested in seeing the output of (as root user):
> systemctl status mysql

barry at MythBE1:~$ systemctl status mysql
● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor
preset: en
   Active: activating (start-post) (Result: exit-code) since Mon
2016-07-11 19:2
  Process: 3981 ExecStart=/usr/sbin/mysqld (code=exited,
status=1/FAILURE)
  Process: 3977 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
(code=exit
 Main PID: 3981 (code=exited, status=1/FAILURE);         : 3982
(mysql-systemd-s
    Tasks: 2 (limit: 512)
   CGroup: /system.slice/mysql.service
           └─control
             ├─3982 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─4075 sleep 1

Jul 11 19:22:00 MythBE1 systemd[1]: Starting MySQL Community Server...
Jul 11 19:22:02 MythBE1 systemd[1]: mysql.service: Main process exited,
code=exi
lines 1-14/14 (END)




> to see if mysql is crashed for some reason. Also (as root user):
> netstat -peanut | grep 3306
barry at MythBE1:~$ 
barry at MythBE1:~$ sudo netstat -peanut | grep 3306
[sudo] password for barry: 
barry at MythBE1:~$ sudo netstat -peanut | grep 3306
barry at MythBE1:~$ 

If no one's listening no one can hear! (But we need to find out why!)



> To see what is listening on the mysql port. I would also be interested
> in seeing what hosts your mysql users have rights for, run the
> following command from a terminal on your backend:
> 
> mysql -uroot -p mythconverg -e "select host,user from mysql.user;"
> (and type your root mysql user password in when prompted)
barry at MythBE1:~$ mysql -uroot -p mythconverg -e "select host,user from
mysql.user;"
Enter password: 
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
barry at MythBE1:~$ 

I've Googled and found where this "error 2002" has something to do with
all of the repositories for MySQL are not loaded properly/correctly with
version 16.04 (and I think 14.04).  There are instructions to remove and
re-install which I have not done yet.  Had to do previously to when
originally got the system up.



> I have previously had issues where I had granted my mythtv user mysql
> rights on the localhost host but the user was trying to connect on
> 127.0.0.1 which in my mind are essentially equivalent however not
> equivalent enough for mysql (or it was vice versa I don?t quite
> recall).
During my original panicky freak-out had tried localhost (127.0.0.1)
with no luck.  Then tried the IP address (static - though I think
assigned by the router and not by the machine if that makes a
difference.  (And would have to look that up.)


> Otherwise have you checked things like disk usage for an excessively
> full disk? Run the following command:
> df -h
barry at MythBE1:~$ df -h
Filesystem               Size  Used Avail Use% Mounted on
udev                     3.9G     0  3.9G   0% /dev
tmpfs                    799M  9.7M  789M   2% /run
/dev/sda1                222G  5.0G  205G   3% /
tmpfs                    3.9G     0  3.9G   0% /dev/shm
tmpfs                    5.0M  8.0K  5.0M   1% /run/lock
tmpfs                    3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sdb1                2.8T  180G  2.6T   7% /var
//192.168.0.120/Backups  4.5T  3.2T  1.4T  71% /mnt/NSA320
tmpfs                    799M  8.0K  799M   1% /run/user/1000
barry at MythBE1:~$ 

Well that's interesting: it can see my backup server (192.168.0.120) and
I didn't tell it!!  ...OK, /dev/sda1 is the HDD with the OS on
it; /dev/sdb1 is the 3TB drive for storage.

And again, thanks!

Barry