[atomic] Mysql 5.1.47
-
- Atomicorp Staff - Site Admin
- Posts: 8355
- Joined: Wed Dec 31, 1969 8:00 pm
- Location: earth
- Contact:
[atomic] Mysql 5.1.47
From here on out the [atomic] channel will be standardized on Mysql 5.1, starting with version 5.1.47.
Changelog from 5.0 to 5.1 is fairly significant and too lengthy to post here. Releases following this will cover just the differences from the previous versions.
Changelog from 5.0 to 5.1 is fairly significant and too lengthy to post here. Releases following this will cover just the differences from the previous versions.
Re: [atomic] Mysql 5.1.47
One important note (especially if you have used mysqltuner to tweak your my.cnf)
The Berkley engine was removed in 5.1. This engine used to be available in 5.0 and was enabled by default. To save resources, mysqltuner would recommend you add the following to my.cnf
You MUST comment this line out or mysql 5.1 will fail to start.
In addition, after mysql is running again, you must run the following
The Berkley engine was removed in 5.1. This engine used to be available in 5.0 and was enabled by default. To save resources, mysqltuner would recommend you add the following to my.cnf
Code: Select all
skip-bdb
In addition, after mysql is running again, you must run the following
Code: Select all
mysql_upgrade -u <mysql root user> -p
"Its not a mac. I run linux... I'm actually cool." - scott
Re: [atomic] Mysql 5.1.47
I have the same experience as highland. Remove skip-bdb and run the update.
Re: [atomic] Mysql 5.1.47
I have updated mysql to the latest 5.1.47...
However, plesk has warning
Should I ignore this?
Also, the instructions from Highland:
One more thing...the update warning said my.cnf has been saved as my.cnf.rpmnew....should I replace the older my.cnf with the new version. I did comment out the "skip-bdb" before the update...
However, plesk has warning
Code: Select all
Your PHP MySQL library version 5.0.90 differs from your MySQL server version 5.1.47. This may cause unpredictable behavior.
Also, the instructions from Highland:
Is the mysql root user "admin", or as shown in "top" interface as user "mysql", or am I to run the command as exactly spelled out without substitution of another user?mysql_upgrade -u <mysql root user> -p
One more thing...the update warning said my.cnf has been saved as my.cnf.rpmnew....should I replace the older my.cnf with the new version. I did comment out the "skip-bdb" before the update...
Re: [atomic] Mysql 5.1.47
You should use "admin" for mysql_upgrade if you are running a standard Plesk installation.
I don't think you need to copy the rpmnew-version to your default my.conf. You could do it, if you haven't made any alternations to your my.conf. If you donät get any errors, I'd stick to the one you've got running right now.
I don't think you need to copy the rpmnew-version to your default my.conf. You could do it, if you haven't made any alternations to your my.conf. If you donät get any errors, I'd stick to the one you've got running right now.
Re: [atomic] Mysql 5.1.47
Yes. You would probably break Plesk trying to update the client. There's no harm in the client different for the most part.Your PHP MySQL library version 5.0.90 differs from your MySQL server version 5.1.47. Should I ignore this?
For Plesk users, use "admin" as your user and your Plesk admin password as the password. If you don't have Plesk installed, you would use root.Is the mysql root user "admin", or as shown in "top" interface as user "mysql", or am I to run the command as exactly spelled out without substitution of another user?
"Its not a mac. I run linux... I'm actually cool." - scott
Re: [atomic] Mysql 5.1.47
Thanks for the clarification....
I ran the upgrade command, then did some repairs on the tables, and some optimizing, reran the command several times till everything came together, but there is one repeating error:
I ran the upgrade command, then did some repairs on the tables, and some optimizing, reran the command several times till everything came together, but there is one repeating error:
The file /var/log/mysql-slow.log does exist...I don't know why this error.ERROR 29 (HY000) at line 334: File '/var/log/mysql-slow.log' not found (Errcode: 13)
Re: [atomic] Mysql 5.1.47
I had the same error. Got rid of it by doing the following:
Code: Select all
# log_slow_queries=/var/log/mysqld.slow.log
slow_query_log=1
Re: [atomic] Mysql 5.1.47
Or you can do the following
Code: Select all
#touch /var/log/mysqld.slow.log
#chown mysql:mysql /var/log/mysqld.slow.log
"Its not a mac. I run linux... I'm actually cool." - scott
-
- Forum User
- Posts: 57
- Joined: Sun Sep 06, 2009 5:35 am
Re: [atomic] Mysql 5.1.47
This last update is causing a lot of problems in our server.
Whenever we try to use PhpMyAdmin or Plesk's built-in add database user feature, we get an error from the server telling that "table mysql.server does not exist.
We are running Plesk 8.6.
Whenever we try to use PhpMyAdmin or Plesk's built-in add database user feature, we get an error from the server telling that "table mysql.server does not exist.
We are running Plesk 8.6.
Re: [atomic] Mysql 5.1.47
Got mine going with no issues.
I followed the tips above and ran yum.
I did get some warnings about tables needing repair so I ran: mysqlcheck -u <mysql username> -p --auto-repair --check --optimize --all-databases at the end.
I followed the tips above and ran yum.
I did get some warnings about tables needing repair so I ran: mysqlcheck -u <mysql username> -p --auto-repair --check --optimize --all-databases at the end.
Re: [atomic] Mysql 5.1.47
Sounds like you didnät run the upgrade command after installation...magneticat wrote:This last update is causing a lot of problems in our server.
Whenever we try to use PhpMyAdmin or Plesk's built-in add database user feature, we get an error from the server telling that "table mysql.server does not exist.
We are running Plesk 8.6.
-
- Forum User
- Posts: 57
- Joined: Sun Sep 06, 2009 5:35 am
Re: [atomic] Mysql 5.1.47
I did, but apparently I had to run it twice and then it worked.
The second time, with the force option.
The second time, with the force option.
Re: [atomic] Mysql 5.1.47
@magneticat...please tell me how you used the force option and the actual command lines used...I cannot get this upgrade command to work...got all the tables in order , but still getting the error at the end...
Re: [atomic] Mysql 5.1.47
So i get this correct i have the following updates available below as of this morning.
Is it as simple as following the below steps for Plesk 9.5 from what i gather or am i missing something and setting up for a failure?
1. yum upgrade and install all the updates.
2. after updates installed then run "mysql_upgrade -u <admin> -p <password>"
3. mysqlcheck -u <admin> -p <password> --auto-repair --check --optimize --all-databases
Code: Select all
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package glibc.i686 0:2.5-49.el5_5.2 set to be updated
---> Package glibc-common.i386 0:2.5-49.el5_5.2 set to be updated
---> Package glibc-devel.i386 0:2.5-49.el5_5.2 set to be updated
---> Package glibc-headers.i386 0:2.5-49.el5_5.2 set to be updated
---> Package mysql.i386 0:5.1.47-1.el5.art set to be updated
--> Processing Dependency: libmysqlclient.so.15 for package: psa-mail-driver-common
--> Processing Dependency: libmysqlclient.so.15 for package: psa-backup-manager
--> Processing Dependency: libmysqlclient.so.15 for package: ossec-hids-server
--> Processing Dependency: libmysqlclient.so.15 for package: psa-mail-qc-driver
--> Processing Dependency: libmysqlclient.so.15 for package: ruby-mysql
--> Processing Dependency: libmysqlclient.so.15 for package: psa
--> Processing Dependency: libmysqlclient.so.15 for package: asl-php-mysql
--> Processing Dependency: libmysqlclient.so.15 for package: psa-hotfix3-9.2.3
--> Processing Dependency: libmysqlclient.so.15 for package: roadsend-php-libs
--> Processing Dependency: libmysqlclient.so.15 for package: perl-DBD-MySQL
--> Processing Dependency: libmysqlclient.so.15 for package: psa-spamassassin
--> Processing Dependency: libmysqlclient.so.15 for package: php-mysql
--> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15) for package: perl-DBD-MySQL
--> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15) for package: asl-php-mysql
--> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15) for package: ruby-mysql
--> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15) for package: php-mysql
---> Package mysql-libs.i386 0:5.1.47-1.el5.art set to be updated
---> Package mysql-server.i386 0:5.1.47-1.el5.art set to be updated
---> Package nscd.i386 0:2.5-49.el5_5.2 set to be updated
---> Package perl.i386 4:5.8.8-32.el5_5.1 set to be updated
---> Package perl-suidperl.i386 4:5.8.8-32.el5_5.1 set to be updated
---> Package strace.i386 0:4.5.18-5.el5_5.5 set to be updated
---> Package sudo.i386 0:1.7.2p1-7.el5_5 set to be updated
--> Running transaction check
---> Package mysqlclient15.i386 0:5.0.90-1.el5.art set to be updated
addons/filelists | 195 B 00:00
asl-2.0/filelists_db | 1.3 MB 00:03
atomic/filelists_db | 440 kB 00:00
base/filelists_db | 3.4 MB 00:16
extras/filelists_db | 195 kB 00:00
plesk/filelists | 901 kB 00:03
updates/filelists_db | 909 kB 00:02
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
glibc i686 2.5-49.el5_5.2 updates 5.3 M
glibc-common i386 2.5-49.el5_5.2 updates 16 M
glibc-devel i386 2.5-49.el5_5.2 updates 2.0 M
glibc-headers i386 2.5-49.el5_5.2 updates 602 k
mysql i386 5.1.47-1.el5.art atomic 4.1 M
mysql-libs i386 5.1.47-1.el5.art atomic 2.1 M
mysql-server i386 5.1.47-1.el5.art atomic 11 M
nscd i386 2.5-49.el5_5.2 updates 165 k
perl i386 4:5.8.8-32.el5_5.1 updates 12 M
perl-suidperl i386 4:5.8.8-32.el5_5.1 updates 62 k
strace i386 4.5.18-5.el5_5.5 updates 172 k
sudo i386 1.7.2p1-7.el5_5 updates 230 k
Installing for dependencies:
mysqlclient15 i386 5.0.90-1.el5.art atomic 1.4 M
Transaction Summary
================================================================================
Install 1 Package(s)
Upgrade 12 Package(s)
1. yum upgrade and install all the updates.
2. after updates installed then run "mysql_upgrade -u <admin> -p <password>"
3. mysqlcheck -u <admin> -p <password> --auto-repair --check --optimize --all-databases
James Nascimento
Chief Information Officer
East Commerce Solutions, Inc.
22 Morris Lane
East Providence, RI 02914
Ph. 800-527-5395 x263
Fax. 888-999-5891
Chief Information Officer
East Commerce Solutions, Inc.
22 Morris Lane
East Providence, RI 02914
Ph. 800-527-5395 x263
Fax. 888-999-5891