iman4web
April 7th, 2019, 14:27
از تو WHM CENTOS 6.7میخوام mysql رو از ورژن 5.6.41 به ورژن MySQL 5.7 آپدیت کنم. ولی وسط کار این خطا میاد
چی کار باید بکنم ؟
Starting process with log file at /var/cpanel/logs/mysql_upgrade.20190407-141846/unattended_upgrade.log
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MySQL enables "strict mode" by default as of version 5.7. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MySQL are compatible before upgrading. More information about strict mode is availablehere.
Beginning “MySQL 5.7” upgrade...
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MySQL enables "strict mode" by default as of version 5.7. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MySQL are compatible before upgrading. More information about strict mode is availablehere.
Obtained version information from system.
Ensuring the “Mysql57” repository is available and working.
checkyum version 22.3
Ensuring that the package “coreutils” is available.
Restarting mysql service.
Waiting for “mysql” to restart …ionice: cannot parse number 'none'
…waiting for “mysql” to initialize ………finished.
Service Status
mysql (/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=server.webhostdeveloper.com.err --open-files-limit=16000 --pid-file=/var/lib/mysql/server.webhostdeveloper.com.pid) is running as mysql with PID 19220 (pidfile+/proc check method).
Startup Log
Starting MySQL.[ OK ]
Log Messages
2019-04-07 14:19:11 19220 [Note] /usr/sbin/mysqld: ready for connections.
2019-04-07 14:19:10 2338 [Note] /usr/sbin/mysqld: Shutdown complete
2019-04-07 14:19:09 2338 [Note] /usr/sbin/mysqld: Normal shutdown
2019-04-02 13:39:15 2338 [Note] /usr/sbin/mysqld: ready for connections.
2019-04-02 13:38:22 7470 [Note] /usr/sbin/mysqld: Shutdown complete
mysql restarted successfully.
The system was not able to ensure the availability of the “coreutils” package: (XID 6rhkey) “/usr/bin/yum” reported error code “1” when it ended: http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "Couldn't resolve host 'apt.sw.be'"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: rpmforge. Please verify its path and try again
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MySQL enables "strict mode" by default as of version 5.7. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MySQL are compatible before upgrading. More information about strict mode is availablehere.
چی کار باید بکنم ؟
Starting process with log file at /var/cpanel/logs/mysql_upgrade.20190407-141846/unattended_upgrade.log
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MySQL enables "strict mode" by default as of version 5.7. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MySQL are compatible before upgrading. More information about strict mode is availablehere.
Beginning “MySQL 5.7” upgrade...
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MySQL enables "strict mode" by default as of version 5.7. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MySQL are compatible before upgrading. More information about strict mode is availablehere.
Obtained version information from system.
Ensuring the “Mysql57” repository is available and working.
checkyum version 22.3
Ensuring that the package “coreutils” is available.
Restarting mysql service.
Waiting for “mysql” to restart …ionice: cannot parse number 'none'
…waiting for “mysql” to initialize ………finished.
Service Status
mysql (/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=server.webhostdeveloper.com.err --open-files-limit=16000 --pid-file=/var/lib/mysql/server.webhostdeveloper.com.pid) is running as mysql with PID 19220 (pidfile+/proc check method).
Startup Log
Starting MySQL.[ OK ]
Log Messages
2019-04-07 14:19:11 19220 [Note] /usr/sbin/mysqld: ready for connections.
2019-04-07 14:19:10 2338 [Note] /usr/sbin/mysqld: Shutdown complete
2019-04-07 14:19:09 2338 [Note] /usr/sbin/mysqld: Normal shutdown
2019-04-02 13:39:15 2338 [Note] /usr/sbin/mysqld: ready for connections.
2019-04-02 13:38:22 7470 [Note] /usr/sbin/mysqld: Shutdown complete
mysql restarted successfully.
The system was not able to ensure the availability of the “coreutils” package: (XID 6rhkey) “/usr/bin/yum” reported error code “1” when it ended: http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "Couldn't resolve host 'apt.sw.be'"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: rpmforge. Please verify its path and try again
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MySQL enables "strict mode" by default as of version 5.7. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MySQL are compatible before upgrading. More information about strict mode is availablehere.