Bug #520
Problem with mysql 64bit
| Status: | Closed | Start date: | 05/13/2011 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: |  Danny Terweij |
% Done: | 100% |
|
| Category: | Thirdparty & RPM Packages | Spent time: | 4.60 hours | |
| Target version: | Packages | |||
| Resolution: | No Feedback | Operating System: | ||
| Reproduceable: | Architecture: |
Description
I found mysql-5.0.*92*-lxcenter.1.x86_64.rpm and zend package from lxcenter repo.
New install for centos 5.5 and 5.6 always problems. It's include problem for upgrade to centos 5.6
Solution:
1. Use mysql from centos or version mysql-5.0.*91*-lxcenter.1.x86_64.rpm from lxcenter
2. Rezip hypervm-current.zip without zend-encoder for every php files (can be taken from svn)
I will be make new thread for this 'temporary' solution in the lxcenter forum.
History
Updated by Danny Terweij about 1 year ago
Explain exact what the problem is. I can not guess what your problem is :)
What happens, what happens not.
Show logfiles, screenshots etc etc.
Updated by Mustafa Ramadhan about 1 year ago
I am wrong about zend encoder but mysql.
Please read http://forum.lxcenter.org/index.php?t=msg&th=16008
Yes, the problem is Mysql version mysql-5.0.92-lxcenter.1.x86_64.rpm. No for mysql-5.0.91-lxcenter.1.x86_64.rpm.
For me, more prepare to use mysql fro CentOS.
Updated by Danny Terweij about 1 year ago
- Subject changed from Problem with mysql and zend from lxcenter repo to Problem with mysql 64bit
I did read the forum message.
Its not related to "update" processes.
It might be only the case for a new Kloxo installation on a 64Bit system. 64Bit is still not yet supported.
And the problem is not described in detail. Just a line with some connect error is not enough.
More details are needed.
rpm -qa | grep mysql, try to (re)start mysql manualy. Look for logfiles and watch for odd things and report it.
All my 64Bit production servers with HyperVM 64bit is running .92 fine. It installed .92 fine. No errors.
Updated by Mustafa Ramadhan about 1 year ago
I hope this is not 'general' and only 'special' issue for my case. This is strange for me, all my 'testing' server with HyperVM always problems with .92.
BTW, where I can find log error for mysql?
Updated by Walter Secco 12 months ago
- Assignee set to Danny Terweij
- Priority changed from Normal to Urgent
There are 3 problems today:
1) The install script is not detecting if MySQL is already installed. It should and instruct the user to remove it along with the databases. If you do it manually today, HyperVM installs just fine (using the default root user and no pass unless provided - but no alerts). I can update the install scripts using Kloxo's as a model but I need Danny to zip the new program-install.
2) Looking at mysql.spec, it does not Obsoletes relevant CentOS/RHEL MySQL packages. This is required otherwise yum will keep old MySQL 5.0.77 and libs and try to install LxCenter provided MySQL packages in the same path causing file conflicts. A correct Obsoletes flag will cause yum to remove the old version(s) prior to unpacking the new 5.0.9x versions. This gets worse with x86_64 as both 32 and 64 bit versions of MySQL 5.0.77 are usually installed by default which results in this:
file /etc/my.cnf from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/share/mysql/czech/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/share/mysql/danish/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/share/mysql/dutch/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/share/mysql/english/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
...
file /etc/my.cnf from install of mysql-5.0.77-4.el5_6.6.x86_64 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/lib64/mysql/libmysqlclient.so.15.0.0 from install of mysql-5.0.77-4.el5_6.6.x86_64 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/lib64/mysql/libmysqlclient_r.so.15.0.0 from install of mysql-5.0.77-4.el5_6.6.x86_64 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/share/mysql/czech/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.x86_64 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/share/mysql/danish/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.x86_64 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
file /usr/share/mysql/dutch/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.x86_64 conflicts with file from package mysql-libs-5.0.92-lxcenter.1.x86_64
I don't have the resources to make and test these changes.
3) lxlabs.repo generated in RHEL 5.6 nodes will add the non-existent url http://download.lxlabs.com/download/update/rhel-5.6/ . A symlink must be created urgently. Current and new HyperVM users have to edit lxlabs.repo, replace rhel-5.6 by centos-5 and "chattr +i" it. This is reported to work.
This sums up the problems reported to this date and I'm raising the priority specially because of item 3. This should be trivial to fix but my hands are tied. So I'm assigning Danny for this as he has access to the download server to make these changes.
If we do at least 1 and 3, we will fix 99.9% of the issues with the install process. But there are still many HyperVM users running CentOS/RHEL provided MySQL 5.0.7x withholding updates because of the reports in the forums of problems with LxCenter's MySQL packages. This is easily fixed but the forums are littered with "solutions" I wouldn't give to my worst enemy. It should be a high priority before people break their servers beyond repair.
@Mustafa Ramadhan
I have to ask you to stop advising people to download HyperVM SVN code. Think of "trunk" code as "pre-alpha" code. The code there is untested and incomplete. IT WILL break peoples server and they will blame you (and rightfully so). Understand we are doing the inverse here. Stable, production quality will be merged to a 2.1.x branch which does not exist today. Only then it will be tagged for point or maintenance release (2.1.0/2.1.1/etc).
Until these are available, this is very bad advice. If all we had to do was zip trunk code and release we would have already done that. It's not that simple.
Updated by Danny Terweij 12 months ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
rhel-5.6 symlink created.
Updated by Danny Terweij 12 months ago
- % Done changed from 10 to 60
Rebuilded mysql-5.0.92 release lxcenter.2 and straight into the update repository.
This should obsolete mysql-5.0.77-*.i386 on 64Bit systems. I can not test it, please give feedback if this works.
It installed fine without the 5.0.77 conficts problem.
Updated by Mustafa Ramadhan 12 months ago
@Walter,
I will more careful about it.
Yes, the problem is related to mysql-5.0.92 only. Downgrade to mysql-5.0.91 not enough. Read http://forum.lxcenter.org/index.php?t=msg&th=16008 for my solution. I am more prefered to use mysql from centos repo until this time mostly because less dependencies if try 'yum remove' and then 'yum install'.
@All,
My last test (read http://forum.lxcenter.org/index.php?t=msg&th=16075) with still the same problem with mysql-5.0.92. Use mysql from centos repo is fine.
Updated by Danny Terweij 12 months ago
lxcenter.2 also fails. As i did not get feedback...
I am almost ready with a lxcenter.4. I completely dropped the 5.0.92 src and using 5.0.91-lxcenter.1 src rpm with a update to 5.0.92.
Added: Obsolete mysql <= 5.0.77 to the spec and mysql-libs package are perhaps not required anymore...
It's still building right now.
Updated by Mustafa Ramadhan 12 months ago
Danny Terweij wrote:
lxcenter.2 also fails. As i did not get feedback... I am almost ready with a lxcenter.4. I completely dropped the 5.0.92 src and using 5.0.91-lxcenter.1 src rpm with a update to 5.0.92. Added: Obsolete mysql <= 5.0.77 to the spec and mysql-libs package are perhaps not required anymore... It's still building right now.
In my 'testing' server, I try:
1. remove mysql (install from centos repo) with "yum remove mysql mysql-server", then
2. install mysql (install from lxcenter-test) with "yum install mysql mysql-server"
Nothing found error.
Updated by Mustafa Ramadhan 12 months ago
I found different thing.
Uninstall lxphp and install again which lxphp have dependencies to mysqlclient15-5.0.92.lxcenter.1 and gdbm (taken from centos). It's normal?
Updated by Mustafa Ramadhan 12 months ago
package 'gdbm' very dangerous.
If I try 'yum remove gdbm' then will be also remove so many dependencies/packages (until 260; including yum, witch, wget, etc)
Updated by Mustafa Ramadhan 12 months ago
package lxphp still need mysqlclient15 (as dependencies). So, mysqlclient15 importance?.
This is as same as http://project.lxcenter.org/issues/525
Updated by Danny Terweij 12 months ago
Mustafa Ramadhan wrote:
In my 'testing' server, I try:
1. remove mysql (install from centos repo) with "yum remove mysql mysql-server", then 2. install mysql (install from lxcenter-test) with "yum install mysql mysql-server"
Nothing found error.
That is not the case. That will install/update fine.
CentOS with a base install and on systems with mysql (already) installed on 64Bit systems do have:
mysql-5.0.77 .i386 AND x86_64 packages.
You have to test with those packages against the .lxcenter.x packages.
lxcenter.4 also failed. the Obsolete line works, .i386 is going to be replaced but the x86_64 does still warn about conflicted files. It just need to overwrite the damn files :)
Updated by Danny Terweij 12 months ago
Mustafa Ramadhan wrote:
package 'gdbm' very dangerous.
If I try 'yum remove gdbm' then will be also remove so many dependencies/packages (until 260; including yum, witch, wget, etc)
This package is not dangerous. Its the *G*NU *D*ata*B*ase *M*anager.
Updated by Danny Terweij 12 months ago
Mustafa Ramadhan wrote:
package lxphp still need mysqlclient15 (as dependencies). So, mysqlclient15 importance?.
This is as same as http://project.lxcenter.org/issues/525
Yes lxphp is 32Bit on 64bit systems. It needs mysqlclient 32bit to get the Kloxo GUI connected to the mysql database.
Watch the packages and the architectures when you do something. Its just logical :)
Updated by Mustafa Ramadhan 12 months ago
Danny Terweij wrote:
Mustafa Ramadhan wrote:
package 'gdbm' very dangerous.
If I try 'yum remove gdbm' then will be also remove so many dependencies/packages (until 260; including yum, witch, wget, etc)
This package is not dangerous. Its the *G*NU *D*ata*B*ase *M*anager.
It's ok because by default exist on centos system
Updated by Mustafa Ramadhan 12 months ago
Danny Terweij wrote:
Mustafa Ramadhan wrote:
package lxphp still need mysqlclient15 (as dependencies). So, mysqlclient15 importance?.
This is as same as http://project.lxcenter.org/issues/525
Yes lxphp is 32Bit on 64bit systems. It needs mysqlclient 32bit to get the Kloxo GUI connected to the mysql database.
Watch the packages and the architectures when you do something. Its just logical :)
With mysql and mysql-server from centos repo (still include mysql 32bit beside 64bit), mysqlclient* doesn't needed and hypervm still running well. It's seems like my testing ( http://forum.lxcenter.org/index.php?t=msg&th=16075 ).
This is what I mean mysqlclient important? :)
Updated by Danny Terweij 12 months ago
You still dont understand it.
64Bit OS:
When installed or build (vm, and mysql is installed you have:
- mysql 5.0.77 32bit
- mysql 5.0.77 64bit
Both installed (Why is that!?!? someone can give me that answer?)
lxphp is 32bit and uses mysql 5.0.77 32bit mysql.so extention.
HyperVM GUI uses 32bit package.
php is 64bit and uses the 64bit mysql.so extention (Serves web content to the public).
CentOS does not have a mysql-libs or mysqlclient package (that provides mysql.so)
I do have a HyperVM 64Bit OS, with 5.0.92.lxcenter. 64 bit package installed (removed 5.0.77 by hand with rpm -e package --nodeps). But then the communication between HyperVM GUI and MySQL is lost. So i needed mysqlclient15 (thats a 32bit package) to provide a 32bit mysql.so extention.
Thats why mysqlclient10/15 exists in Repo.
It is all working well, but it is a manual action. Now to get it automaticly...., thats the problem we have.
This is all you have to know Mustafa. So yes mysqlclient can be important for systems that did do the same as i did (manual action).
I hope centos 6 comes out fast ;-)
Updated by Mustafa Ramadhan 12 months ago
I have different experience. Since appear 5.0.92.lxcenter.2 problem, my 'solution' is:
1. add "exclude=mysql*" in lxlabs.repo (for hypervm) and lxcenter.repo (for kloxo)
2. for repair existing system, run "yum downgrade mysql mysal-server" (mysql 5.0.77 32bit and 64bit will be installed). Then "yum remove mysqlclient*" (because nothing dependencies for other packages)
3. for new install, just install hypervm as usual. Then "yum remove mysqlclient*" (if exist)
Then HyperVM not running?. No, HyperVM running well as usual.
Use from other repo (I try from CentALT which serve 5.0.92 version) seems like lxcenter repo problem. So, my latest proof is my testing (see above link).
Yes I know, mysql 5.0.92 from lxcenter need mysqlclient (because 'by design'). Mysql 5.0.77 from centos doesn't need.
I don't have other solutions except use mysql from centos at this time.
Updated by Mustafa Ramadhan 12 months ago
Upgrade from mysql 5.0.77 to mysql 5.1.x (from utterramblings/jason repo) seems like ok.
Updated by Danny Terweij 7 months ago
- Target version set to 2.1.x
Updated by Danny Terweij 5 months ago
- Category set to Thirdparty & RPM Packages
- Target version changed from 2.1.x to Packages
Updated by Danny Terweij 3 months ago
- Status changed from In Progress to Closed
- % Done changed from 60 to 100
- Resolution set to No Feedback
I think this is all solved with the .95 from C5-Base updates for Mustafa.
Closed. No feedback and auto-fixed by new upstream packages.