/ Register

Join the community today
Register Now

MariaDB Error When Trying To Restart MySQL

Discussion in 'Nginx, PHP-FPM & MariaDB MySQL' started by BamaStangGuy, Oct 31, 2014.

Previous Thread Next Thread
Loading...
  1. Oct 31, 2014 #1
    BamaStangGuy

    BamaStangGuy Premium Member Premium Member

    651
    189
    43
    May 25, 2014
    Ratings:
    +264
    Local Time:
    11:02 AM
    I get this every time I try to restart MySQL:
    [root@localhost forum]# service mysql restart

    ERROR! MySQL server PID file could not be found!

    Starting MySQL SUCCESS!

    It appears to not actually restart it.
     
  2. Oct 31, 2014 #2
    eva2000

    eva2000 Administrator Staff Member

    46,002
    10,452
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +16,214
    Local Time:
    3:02 AM
    Nginx 1.19.x
    MariaDB 5.5/10.x
    I'd check your mysql error log which is listed along with all other log file locations as per How to troubleshoot Centmin Mod initial install issues (/var/log/mysqld.log) for clues

    If it's related to different sized innodb_log_file_size compared to the initialised innodb instance on initial Centmin Mod install which defaults to 48M size or 64M size, then you'd need to change innodb_log_file_size as per official MySQL documentation for Changing Size of InnoDB Log Files. Only move/delete the log files ib_logfile0, ib_logfile1 redo logs when MySQL is shutdown.
     
  3. Oct 31, 2014 #3
    BamaStangGuy

    BamaStangGuy Premium Member Premium Member

    651
    189
    43
    May 25, 2014
    Ratings:
    +264
    Local Time:
    11:02 AM
    A reboot of the server fixed it. Guess it had rogue processes it couldn't kill.
     
  4. Oct 31, 2014 #4
    eva2000

    eva2000 Administrator Staff Member

    46,002
    10,452
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +16,214
    Local Time:
    3:02 AM
    Nginx 1.19.x
    MariaDB 5.5/10.x
    still good to check mysql error log for more underlying issues as to why it didn't restart :)
     
  5. Apr 29, 2015 #5
    jeffwidman

    jeffwidman Active Member

    152
    27
    28
    Dec 3, 2014
    Ratings:
    +51
    Local Time:
    9:02 AM
    I just hit this as well. I hadn't touched the innodb_log_files; only thing I changed was making the innodb_buffer_pool_size smaller than it previously was. My best guess is that when MariaDB tried to reload the buffer pool (since it saves it to disk when it shuts down) it fails because the file on disk is now bigger than allowed to be loaded into ram. A reboot of the server fixed it.
     
Previous Thread Next Thread
Loading...

.