[mythtv-users] Sudden seemingly-random database issues

[Brian S]

Thanks both for the quick responses. I'm not well-versed at all in mysql, but here's what I have.

>  - Can you login to the database using the command-line mysql client? 
>  - Is the mysqld processr running? 
>  sudo service mysql status 

brain at myth-master:~$ sudo service mysql status
mysql stop/waiting


>  sudo /etc/init.d/mysql status

brain at myth-master:~$ sudo /etc/init.d/mysql status
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql status

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status mysql
mysql stop/waiting


>  mysql -u mythtv -p 

brain at myth-master:~$ mysql -u mythtv -p
Enter password: 
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)

(I'm assuming I would use the same PW myth does to connect...also tried w/no password and same result)


Here's the terminal output if I attempt to start it manually:
brain at myth-master:~$ /etc/init.d/mysql start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start mysql
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.43" (uid=1000 pid=3672 comm="start mysql ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
brain at myth-master:~$ sudo /etc/init.d/mysql start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start mysql
start: Job failed to start


>  - Anything interesting in the MySQL log? It should be /var/log/mysql.log 
>  and /var/log/mysql.err. 

These are both 0-byte files - the old (gzipped) mysql.log files are also empty.

>  - Have you checked available disk space? 
Yes - primary (non-recordins) partition has ~14gb avail & data partition has +200gb avail.

>  - Are there any disk related errors in syslog?
Nothing there about disks, although there is some complaining about trying to start mysql:
Sep 22 18:57:01 myth-master kernel: [ 4353.046559] type=1400 audit(1411430221.230:25): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=4104 comm="apparmor_parser"
Sep 22 18:57:02 myth-master kernel: [ 4354.165056] init: mysql main process (4108) terminated with status 1
Sep 22 18:57:02 myth-master kernel: [ 4354.165088] init: mysql main process ended, respawning
Sep 22 18:57:03 myth-master kernel: [ 4355.080353] init: mysql post-start process (4109) terminated with status 1
Sep 22 18:57:03 myth-master kernel: [ 4355.089025] type=1400 audit(1411430223.274:26): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=4156 comm="apparmor_parser"
Sep 22 18:57:04 myth-master kernel: [ 4356.204562] init: mysql main process (4160) terminated with status 1
Sep 22 18:57:04 myth-master kernel: [ 4356.204594] init: mysql main process ended, respawning
Sep 22 18:57:05 myth-master kernel: [ 4357.118818] init: mysql post-start process (4161) terminated with status 1
Sep 22 18:57:05 myth-master kernel: [ 4357.127518] type=1400 audit(1411430225.310:27): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=4208 comm="apparmor_parser"
Sep 22 18:57:06 myth-master kernel: [ 4358.240989] init: mysql main process (4212) terminated with status 1
Sep 22 18:57:06 myth-master kernel: [ 4358.241021] init: mysql respawning too fast, stopped


So I am guessing the problem is mysql is not starting/running, but I'm not really sure how to fix that, or what direction to go in to find out why this is happening. Any help is of course very much appreciated. 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140922/8a14ee4d/attachment.html>