[mythtv-users] MythBE1 Backend Failed

[Barry Martin]

Hi Geoff!

Follow-up to where I left off with the previous reply.  Hope I'm
following your instructions.  
Basically copied what was in Terminal to a thumbdrive file and pasted
here with some comments inserted.  Looks like MySQL just wants to be
extremely antisocial.  (Sorry - have to make jokes because I'm
frustrated- seems like sooooo close!)



Following Geoff's suggestion (his #2):

barry at MythBE1:~$ 
barry at MythBE1:~$ /usr/bin/chmod 777 /var/log > /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/mkdir  /var/log/mysql > /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/chmod -v 0777     /var/log/mysql > /dev/null
2>&1
barry at MythBE1:~$ /usr/bin/chpwn -v mysql:mysql  /var/log/mysql
> /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/chown -v mysql:mysql  /var/log/mysql
> /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/touch  /var/log/mysql/mysql.log > /dev/null
2>&1
barry at MythBE1:~$ /usr/bin/chown -v
mysql:mysql     /var/log/mysql/mysql.log > /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/chmod 777  /var/log/mysql/mysql.log
> /dev/null 2>&1
barry at MythBE1:~$ systemctl restart mysql.service

Job for mysql.service failed because the control process exited with
error code. See "systemctl status mysql.service" and "journalctl -xe"
for details.
barry at MythBE1:~$ 


OK, so I'm not a touch-typist! (Error in line 4.)    ...Reviewing this
post.  OK, the redirect end is for the batch file, script, whatever it
should properly be called.  I did type in as above originally and got
these notes.  What happens if I can see the output?  Put that at the
end.  (Notes for the redo start at "REDO".)



barry at MythBE1:~$ 
barry at MythBE1:~$ systemctl status mysql.service
● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor
preset: enabled)
   Active: activating (start-post) (Result: exit-code) since Wed
2016-07-13 16:48:53 CDT; 27s ago
  Process: 27033 ExecStart=/usr/sbin/mysqld (code=exited,
status=1/FAILURE)
  Process: 27029 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
(code=exited, status=0/SUCCESS)
 Main PID: 27033 (code=exited, status=1/FAILURE);         : 27034
(mysql-systemd-s)
   CGroup: /system.slice/mysql.service
           └─control
             ├─27034 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─27116 sleep 1

Jul 13 16:48:53 MythBE1 systemd[1]: Starting MySQL Community Server...
Jul 13 16:48:55 MythBE1 systemd[1]: mysql.service: Main process exited,
code=exited, status=1/FAILURE
barry at MythBE1:~$ 





journalctl -xe  -- last bunch of lines seemed o make soem sense to start
at this point:

-- Unit mysql.service has finished shutting down.
Jul 13 16:49:24 MythBE1 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has begun starting up.
Jul 13 16:49:26 MythBE1 systemd[1]: mysql.service: Main process exited,
code=exited, status=1/FAILURE
Jul 13 16:49:47 MythBE1 systemd[1]: Started CUPS Scheduler.
-- Subject: Unit cups.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit cups.service has finished starting up.
-- 
-- The start-up result is done.
Jul 13 16:49:54 MythBE1 systemd[1]: Failed to start MySQL Community
Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has failed.
-- 
-- The result is failed.
Jul 13 16:49:54 MythBE1 systemd[1]: mysql.service: Unit entered failed
state.
Jul 13 16:49:54 MythBE1 systemd[1]: mysql.service: Failed with result
'exit-code'.
Jul 13 16:49:54 MythBE1 systemd[1]: mysql.service: Service hold-off time
over, scheduling restart.
Jul 13 16:49:54 MythBE1 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has finished shutting down.
Jul 13 16:49:54 MythBE1 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has begun starting up.
Jul 13 16:49:56 MythBE1 systemd[1]: mysql.service: Main process exited,
code=exited, status=1/FAILURE




----

barry at MythBE1:~$ ExecStart=/usr/sbin/mysqld

No response --> goes to next command line.  

Tried start with sudo and got the brief help screen for sudo.  Guess is
OK.


barry at MythBE1:~$ ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
No command 'pre' found, did you mean: [etc.]


barry at MythBE1:~$ ExecStartPre=/usr/share/mysql/mysql-systemd-start
barry at MythBE1:~$ 
barry at MythBE1:~$ sudo mysql -umythtv -pmythtv mythconverg
[sudo] password for barry: 
mysql: [Warning] Using a password on the command line interface can be
insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
barry at MythBE1:~$ 

<Grrr!>


--  --  --  --

"REDO Section"

OK, here is where I got my great idea to see what the hidden output was
for this section:
barry at MythBE1:~$ /usr/bin/chmod 777 /var/log > /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/mkdir  /var/log/mysql > /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/chmod -v 0777     /var/log/mysql > /dev/null
2>&1
barry at MythBE1:~$ /usr/bin/chpwn -v mysql:mysql  /var/log/mysql
> /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/chown -v mysql:mysql  /var/log/mysql
> /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/touch  /var/log/mysql/mysql.log > /dev/null
2>&1
barry at MythBE1:~$ /usr/bin/chown -v
mysql:mysql     /var/log/mysql/mysql.log > /dev/null 2>&1
barry at MythBE1:~$ /usr/bin/chmod 777  /var/log/mysql/mysql.log
> /dev/null 2>&1
barry at MythBE1:~$ systemctl restart mysql.service


barry at MythBE1:~$ /usr/bin/chmod 777 /var/log
bash: /usr/bin/chmod: No such file or directory
barry at MythBE1:~$ sudo /usr/bin/chmod 777 /var/log
sudo: /usr/bin/chmod: command not found
barry at MythBE1:~$ 
barry at MythBE1:~$ chmod 777 /var/log
chmod: changing permissions of '/var/log': Operation not permitted
barry at MythBE1:~$ sudo chmod 777 /var/log
barry at MythBE1:~$ 
barry at MythBE1:~$ mkdir /var/log/mysql
mkdir: cannot create directory ‘/var/log/mysql’: File exists
barry at MythBE1:~$ 
barry at MythBE1:~$ sudo chmod -v 777 /var/log/mysql
mode of '/var/log/mysql' changed from 0750 (rwxr-x---) to 0777
(rwxrwxrwx)
barry at MythBE1:~$ 
barry at MythBE1:~$ sudo chown -v mysql:mysql /var/log/mysql
changed ownership of '/var/log/mysql' from mysql:adm to mysql:mysql
barry at MythBE1:~$ 
barry at MythBE1:~$ sudo touch /var/log/mysql/mysql.log
barry at MythBE1:~$ 
barry at MythBE1:~$ sudo chown -v mysql:mysql /var/log/mysql/mysql.log
changed ownership of '/var/log/mysql/mysql.log' from root:root to
mysql:mysql
barry at MythBE1:~$ 
barry at MythBE1:~$ sudo chmod 777 /var/log/mysql/mysql.log
barry at MythBE1:~$ 
barry at MythBE1:~$ systemctl restart mysql.service
Job for mysql.service failed because the control process exited with
error code. See "systemctl status mysql.service" and "journalctl -xe"
for details.
barry at MythBE1:~$ 

Ah poo...



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160713/57c9a40c/attachment.html>