Yes, I understand the it should be run with mysql user. This is only a development machine, so not too worried about security
right now..more worried about getting up and developing
. Version is 5.6
ii mysql-common 5.5.37-1
ii mysql-common-5.6 5.6.19-1~exp1
ii mysql-server-5.6 5.6.19-1~exp1
ii mysql-server-core-5.6 5.6.19-1~exp1
I don't think I am going to be able to create a log file because it fails at the su so mysql command does not ever run. This is not a problem with mysql, more like a bash issue.
Yes, Debian AMD64. 'echo $0' shows I am running bash. Your command 'dpkg-reconfigure dash' seems to configure the shell to dash. You meant to say bash right? I did run the command but said no to changing to dash and it configured bash so now I'm getting this which is a step forward, no more weird bash-completion errors:
mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Tue 2014-07-29 00:15:41 PDT; 2min 20s ago
Jul 29 00:15:09 linksys systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 29 00:15:10 linksys su[4636]: Successful su for mysql by root
Jul 29 00:15:10 linksys su[4636]: + ??? root:mysql
Jul 29 00:15:10 linksys su[4636]: pam_unix(su:session): session opened for user mysql by (uid=0)
Jul 29 00:15:41 linksys mysql[4608]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . ....ailed!
Jul 29 00:15:41 linksys systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 29 00:15:41 linksys systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 29 00:15:41 linksys systemd[1]: Unit mysql.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
After removing a few more packages and disabling some service, it is finally running. Not exactly sure what fixed it though but szboardstretcher's idea definitely lead to the answer(thank you very much and thanks to all who contributed). I think I was in a dash shell. I know I installed dash because it is smaller and faster. Something is not right with it if it tries to do something bash-completion(that'll be a bug for Debian folks to work out maybe). Also learned a couple of new things about Linux. Here is a command history if it will help anyone in the future(I had 2 consoles open...):
aptitude remove console-kit
502 scite /etc/init.d/mysql
503 ps -A
504 ps -A | grep mysql
505 ps axf
506 aptitude remove pykaraoke
507 aptitude remove timidity
508 ps -A | grep smb
509 update-rc.d disable smbd 2 3 4 5
510 update-rc.d smbd disable 2 3 4 5
511 systemctl --help
512 systemctl disable smbd.service
513 systemctl stop smbd.service
514 ps -A | grep smb
515 ps A
516 ps axf
517 systemctl stop proftpd.service
518 systemctl disable proftpd.service
519 systemctl stop gpm.service
520 systemctl disable gpm.service
521 systemctl stop nmbd.service
522 systemctl disable nmbd.service
523 systemctl disable scanlogd.service
524 systemctl stop scanlogd.service
525 ps axf
526 dpkg -l | grep udisks
527 service udisks status
528 service udisks sttop
529 service udisks stop
530 service udisks start
531 service udisks status
532* service udisks st
533 service udisks status
534 service udisks2 start
535 service udisks status
536 service udisks2 status
537 dpkg -l | grep udisk
538 aptitude remove udisks
539 ps -A
540 ps axf
543 cat /var/log/mysql/error.log
544 rm /var/log/mysql/error.log
545 ps axf | grep mysql
546 scite /etc/init.d/mysql
528 aptitude purge consolekit
529 sudo aptitude purge consolekit
530 dpkg remove foomatic-filters ghostscript-cups udisk2 upower udisks libcolord2
531 sudo aptitude remove foomatic-filters ghostscript-cups udisk2 upower udisks libcolord2
532 dpkg-reconfigure dash
533 sudo dpkg-reconfigure dash
534 echo $0
535 sudo service mysql start
536 systemctl status mysql.service
537 journalctl -xn
538 systemctl start mysql
539 sudo systemctl start mysql
540 journalctl -xn
541 sudo systemctl start apache2
542 sudo systemctl stop mysql
543 sudo systemctl start mysql
@jpollard, in Debian, this su - mysql -s /bin/sh -c "/usr/bin/mysqld_safe > /dev/null 2>&1 &" thing was in a init script so I used it. I just ran it in bash and it does run now, it wasn't running before.
