Learn about Centmin Mod LEMP Stack today
Become a Member

MariaDB Failed to Start MariaDB 10.1.38 Database Server

Discussion in 'Nginx, PHP-FPM & MariaDB MySQL' started by Hiperteks, Apr 1, 2019.

  1. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    Please help. Can not :
    • CentOS Version: CentOS 7 64bit
    • Centmin Mod Version Installed: 123.09beta01
    • Nginx Version Installed: 1.15.10
    • PHP Version Installed: 7.2.4
    • MariaDB MySQL Version Installed: 10.1.38
    Code (Text):
    [22:02][[email protected] ~]# cminfo top
    ------------------------------------------------------------------
     Centmin Mod Top Info:
    ------------------------------------------------------------------
     Server Location Info
    
      city: Singapore
      region: Central Singapore Community Development Council
      country: SG
      ASN: AS63949 Linode, LLC
    
     Processors physical = 2, cores = 2, virtual = 2, hyperthreading = no
    
          2  2499.984
          2  Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz
          2  16384 KB
    
     System Up Since:     2019-03-31 21:49:36
     System Uptime:     up 13 minutes
     MySQL Server Started     not running
     MySQL Uptime:         not running
     MySQL Uptime (secs):     not running
     Server Type:         kvm
     CentOS Version:     7.6
     Centmin Mod:         123.09beta01.b120
     Nginx PageSpeed:     OFF
     Nginx Version:     1.15.10 (310319-202454-centos7-kvm)
     PHP-FPM Version:     7.2.4
     MariaDB Version:     10.1.38
     CSF Firewall:         v12.10
     Memcached Server:     1.5.7
     NSD Version:         -
     Siege Version:     4.0.2
     Maldet Version:     not installed
     ClamAV Version:     not installed
     ElasticSearch:     not installed
    
    ------------------------------------------------------------------
    free -mtl
                  total        used        free      shared  buff/cache   available
    Mem:           3930         487        2436          67        1005        3074
    Low:           3930        1493        2436
    High:             0           0           0
    Swap:           511           0         511
    Total:         4442         487        2948
    
    ------------------------------------------------------------------
    df -hT
    Filesystem     Type      Size  Used Avail Use% Mounted on
    /dev/root      ext4       47G   46G     0 100% /
    devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
    tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
    tmpfs          tmpfs     2.0G  8.7M  2.0G   1% /run
    tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
    /dev/loop0     ext4      5.8G   25M  5.5G   1% /tmp
    tmpfs          tmpfs     394M     0  394M   0% /run/user/0
    


    /etc/centminmod/custom_config.inc
    Code (Text):
    cat /etc/centminmod/custom_config.inc
    # Nginx Dynamic Module Switches
    NGXDYNAMIC_NJS='n'
    NGXDYNAMIC_XSLT='y'
    NGXDYNAMIC_PERL='n'
    NGXDYNAMIC_IMAGEFILTER='y'
    NGXDYNAMIC_GEOIP='n'
    NGXDYNAMIC_STREAM='y'
    NGXDYNAMIC_STREAMGEOIP='y'  # nginx 1.11.3+ option http://hg.nginx.org/nginx/rev/558db057adaa
    NGXDYNAMIC_STREAMREALIP='y' # nginx 1.11.4+ option http://hg.nginx.org/nginx/rev/9cac11efb205
    NGXDYNAMIC_HEADERSMORE='y'
    NGXDYNAMIC_SETMISC='y'
    NGXDYNAMIC_ECHO='y'
    NGXDYNAMIC_LUA='n'          # leave disabled due to bug https://github.com/openresty/lua-nginx-module/issues/715
    NGXDYNAMIC_SRCCACHE='y'
    NGXDYNAMIC_DEVELKIT='n'     # leave disabled as it requires lua nginx module as dynamic but it has a bug in lua nginx
    NGXDYNAMIC_MEMC='y'
    NGXDYNAMIC_REDISTWO='y'
    NGXDYNAMIC_NGXPAGESPEED='n'
    NGXDYNAMIC_BROTLI='y'
    NGXDYNAMIC_FANCYINDEX='y'
    NGXDYNAMIC_HIDELENGTH='y'
    
    NGINX_PAGESPEED=y
    LETSENCRYPT_DETECT='n'
    MARCH_TARGETNATIVE='n'
    LETSENCRYPT_DETECT='y'
    NGXDYNAMIC_BROTLI='y'
    NGINX_LIBBROTLI='y'
    NGINX_BROTLIDEP_UPDATE='y'
    PHP_ARGON='y' # potrebno za bolji hash algoritam passworda na xenforu
    PHP_BROTLI='y' # brotli php extension https://github.com/kjdev/php-ext-brotli
    PHP_LZFOUR='y' # lz4 php extension https://github.com/kjdev/php-ext-lz4
    PHP_LZF='y' # lzf php extension https://github.com/php/pecl-file_formats-lzf php-ext-lzf
    PHP_ZSTD='y' # zstd php extension https://github.com/kjdev/php-ext-zstd
    #AUTODETECPHP_OVERRIDE='y' # recompile php exensions on minor php (aka 7.3.x) upgrade
    AUDITD_ENABLE='y' # Auditd skripta
    RCLONE_ENABLE='y' # Rclone skripta
    NGINX_DEVTOOLSETGCC='y' # umjesto clang ide gcc kompilacija kod nginx
    DEVTOOLSETEIGHT='y' # ide 8.x verzija gcc kompilacije umjesto defaultne 5.x ili 6.x ili 7.x
    #CRYPTO_DEVTOOLSETGCC='y' # newer Intel GCC
    #NGINX_HPACK='y' # enabling HPACK for Nginx
    NGINX_DYNAMICTLS='y' # add Nginx Dynamic TLS Cloudflare Patch - http://bit.ly/2EYzhk7
    NGINXPATCH='y' # add Nginx Dynamic TLS Cloudflare Patch - http://bit.ly/2EYzhk7
    NGINX_GEOIPTWOLITE='y' # GeoIP2 Lite nginx module
    NGXDYNAMIC_GEOIPTWOLITE='y' # GeoIP2 Lite nginx module
    


    Code (Text):
    mysql -v input
    [23:03][[email protected] ~]# mysql -v
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused")
    


    mysqlrestart
    Code (Text):
    [23:08][[email protected] ~]# mysqlrestart
    Restarting mysql (via systemctl):  Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
                                                               [FAILED]
    


    systemctl status mariadb.service -l
    Code (Text):
    [23:11][[email protected] ~]# systemctl status mariadb.service -l
    ● mariadb.service - MariaDB 10.1.38 database server
       Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
               └─migrated-from-my.cnf-settings.conf, openfileslimit.conf, protecthome.conf
       Active: failed (Result: exit-code) since Sun 2019-03-31 23:09:01 UTC; 3min 12s ago
         Docs: man:mysqld(8)
               https://mariadb.com/kb/en/library/systemd/
      Process: 13661 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
      Process: 13436 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
      Process: 13434 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
     Main PID: 13661 (code=exited, status=1/FAILURE)
       Status: "MariaDB server is down"
    
    Mar 31 23:09:00 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 23:09:01 sg2.domain.com mysqld[13661]: 2019-03-31 23:09:01 139854599416064 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 23:09:01 sg2.domain.com mysqld[13661]: 2019-03-31 23:09:01 139854599416064 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 13661 ...
    Mar 31 23:09:01 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 23:09:01 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 23:09:01 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 23:09:01 sg2.domain.com systemd[1]: mariadb.service failed.
    



    I tried this but it didn't work.
    https://community.centminmod.com/threads/mariadb-10-1-16-unable-to-restart-fix.8071/

    MariaDB mysql error logs
    Code (Text):
    [23:22][[email protected] ~]# journalctl -u mariadb --no-pager | sed -e "s|$(hostname)|hostname|g" | tail -500
    -- Logs begin at Sun 2019-03-31 21:49:37 UTC, end at Sun 2019-03-31 23:22:58 UTC. --
    Mar 31 21:49:40 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 2850 ...
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Using Linux native AIO
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 7f1069d51900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 21:49:41 hostname mysqld[2850]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 21:49:41 hostname mysqld[2850]: InnoDB: Operating system error number 28.
    Mar 31 21:49:41 hostname mysqld[2850]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 21:49:41 hostname mysqld[2850]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 21:49:41 hostname mysqld[2850]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 21:49:41 hostname mysqld[2850]: InnoDB: Some operating system error numbers are described at
    Mar 31 21:49:41 hostname mysqld[2850]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 21:49:41 hostname mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Aborting
    Mar 31 21:49:41 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 21:49:41 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 21:49:41 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 21:49:41 hostname systemd[1]: mariadb.service failed.
    Mar 31 21:58:58 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 3586 ...
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Using Linux native AIO
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 7ff66aa4f900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 21:58:59 hostname mysqld[3586]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 21:58:59 hostname mysqld[3586]: InnoDB: Operating system error number 28.
    Mar 31 21:58:59 hostname mysqld[3586]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 21:58:59 hostname mysqld[3586]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 21:58:59 hostname mysqld[3586]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 21:58:59 hostname mysqld[3586]: InnoDB: Some operating system error numbers are described at
    Mar 31 21:58:59 hostname mysqld[3586]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 21:58:59 hostname mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Aborting
    Mar 31 21:58:59 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 21:58:59 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 21:58:59 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 21:58:59 hostname systemd[1]: mariadb.service failed.
    Mar 31 22:00:46 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 4196 ...
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 7f452735d900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:00:46 hostname mysqld[4196]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:00:46 hostname mysqld[4196]: InnoDB: Operating system error number 28.
    Mar 31 22:00:46 hostname mysqld[4196]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:00:46 hostname mysqld[4196]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:00:46 hostname mysqld[4196]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:00:46 hostname mysqld[4196]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:00:46 hostname mysqld[4196]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 22:00:46 hostname mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Aborting
    Mar 31 22:00:46 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:00:46 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:00:46 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:00:46 hostname systemd[1]: mariadb.service failed.
    Mar 31 22:02:17 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 5481 ...
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 7fc5ef7ba900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:02:18 hostname mysqld[5481]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:02:18 hostname mysqld[5481]: InnoDB: Operating system error number 28.
    Mar 31 22:02:18 hostname mysqld[5481]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:02:18 hostname mysqld[5481]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:02:18 hostname mysqld[5481]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:02:18 hostname mysqld[5481]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:02:18 hostname mysqld[5481]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 22:02:18 hostname mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Aborting
    Mar 31 22:02:18 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:02:18 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:02:18 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:02:18 hostname systemd[1]: mariadb.service failed.
    Mar 31 22:25:18 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 8790 ...
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] mysqld: Error writing file '/var/lib/mysql/aria_log_control' (Errcode: 28 "No space left on device")
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] mysqld: Got error 'Can't create file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] Plugin 'Aria' init function returned error.
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:25:18 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:19 7f5e97aba900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:25:19 hostname mysqld[8790]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:25:19 hostname mysqld[8790]: InnoDB: Operating system error number 28.
    Mar 31 22:25:19 hostname mysqld[8790]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:25:19 hostname mysqld[8790]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:25:19 hostname mysqld[8790]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:25:19 hostname mysqld[8790]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:25:19 hostname mysqld[8790]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 22:25:19 hostname mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 22:25:19 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:25:19 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:25:19 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:25:19 hostname systemd[1]: mariadb.service failed.
    Mar 31 22:27:12 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 9207 ...
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when trying to use aria control file '/var/lib/mysql/aria_log_control'
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [ERROR] Plugin 'Aria' init function returned error.
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:27:12 hostname mysqld[9207]: 2019-03-31 22:27:12 7fdabc406900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:27:12 hostname mysqld[9207]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:27:12 hostname mysqld[9207]: InnoDB: Operating system error number 28.
    Mar 31 22:27:12 hostname mysqld[9207]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:27:12 hostname mysqld[9207]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:27:12 hostname mysqld[9207]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:27:12 hostname mysqld[9207]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:27:12 hostname mysqld[9207]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:27:12 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:27:12 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:27:12 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:27:12 hostname systemd[1]: mariadb.service failed.
    Mar 31 22:53:24 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:53:24 hostname mysqld[12044]: 2019-03-31 22:53:24 140185134954752 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 22:53:24 hostname mysqld[12044]: 2019-03-31 22:53:24 140185134954752 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 12044 ...
    Mar 31 22:53:24 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:53:24 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:53:24 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:53:24 hostname systemd[1]: mariadb.service failed.
    Mar 31 22:56:46 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:56:47 hostname mysqld[12517]: 2019-03-31 22:56:47 140012949309696 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 22:56:47 hostname mysqld[12517]: 2019-03-31 22:56:47 140012949309696 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 12517 ...
    Mar 31 22:56:47 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:56:47 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:56:47 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:56:47 hostname systemd[1]: mariadb.service failed.
    Mar 31 23:09:00 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 23:09:01 hostname mysqld[13661]: 2019-03-31 23:09:01 139854599416064 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 23:09:01 hostname mysqld[13661]: 2019-03-31 23:09:01 139854599416064 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 13661 ...
    Mar 31 23:09:01 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 23:09:01 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 23:09:01 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 23:09:01 hostname systemd[1]: mariadb.service failed.
    Mar 31 23:22:00 hostname systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 23:22:00 hostname mysqld[22239]: 2019-03-31 23:22:00 139744912476416 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 23:22:00 hostname mysqld[22239]: 2019-03-31 23:22:00 139744912476416 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 22239 ...
    Mar 31 23:22:00 hostname systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 23:22:00 hostname systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 23:22:00 hostname systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 23:22:00 hostname systemd[1]: mariadb.service failed.
    [23:23][[email protected] ~]#
    



    I tried to delete delete aria_log_control too, but it didn't work, Mariadb remained down.

    Very sad. I can't even backup the database.
     
  2. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    my.cnf
    Code (Text):
    [client]
    socket=/var/lib/mysql/mysql.sock
    
    [mysql]
    max_allowed_packet = 64M
    
    [mysqld]
    local-infile=0
    ignore-db-dir=lost+found
    character-set-server=utf8
    datadir=/var/lib/mysql
    socket=/var/lib/mysql/mysql.sock
    
    #bind-address=127.0.0.1
    # optimized my.cnf for MariaDB 5.5.x
    # by eva2000
    # centminmod.com
    
    tmpdir=/home/mysqltmp
    
    innodb=ON
    #skip-federated
    #skip-pbxt
    #skip-pbxt_statistics
    #skip-archive
    #skip-name-resolve
    #old_passwords
    back_log = 512
    max_connections = 500
    key_buffer_size = 256M
    myisam_sort_buffer_size = 256M
    myisam_max_sort_file_size = 2048M
    join_buffer_size = 256K
    read_buffer_size = 256K
    sort_buffer_size = 256K
    table_definition_cache = 8192
    table_open_cache = 4096
    thread_cache_size = 256
    wait_timeout = 1800
    connect_timeout = 10
    tmp_table_size = 256M
    max_heap_table_size = 256M
    max_allowed_packet = 64M
    #max_seeks_for_key = 4294967295
    #group_concat_max_len = 1024
    max_length_for_sort_data = 1024
    net_buffer_length = 16384
    max_connect_errors = 100000
    concurrent_insert = 2
    read_rnd_buffer_size = 512K
    bulk_insert_buffer_size = 8M
    # query_cache boost for MariaDB >10.1.2+
    # [URL]https://community.centminmod.com/posts/30811/[/URL]
    query_cache_limit = 1024K
    query_cache_size = 80M
    query_cache_type = 1
    query_cache_min_res_unit = 2K
    query_prealloc_size = 262144
    query_alloc_block_size = 65536
    transaction_alloc_block_size = 8192
    transaction_prealloc_size = 4096
    default-storage-engine = InnoDB
    
    log_warnings=1
    slow_query_log=0
    long_query_time=1
    slow_query_log_file=/var/lib/mysql/slowq.log
    log-error=/var/log/mysqld.log
    
    # innodb settings
    innodb_large_prefix=1
    innodb_purge_threads=1
    innodb_file_format = Barracuda
    innodb_file_per_table = 1
    innodb_open_files = 4000
    innodb_data_file_path= ibdata1:10M:autoextend
    innodb_buffer_pool_size = 512M
    
    ## [URL]https://mariadb.com/kb/en/mariadb/xtradbinnodb-server-system-variables/#innodb_buffer_pool_instances[/URL]
    #innodb_buffer_pool_instances=2
    
    innodb_log_files_in_group = 2
    innodb_log_file_size = 256M
    innodb_log_buffer_size = 8M
    innodb_flush_log_at_trx_commit = 2
    innodb_thread_concurrency = 0
    innodb_lock_wait_timeout=50
    innodb_flush_method = O_DIRECT
    innodb_support_xa=1
    
    # 200 * # DISKS
    innodb_io_capacity = 300
    innodb_io_capacity_max = 2000
    innodb_read_io_threads = 4
    innodb_write_io_threads = 2
    innodb_flush_neighbors = 1
    
    # mariadb settings
    [mariadb]
    #thread-handling = pool-of-threads
    #thread-pool-size= 20
    #mysql --port=3307 --protocol=tcp
    #extra-port=3307
    #extra-max-connections=1
    
    userstat = 0
    key_cache_segments = 1
    aria_group_commit = none
    aria_group_commit_interval = 0
    aria_log_file_size = 64M
    aria_log_purge_type = immediate
    aria_pagecache_buffer_size = 64M
    aria_sort_buffer_size = 64M
    
    [mariadb-5.5]
    innodb_file_format = Barracuda
    innodb_file_per_table = 1
    
    #ignore_db_dirs=
    query_cache_strip_comments=0
    
    innodb_read_ahead = linear
    innodb_adaptive_flushing_method = estimate
    innodb_flush_neighbor_pages = 1
    innodb_stats_update_need_lock = 0
    innodb_log_block_size = 512
    
    log_slow_filter =admin,filesort,filesort_on_disk,full_join,full_scan,query_cache,query_cache_miss,tmp_table,tmp_table_on_disk
    
    [mysqld_safe]
    socket=/var/lib/mysql/mysql.sock
    log-error=/var/log/mysqld.log
    #nice = -5
    open-files-limit = 8192
    
    [mysqldump]
    quick
    max_allowed_packet = 64M
    
    [myisamchk]
    tmpdir=/home/mysqltmp
    key_buffer = 256M
    sort_buffer = 32M
    read_buffer = 32M
    write_buffer = 32M
    
    [mysqlhotcopy]
    interactive-timeout
    
    [mariadb-10.0]
    innodb_file_format = Barracuda
    innodb_file_per_table = 1
    
    # 2 variables needed to switch from XtraDB to InnoDB plugins
    #plugin-load=ha_innodb
    #ignore_builtin_innodb
    
    ## MariaDB 10 only save and restore buffer pool pages
    ## warm up InnoDB buffer pool on server restarts
    innodb_buffer_pool_dump_at_shutdown=1
    innodb_buffer_pool_load_at_startup=1
    innodb_buffer_pool_populate=0
    ## Disabled settings
    performance_schema=OFF
    innodb_stats_on_metadata=OFF
    innodb_sort_buffer_size=2M
    innodb_online_alter_log_max_size=128M
    query_cache_strip_comments=0
    log_slow_filter =admin,filesort,filesort_on_disk,full_join,full_scan,query_cache,query_cache_miss,tmp_table,tmp_table_on_disk
     
  3. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    Code (Text):
    [00:10][[email protected] ~]# ls -lah /home | grep mysqltmp
    drwxrwxrwt   2 mysql      mysql      4.0K Apr  1 00:06 mysqltmp


    journalctl -u mariadb --no-pager
    Code (Text):
    [00:12][[email protected] ~]#  journalctl -u mariadb --no-pager
    -- Logs begin at Sun 2019-03-31 21:49:37 UTC, end at Mon 2019-04-01 00:13:26 UTC. --
    Mar 31 21:49:40 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 2850 ...
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Using Linux native AIO
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 7f1069d51900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: InnoDB: Operating system error number 28.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: InnoDB: Some operating system error numbers are described at
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 21:49:41 sg2.domain.com mysqld[2850]: 2019-03-31 21:49:41 139708471777536 [ERROR] Aborting
    Mar 31 21:49:41 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 21:49:41 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 21:49:41 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 21:49:41 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 21:58:58 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 3586 ...
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Using Linux native AIO
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 7ff66aa4f900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: InnoDB: Operating system error number 28.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: InnoDB: Some operating system error numbers are described at
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 21:58:59 sg2.domain.com mysqld[3586]: 2019-03-31 21:58:59 140696327878912 [ERROR] Aborting
    Mar 31 21:58:59 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 21:58:59 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 21:58:59 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 21:58:59 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 22:00:46 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 4196 ...
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 7f452735d900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: InnoDB: Operating system error number 28.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 22:00:46 sg2.domain.com mysqld[4196]: 2019-03-31 22:00:46 139934987311360 [ERROR] Aborting
    Mar 31 22:00:46 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:00:46 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:00:46 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:00:46 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 22:02:17 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 5481 ...
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 7fc5ef7ba900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: InnoDB: Operating system error number 28.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 22:02:18 sg2.domain.com mysqld[5481]: 2019-03-31 22:02:18 140488103143680 [ERROR] Aborting
    Mar 31 22:02:18 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:02:18 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:02:18 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:02:18 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 22:25:18 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 8790 ...
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] mysqld: Error writing file '/var/lib/mysql/aria_log_control' (Errcode: 28 "No space left on device")
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] mysqld: Got error 'Can't create file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] Plugin 'Aria' init function returned error.
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:25:18 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:18 140044248262912 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:19 7f5e97aba900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: InnoDB: Operating system error number 28.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 128 MB
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 22:25:19 sg2.domain.com mysqld[8790]: 2019-03-31 22:25:19 140044248262912 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 22:25:19 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:25:19 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:25:19 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:25:19 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 22:27:12 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 9207 ...
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when trying to use aria control file '/var/lib/mysql/aria_log_control'
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [ERROR] Plugin 'Aria' init function returned error.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Using Linux native AIO
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 140577437935872 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: 2019-03-31 22:27:12 7fdabc406900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: InnoDB: Operating system error number 28.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: InnoDB: Some operating system error numbers are described at
    Mar 31 22:27:12 sg2.domain.com mysqld[9207]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 22:27:12 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:27:12 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:27:12 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:27:12 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 22:53:24 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:53:24 sg2.domain.com mysqld[12044]: 2019-03-31 22:53:24 140185134954752 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 22:53:24 sg2.domain.com mysqld[12044]: 2019-03-31 22:53:24 140185134954752 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 12044 ...
    Mar 31 22:53:24 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:53:24 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:53:24 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:53:24 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 22:56:46 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 22:56:47 sg2.domain.com mysqld[12517]: 2019-03-31 22:56:47 140012949309696 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 22:56:47 sg2.domain.com mysqld[12517]: 2019-03-31 22:56:47 140012949309696 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 12517 ...
    Mar 31 22:56:47 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 22:56:47 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 22:56:47 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 22:56:47 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 23:09:00 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 23:09:01 sg2.domain.com mysqld[13661]: 2019-03-31 23:09:01 139854599416064 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 23:09:01 sg2.domain.com mysqld[13661]: 2019-03-31 23:09:01 139854599416064 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 13661 ...
    Mar 31 23:09:01 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 23:09:01 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 23:09:01 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 23:09:01 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 23:22:00 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 23:22:00 sg2.domain.com mysqld[22239]: 2019-03-31 23:22:00 139744912476416 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 23:22:00 sg2.domain.com mysqld[22239]: 2019-03-31 23:22:00 139744912476416 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 22239 ...
    Mar 31 23:22:00 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 23:22:00 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 23:22:00 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 23:22:00 sg2.domain.com systemd[1]: mariadb.service failed.
    Mar 31 23:51:44 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 17461 ...
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when trying to use aria control file '/var/lib/mysql/aria_log_control'
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] Plugin 'Aria' init function returned error.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: The InnoDB memory heap is disabled
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Using Linux native AIO
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Using SSE crc32 instructions
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Initializing buffer pool, size = 512.0M
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Completed initialization of buffer pool
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] InnoDB: Setting log file ./ib_logfile101 size to 256 MB
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 7f440cf71900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: InnoDB: Operating system error number 28.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: InnoDB: Check that your OS and file system support files of this size.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: InnoDB: Error number 28 means 'No space left on device'.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: InnoDB: Some operating system error numbers are described at
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 256 MB
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] Plugin 'InnoDB' init function returned error.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] Unknown/unsupported storage engine: InnoDB
    Mar 31 23:51:44 sg2.domain.com mysqld[17461]: 2019-03-31 23:51:44 139930252024064 [ERROR] Aborting
    Mar 31 23:51:44 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Mar 31 23:51:44 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Mar 31 23:51:44 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Mar 31 23:51:44 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 00:06:27 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 22685 ...
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when trying to use aria control file '/var/lib/mysql/aria_log_control'
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] Plugin 'Aria' init function returned error.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: The InnoDB memory heap is disabled
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Compressed tables use zlib 1.2.7
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Using Linux native AIO
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Using SSE crc32 instructions
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Initializing buffer pool, size = 512.0M
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Completed initialization of buffer pool
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] InnoDB: Setting log file ./ib_logfile101 size to 256 MB
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01 00:06:27 7f83d01e7900 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: InnoDB: 1048576 bytes should have been written, only 0 were written.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: InnoDB: Operating system error number 28.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: InnoDB: Check that your OS and file system support files of this size.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: InnoDB: Error number 28 means 'No space left on device'.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: InnoDB: Some operating system error numbers are described at
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 256 MB
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] Plugin 'InnoDB' init function returned error.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [Note] Plugin 'FEEDBACK' is disabled.
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] Unknown/unsupported storage engine: InnoDB
    Apr 01 00:06:27 sg2.domain.com mysqld[22685]: 2019-04-01  0:06:27 140204109101312 [ERROR] Aborting
    Apr 01 00:06:27 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 00:06:27 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 00:06:27 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 00:06:27 sg2.domain.com systemd[1]: mariadb.service failed.
     
  4. eva2000

    eva2000 Administrator Staff Member

    39,742
    8,765
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +13,486
    Local Time:
    7:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    • Like Like x 1
  5. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    Thank you very much, @eva2000. I will add disk space.
     
  6. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    I have doubled the RAM and SSD. Mariadb is still down. There is no solution yet. I dont khow whats wrong.

    Code (Text):
    [04:36][[email protected] ~]# service mysqld status -l
    Redirecting to /bin/systemctl status  -l mysqld.service
    ● mariadb.service - MariaDB 10.1.38 database server
       Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
               └─migrated-from-my.cnf-settings.conf, openfileslimit.conf, protecthome.conf
       Active: failed (Result: exit-code) since Mon 2019-04-01 04:27:29 UTC; 8min ago
         Docs: man:mysqld(8)
               https://mariadb.com/kb/en/library/systemd/
      Process: 23998 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
      Process: 23774 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
      Process: 23772 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
     Main PID: 23998 (code=exited, status=1/FAILURE)
       Status: "MariaDB server is down"
    
    Apr 01 04:27:26 sg2.domain.com mysqld[23998]: 2019-04-01 04:27:26 7fe2dcf86900 InnoDB: Error: page 555 log sequence number 179058757040
    Apr 01 04:27:26 sg2.domain.com mysqld[23998]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:27:26 sg2.domain.com mysqld[23998]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:27:26 sg2.domain.com mysqld[23998]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:27:26 sg2.domain.com mysqld[23998]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:27:26 sg2.domain.com mysqld[23998]: InnoDB: for more information.
    Apr 01 04:27:29 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 04:27:29 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 04:27:29 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 04:27:29 sg2.domain.com systemd[1]: mariadb.service failed.
    [04:36][[email protected] ~]#
     
  7. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    journalctl -u mariadb --no-pager

    Code (Text):
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 475 log sequence number 179058480377
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 701 log sequence number 179053970959
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 245 log sequence number 179058752929
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 531 log sequence number 179058752929
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 565 log sequence number 179058438164
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 246 log sequence number 179057962572
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1093 log sequence number 179057962572
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 758 log sequence number 179053972539
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 247 log sequence number 179058753155
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1207 log sequence number 179058753155
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 745 log sequence number 179056737424
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 248 log sequence number 179057808227
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1181 log sequence number 179057808227
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 553 log sequence number 179056737909
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 249 log sequence number 179058753365
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1185 log sequence number 179058753365
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 378 log sequence number 179058438822
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 250 log sequence number 179057808339
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 488 log sequence number 179058075705
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 251 log sequence number 179058753591
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1186 log sequence number 179058753591
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 575 log sequence number 179058439080
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 252 log sequence number 179057808399
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 366 log sequence number 179057808399
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 582 log sequence number 179058439504
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 253 log sequence number 179058753825
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 438 log sequence number 179056390765
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 310 log sequence number 179058753825
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 254 log sequence number 179058480668
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 421 log sequence number 179058439757
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1134 log sequence number 179058480668
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 255 log sequence number 179058754035
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1135 log sequence number 179058754035
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 312 log sequence number 179058440530
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 256 log sequence number 179057808487
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1131 log sequence number 179057808487
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1203 log sequence number 179057734864
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 257 log sequence number 179058754261
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 393 log sequence number 179058440819
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1136 log sequence number 179058754261
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 258 log sequence number 179058480798
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 670 log sequence number 179057308283
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 664 log sequence number 179058480798
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 259 log sequence number 179058754471
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 669 log sequence number 179058754471
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 633 log sequence number 179054836817
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 260 log sequence number 179057808619
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 333 log sequence number 179057329760
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 639 log sequence number 179057808619
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 261 log sequence number 179058754696
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 439 log sequence number 179055099138
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1189 log sequence number 179058754696
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 262 log sequence number 179058480972
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1190 log sequence number 179058480972
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 755 log sequence number 179057737305
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 263 log sequence number 179058754929
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 387 log sequence number 179057406077
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 672 log sequence number 179058754929
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 264 log sequence number 179057808707
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1112 log sequence number 179057808707
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 390 log sequence number 179057887607
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 265 log sequence number 179057808751
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1177 log sequence number 179058755218
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 318 log sequence number 179057808751
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 266 log sequence number 179058481060
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 392 log sequence number 179058481060
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 518 log sequence number 179058461547
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 267 log sequence number 179058481104
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 319 log sequence number 179058481104
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1180 log sequence number 179056230062
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 268 log sequence number 179057808923
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 526 log sequence number 179058463127
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 269 log sequence number 179058481164
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 604 log sequence number 179058755476
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 649 log sequence number 179058481164
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 270 log sequence number 179057963028
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1162 log sequence number 179057963028
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 631 log sequence number 179058755889
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 271 log sequence number 179058481208
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1198 log sequence number 179058481208
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 596 log sequence number 179056564655
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 272 log sequence number 179058481462
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 702 log sequence number 179058481462
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 608 log sequence number 179058756192
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 273 log sequence number 179058481506
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 445 log sequence number 179055712083
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1098 log sequence number 179058481506
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 274 log sequence number 179058481550
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1212 log sequence number 179058481550
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 610 log sequence number 179058756461
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 275 log sequence number 179057809055
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 652 log sequence number 179057809055
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 601 log sequence number 179058466254
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 276 log sequence number 179058481594
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1188 log sequence number 179058481594
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 327 log sequence number 179057889357
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 277 log sequence number 179058481638
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1099 log sequence number 179058481638
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 519 log sequence number 179058168731
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 278 log sequence number 179057140242
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1094 log sequence number 179057140242
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 538 log sequence number 179058756761
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 279 log sequence number 179058481698
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 653 log sequence number 179058481698
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 425 log sequence number 179058170312
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 280 log sequence number 179058494439
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 513 log sequence number 179058494439
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1154 log sequence number 179057462441
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 281 log sequence number 179057963316
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1132 log sequence number 179057963316
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 402 log sequence number 179058170750
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 282 log sequence number 179057809143
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: 2019-04-01 04:46:52 7f6f0ad6e900 InnoDB: Error: page 1184 log sequence number 179057809143
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: is in the future! Current system log sequence number 178723624540.
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 04:46:52 sg2.domain.com mysqld[26047]: InnoDB: for more information.
    Apr 01 04:46:55 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 04:46:55 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 04:46:55 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 04:46:55 sg2.domain.com systemd[1]: mariadb.service failed.
     
  8. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    mysqlcheck --all-databases
    Code (Text):
    [05:11][[email protected] centminmod]# mysqlcheck --all-databases
    mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused") when trying to connect
     
  9. eva2000

    eva2000 Administrator Staff Member

    39,742
    8,765
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +13,486
    Local Time:
    7:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    running out of disk space has corrupted your mysql database data it seems. You probably need to do a forced innodb data recovery to do a full mysql database backup for all databases on server and then wipe/delete all mysql data from server /var/lib/mysql data directory and re-create that data directory and restore all the databases you backed up again.

    If you are unsure, you probably need to hire someone to do this for you.

    see instructions at https://community.centminmod.com/th...to-reset-your-mysql-database-directory.10001/ for one possible way of doing this though not 100% guarantee it will work depending on extent of database corruption you have now
     
  10. eva2000

    eva2000 Administrator Staff Member

    39,742
    8,765
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +13,486
    Local Time:
    7:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    because your databases are corrupted, MariaDB MySQL server is unable to start so mysqlcheck command won't work as Mariadb MySQL server isn't running.
     
  11. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    Thank you for taking the time to reply, @eva2000. Is there a way to retrieve the database backup?
     
  12. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    Sorry, I just read this.
     
  13. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    I tried this step: https://community.centminmod.com/th...to-reset-your-mysql-database-directory.10001/
    but immediately stopped at:

    Code (Text):
    mysqldump --all-databases > /home/mysqlbackup/alldatabases.sql


    How to mysqldump if Mariadb server down?
    Today is such a tiring day. :(

    Code (Text):
    [06:51][[email protected] ~]# mysqldump --all-databases > /home/mysqlbackup/alldatabases.sql
    mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused")" when trying to connect
    [06:57][[email protected] ~]#
    
     
  14. eva2000

    eva2000 Administrator Staff Member

    39,742
    8,765
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +13,486
    Local Time:
    7:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    see notes on using innodb force recover and then trying to start mysql server
     
  15. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    Hai @eva2000, thank you for your help.

    Does mysqldump really need to be successful? So if mysqldump failed like this, I can't continue the process? I am afraid to continue because the next step is to delete the database.

    Code (Text):
    [08:57][[email protected] mysql]# nano  /etc/my.cnf
    [08:57][[email protected] mysql]# mkdir -p /home/mysqlbackup
    [08:57][[email protected] mysql]# mysqldump --all-databases > /home/mysqlbackup/alldatabases.sql
    mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused")" when trying to connect
    [08:58][[email protected] mysql]# mysqladmin flush-tables
    mysqladmin: connect to server at 'localhost' failed
    error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused")'
    Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
    [08:58][[email protected] mysql]# sleep 240
    [09:02][[email protected] mysql]# mysqlstop
    Stopping mysql (via systemctl):                            [  OK  ]
    [09:03][[email protected] mysql]# cp -a /var/lib/mysql/ /var/lib/mysql.orig
    [09:03][[email protected] mysql]#


    I have added innodb_force_recovery = 1 on /etc/my.cnf
     
  16. eva2000

    eva2000 Administrator Staff Member

    39,742
    8,765
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +13,486
    Local Time:
    7:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    yes mysqldump needs to be successful to back up all your mysql database before you delete the data.

    did you start mysql server before mysqldump with /etc/my.cnf set with innodb_force_recovery = 1
     
  17. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    MariaDB Server won't start. I repeated each step several times. I don't know why Mariadb can't start.
    Code (Text):
    Starting mysql (via systemctl):  Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
                                                               [FAILED]
    [13:03][[email protected] ~]#


    systemctl status mariadb.service -l
    Code (Text):
    [13:10][[email protected] ~]# systemctl status mariadb.service -l
    ● mariadb.service - MariaDB 10.1.38 database server
       Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
               └─migrated-from-my.cnf-settings.conf, openfileslimit.conf, protecthome.conf
       Active: failed (Result: exit-code) since Mon 2019-04-01 13:10:27 UTC; 6min ago
         Docs: man:mysqld(8)
               https://mariadb.com/kb/en/library/systemd/
      Process: 9357 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
      Process: 9129 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
      Process: 9127 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
     Main PID: 9357 (code=exited, status=1/FAILURE)
       Status: "MariaDB server is down"
    
    Apr 01 13:10:22 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 13:10:23 sg2.domain.com mysqld[9357]: 2019-04-01 13:10:23 139905791641856 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 13:10:23 sg2.domain.com mysqld[9357]: 2019-04-01 13:10:23 139905791641856 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 9357 ...
    Apr 01 13:10:27 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 13:10:27 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 13:10:27 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 13:10:27 sg2.domain.com systemd[1]: mariadb.service failed.
    [13:17][[email protected] ~]#
    [CODEB]
     
  18. eva2000

    eva2000 Administrator Staff Member

    39,742
    8,765
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +13,486
    Local Time:
    7:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    output for
    Code (Text):
    journalctl -u mariadb --no-pager
     
  19. Hiperteks

    Hiperteks New Member

    14
    0
    1
    Oct 10, 2016
    Ratings:
    +0
    Local Time:
    4:22 PM
    11
    10
    Code (Text):
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 1135 log sequence number 179058754035
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 312 log sequence number 179058440530
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 256 log sequence number 179057808487
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 1131 log sequence number 179057808487
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 1203 log sequence number 179057734864
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 257 log sequence number 179058754261
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 393 log sequence number 179058440819
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 1136 log sequence number 179058754261
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:18 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 258 log sequence number 179058480798
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 670 log sequence number 179057308283
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 664 log sequence number 179058480798
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 259 log sequence number 179058754471
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 669 log sequence number 179058754471
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 633 log sequence number 179054836817
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 260 log sequence number 179057808619
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 333 log sequence number 179057329760
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 639 log sequence number 179057808619
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 261 log sequence number 179058754696
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 439 log sequence number 179055099138
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 1189 log sequence number 179058754696
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 262 log sequence number 179058480972
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 1190 log sequence number 179058480972
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 755 log sequence number 179057737305
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:18 7efd334e1900 InnoDB: Error: page 263 log sequence number 179058754929
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 387 log sequence number 179057406077
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 672 log sequence number 179058754929
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 264 log sequence number 179057808707
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1112 log sequence number 179057808707
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 390 log sequence number 179057887607
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 265 log sequence number 179057808751
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1177 log sequence number 179058755218
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 318 log sequence number 179057808751
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 266 log sequence number 179058481060
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 392 log sequence number 179058481060
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 518 log sequence number 179058461547
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 267 log sequence number 179058481104
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 319 log sequence number 179058481104
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1180 log sequence number 179056230062
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 268 log sequence number 179057808923
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 526 log sequence number 179058463127
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 269 log sequence number 179058481164
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 604 log sequence number 179058755476
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 649 log sequence number 179058481164
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 270 log sequence number 179057963028
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1162 log sequence number 179057963028
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 631 log sequence number 179058755889
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 271 log sequence number 179058481208
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1198 log sequence number 179058481208
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 596 log sequence number 179056564655
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 272 log sequence number 179058481462
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 702 log sequence number 179058481462
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 608 log sequence number 179058756192
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 273 log sequence number 179058481506
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 445 log sequence number 179055712083
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1098 log sequence number 179058481506
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 274 log sequence number 179058481550
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1212 log sequence number 179058481550
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 610 log sequence number 179058756461
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 275 log sequence number 179057809055
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 652 log sequence number 179057809055
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 601 log sequence number 179058466254
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 276 log sequence number 179058481594
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1188 log sequence number 179058481594
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 327 log sequence number 179057889357
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 277 log sequence number 179058481638
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1099 log sequence number 179058481638
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 519 log sequence number 179058168731
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 278 log sequence number 179057140242
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1094 log sequence number 179057140242
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 538 log sequence number 179058756761
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 279 log sequence number 179058481698
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 653 log sequence number 179058481698
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 425 log sequence number 179058170312
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 280 log sequence number 179058494439
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 513 log sequence number 179058494439
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1154 log sequence number 179057462441
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 281 log sequence number 179057963316
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1132 log sequence number 179057963316
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 402 log sequence number 179058170750
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 282 log sequence number 179057809143
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: 2019-04-01 11:16:19 7efd334e1900 InnoDB: Error: page 1184 log sequence number 179057809143
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: is in the future! Current system log sequence number 178723625312.
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: Your database may be corrupt or you may have copied the InnoDB
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: tablespace but not the InnoDB log files. See
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    Apr 01 11:16:19 sg2.domain.com mysqld[4868]: InnoDB: for more information.
    Apr 01 11:16:22 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 11:16:22 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 11:16:22 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 11:16:22 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 11:45:20 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 11:45:21 sg2.domain.com mysqld[5662]: 2019-04-01 11:45:21 140397864040704 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 11:45:21 sg2.domain.com mysqld[5662]: 2019-04-01 11:45:21 140397864040704 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 5662 ...
    Apr 01 11:45:37 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 11:45:37 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 11:45:37 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 11:45:37 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 12:14:09 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 12:14:10 sg2.domain.com mysqld[6228]: 2019-04-01 12:14:10 140571133217024 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 12:14:10 sg2.domain.com mysqld[6228]: 2019-04-01 12:14:10 140571133217024 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 6228 ...
    Apr 01 12:14:14 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 12:14:14 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 12:14:14 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 12:14:14 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 12:14:45 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 12:14:45 sg2.domain.com mysqld[6505]: 2019-04-01 12:14:45 139723412056320 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 12:14:45 sg2.domain.com mysqld[6505]: 2019-04-01 12:14:45 139723412056320 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 6505 ...
    Apr 01 12:14:49 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 12:14:49 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 12:14:49 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 12:14:49 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 12:18:03 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 12:18:03 sg2.domain.com mysqld[6811]: 2019-04-01 12:18:03 139789632010496 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 12:18:03 sg2.domain.com mysqld[6811]: 2019-04-01 12:18:03 139789632010496 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 6811 ...
    Apr 01 12:18:07 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 12:18:07 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 12:18:07 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 12:18:07 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 12:34:36 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 12:34:37 sg2.domain.com mysqld[7429]: 2019-04-01 12:34:37 139723509590272 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 12:34:37 sg2.domain.com mysqld[7429]: 2019-04-01 12:34:37 139723509590272 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 7429 ...
    Apr 01 12:34:41 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 12:34:41 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 12:34:41 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 12:34:41 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 12:53:54 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 12:53:54 sg2.domain.com mysqld[8038]: 2019-04-01 12:53:54 139861143828736 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 12:53:54 sg2.domain.com mysqld[8038]: 2019-04-01 12:53:54 139861143828736 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 8038 ...
    Apr 01 12:53:58 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 12:53:58 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 12:53:58 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 12:53:58 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 12:58:02 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 12:58:03 sg2.domain.com mysqld[8359]: 2019-04-01 12:58:03 139754407459072 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 12:58:03 sg2.domain.com mysqld[8359]: 2019-04-01 12:58:03 139754407459072 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 8359 ...
    Apr 01 12:58:06 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 12:58:06 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 12:58:06 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 12:58:06 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 13:03:06 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 13:03:07 sg2.domain.com mysqld[8694]: 2019-04-01 13:03:07 140328711383296 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 13:03:07 sg2.domain.com mysqld[8694]: 2019-04-01 13:03:07 140328711383296 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 8694 ...
    Apr 01 13:03:10 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 13:03:10 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 13:03:10 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 13:03:10 sg2.domain.com systemd[1]: mariadb.service failed.
    Apr 01 13:10:22 sg2.domain.com systemd[1]: Starting MariaDB 10.1.38 database server...
    Apr 01 13:10:23 sg2.domain.com mysqld[9357]: 2019-04-01 13:10:23 139905791641856 [Note] Using unique option prefix 'ignore-db-dir' is error-prone and can break in the future. Please use the full name 'ignore_db_dirs' instead.
    Apr 01 13:10:23 sg2.domain.com mysqld[9357]: 2019-04-01 13:10:23 139905791641856 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 9357 ...
    Apr 01 13:10:27 sg2.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Apr 01 13:10:27 sg2.domain.com systemd[1]: Failed to start MariaDB 10.1.38 database server.
    Apr 01 13:10:27 sg2.domain.com systemd[1]: Unit mariadb.service entered failed state.
    Apr 01 13:10:27 sg2.domain.com systemd[1]: mariadb.service failed.
    [00:59][[email protected] ~]#
     
  20. eva2000

    eva2000 Administrator Staff Member

    39,742
    8,765
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +13,486
    Local Time:
    7:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
..