Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

debian mysql headwrecker

  • 07-01-2015 4:53pm
    #1
    Registered Users, Registered Users 2 Posts: 9,520 ✭✭✭


    ever since i done a debian system update the mysql service refuses to start.

    Please bear in mind i am only starting out with linux but i am using the mysql in conjunction with the fog ghosting system.

    here is the error log.
    150107 10:14:05  InnoDB: Starting shutdown...
    150107 10:14:06  InnoDB: Shutdown completed; log sequence number 1720871
    150107 10:14:06 [Note]
    150107 10:14:06 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
    150107 10:24:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    150107 10:24:03 [ERROR] Can't read from messagefile '/usr/share/mysql/english/errmsg.sys'
    150107 10:24:03 [Note] Plugin 'FEDERATED' is disabled.
    150107 10:24:03 InnoDB: The InnoDB memory heap is disabled
    150107 10:24:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    150107 10:24:03 InnoDB: Compressed tables use zlib 1.2.7
    150107 10:24:03 InnoDB: Using Linux native AIO
    150107 10:24:03 InnoDB: Initializing buffer pool, size = 128.0M
    150107 10:24:03 InnoDB: Completed initialization of buffer pool
    150107 10:24:03 InnoDB: highest supported file format is Barracuda.
    150107 10:24:03  InnoDB: Waiting for the background threads to start
    150107 10:24:04 InnoDB: 5.5.40 started; log sequence number 1720871
    [B]150107 10:24:04 [ERROR] /usr/sbin/mysqld: unknown option '--explicit_defaults_for_timestamp'[/B]
    150107 10:24:04 [ERROR] Aborting
    

    any ideas?


Comments

  • Registered Users, Registered Users 2 Posts: 20,180 ✭✭✭✭jimgoose


    You'll have that kind of thing after Linux distro upgrades. Try commenting out that directive in /etc/mysql/my.cnf if it's there, and bounce the daemon.


  • Closed Accounts Posts: 431 ✭✭whats newxt


    Is errmsg.sys readable? try going to that path file right clicking on that file with the mouse pointer select properties and change/see if the file is readable if not change it

    as for the other error

    Check your my.cnf file for the options listed in the error logs and comment them out.Then start mysql again

    the above may not work but it's worth a try i guess.


  • Registered Users, Registered Users 2 Posts: 2,001 ✭✭✭lynchie


    That system var was only added in mysql 5.6 yet you are running 5.5.40 - Check your /etc/my.cnf as mentioned and remove it.


  • Registered Users, Registered Users 2 Posts: 9,520 ✭✭✭irishgeo


    i commented it out and i get the folllwoing errors in the log
    150107 15:31:02  InnoDB: Starting shutdown...
    150107 15:31:03  InnoDB: Shutdown completed; log sequence number 1720871
    150107 15:31:03 [Note] 
    150107 15:31:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
    150107 16:15:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    150107 16:15:29 [ERROR] Can't read from messagefile '/usr/share/mysql/english/errmsg.sys'
    150107 16:15:29 [Note] Plugin 'FEDERATED' is disabled.
    150107 16:15:29 InnoDB: The InnoDB memory heap is disabled
    150107 16:15:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    150107 16:15:29 InnoDB: Compressed tables use zlib 1.2.7
    150107 16:15:29 InnoDB: Using Linux native AIO
    150107 16:15:29 InnoDB: Initializing buffer pool, size = 128.0M
    150107 16:15:29 InnoDB: Completed initialization of buffer pool
    150107 16:15:30 InnoDB: highest supported file format is Barracuda.
    150107 16:15:30  InnoDB: Waiting for the background threads to start
    150107 16:15:31 InnoDB: 5.5.40 started; log sequence number 1720871
    150107 16:15:31 [ERROR] Aborting
    
    150107 16:15:31  InnoDB: Starting shutdown...
    150107 16:15:32  InnoDB: Shutdown completed; log sequence number 1720871
    150107 16:15:32 [Note] 
    150107 16:15:32 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
    

    anyway to upgarde to 5.6?


  • Registered Users, Registered Users 2 Posts: 10,271 ✭✭✭✭Standard Toaster


    Is this your issue here?
    http://bugs.mysql.com/bug.php?id=69677


  • Advertisement
Advertisement