Zenoss core installation compatibility issue with MySQL - mysql

I am facing an issue between the Zenoss core installation and MySQL rpms.
The Zenoss core installation won't complete, complaining about mysql-client and mysql-shared versions, even though I have newer versions installed. As suggested in this Quest/answer ,
I also tried to install a 5.5.41 client package but it did not change anything. Here's the situation:
[root#bstfe1032 Zenoss]# yum -y --nogpgcheck localinstall zenoss-4.2.0.el6.x86_64.rpm
[...]
--> Finished Dependency Resolution
Error: Package: zenoss-4.2.0-1586.el6.x86_64 (/zenoss-4.2.0.el6.x86_64)
Requires: mysql-client >= 5.5.13
Error: Package: zenoss-4.2.0-1586.el6.x86_64 (/zenoss-4.2.0.el6.x86_64)
Requires: mysql-shared >= 5.5.13
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root#bstfe1032 Zenoss]# rpm -qa|grep -i mysql
MySQL-client-5.6.22-1.el6.x86_64
MySQL-server-5.6.22-1.el6.x86_64
MySQL-shared-5.6.22-1.el6.x86_64
The Zenoss core install doc points to MySQL packages from mysql.org and this is where I got them.
Any idea of what I should try next ? I am using CentOS 6, this is a testbed and not a production machine because I wanted to give Zenoss core a test drive.

You are mixing "old" packages (zenoss-4.2.0) with too new one (MySQL 5.6) and it's not probably handled correctly in Zenoss core packages.
The best option for you is to use autodeploy script - https://github.com/zenoss/core-autodeploy/blob/4.2.5/core-autodeploy.sh
It will download last Zenoss packages from http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/
and MySQL packages from ftp://mirror.anl.gov/pub/mysql/Downloads/MySQL-5.5/
See http://wiki.zenoss.org/Install_Zenoss for more information.

Related

How to Install cloudstack on RHEL 7.4

I'm trying to install CloudStack managment on RHEL 7.4 Server by following:
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.11/management-server/index.html
Issue 1:
/etc/yum.repos.d/cloudstack.repo
The variable $releasever is translated to 7Server which results in url
baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.11/
Is translated to:
http://cloudstack.apt-get.eu/centos/7Server/4.11/
Which does not exists.
I had to modified it to:
http://cloudstack.apt-get.eu/centos/7/4.11/
There is also
http://cloudstack.apt-get.eu/rhel/7/4.11/
I don’t know which of the two is required.
Issue 2:
When doing:
sudo yum install cloudstack-management
Error: Package: cloudstack-management-4.11.0.0-1.el7.centos.x86_64 (cloudstack)
Requires: apache-commons-daemon-jsvc
I was not able to install this missing package.
Issue 3:
sudo yum install mysql-server
results in:
No package mysql-server available.
I understand that RHEL 7.4 comes with MariaDB and not MySql. I don’t have instructions on how to configure the MariaDB for CloudStack.
Any help will be appreciated.
As you are using redhat, you need to use below repo:
http://cloudstack.apt-get.eu/rhel/7/4.11/
To get apache-commons-daemon-jsvc, you need to enable base repo as this package is provided by redhat.
You can install mariaDB, instead of mysql and then follow exact steps from documentation.
Only difference will be while restarting/starting/enabling service use mariadb instead of mysql.

Can I bypass installing glibc.i686 as a dependency when I already have the x86_64 version?

I'm trying to install Atom from the official RPM provided. libXss.so.1 is a dependency and tries to install the 32-bit version of glibc when I already have the 64-bit version. It then conflicts with the 2.23.1-7 older version of glibc that I already have.
So where do I go from here? I'm guessing that there is a bugfix somewhere in libXss. libXss tries to install i686 arch for all it's dependencies.
I'm using Fedora 24 x86_64
Terminal Output
sudo rpm -ivh atom.x86_64.rpm
error: Failed dependencies:
libXss.so.1 is needed by atom-1.13.0-0.1.x86_64
sudo dnf install libXss.so.1
Error: Transaction check error:
file /usr/share/doc/glibc/NEWS from install of glibc-2.23.1-11.fc24.i686 conflicts with file from package glibc-2.23.1-7.fc24.x86_64
sudo dnf install glibc-2.23.1-11.fc.24.x86_64
Package glibc-2.23.1-11.fc24.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
Secondary/Unimportant Question
Do I need glibc-2.23.1-7.fc24.x86_64 when I already have glibc-2.23.1-11.fc24.x86_64? I see that I have both installed yet I have no conflict problems.
edit
I gave up and decided to install from the copr repo
sudo dnf copr enable mosquito/atom
sudo dnf install atom
Error: Transaction check error:
file /usr/lib64/libkadm5clnt_mit.so.10.0 from install of libkadm5-1.14.4-4.fc24.x86_64 conflicts with file from package krb5-libs-1.14.1-6.fc24.x86_64
file /usr/lib64/libkadm5srv_mit.so.10.0 from install of libkadm5-1.14.4-4.fc24.x86_64 conflicts with file from package krb5-libs-1.14.1-6.fc24.x86_64
What is going on?
Can I bypass installing glibc.i686 as a dependency when I already have the x86_64 version?
Not if you need to install 32-bit software — you'll need the 32-bit libs for that. 64-bit libraries aren't supersets of the 32-bit ones.
I'm trying to install Atom from the official RPM provided. libXss.so.1 is a dependency and tries to install the 32-bit version of glibc when I already have the 64-bit version. It then conflicts with the 2.23.1-7 older version of glibc that I already have.
This is a frequent problem. Installing 32-bit versions of packages without updating to the latest versions of the main 64-bit packages is not supported. Upgrade first, then install.
Do I need glibc-2.23.1-7.fc24.x86_64 when I already have glibc-2.23.1-11.fc24.x86_64? I see that I have both installed yet I have no conflict problems.
This can happen if there's an interrupted upgrade transaction. You should be able to dnf remove glibc-2.23.1-7.fc24.x86_64 safely. If that gives you errors, time to stop and make sure nothing else is wrong. Or, you can really just ignore it — next time a new glibc update comes out, it should replace both.
I gave up and decided to install from the copr repo
The errors you see here are actually the same root problem as trying to install 32-bit packages without updating first. RPMs can share files, as long as they are completely identical. That's true in matched versions of the various kerberos packages, but not true if there's a mismatch, and the dependency information doesn't handle this. So, again upgrade to latest packages before installing new ones.

error in installing ruby-devel using yum?

Hello I try to install ruby gem json but it gives following error
`Building native extensions. This could take a while...
ERROR: Error installing json:
ERROR: Failed to build gem native extension.
mkmf.rb can't find header files for ruby at /usr/share/include/ruby.h
Gem files will remain installed in /home/jenkins/.gem/ruby/gems/json-2.0.2 for inspection.
Results logged to /home/jenkins/.gem/ruby/gems/json-2.0.2/ext/json/ext/generator/gem_make.out`
I looked up similar post and was directed to install ruby-devel. But thats also given me a hard time.
yum install ruby-devel
Loaded plugins: addreleaserel, priorities, product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package ruby-devel.x86_64 0:2.0.0.598-25.el7_1 will be installed
--> Processing Dependency: ruby(x86-64) = 2.0.0.598-25.el7_1 for package: ruby-devel-2.0.0.598-25.el7_1.x86_64
--> Finished Dependency Resolution
Error: Package: ruby-devel-2.0.0.598-25.el7_1.x86_64 (RHN-rhel-x86_64-server-optional-7-1-locked)
Requires: ruby(x86-64) = 2.0.0.598-25.el7_1
Installed: ruby-2.0.0.648-29.el7.x86_64 (#RHN-rhel-x86_64-server-7-latest)
ruby(x86-64) = 2.0.0.648-29.el7
Available: ruby-2.0.0.353-20.el7.x86_64 (RHN-rhel-x86_64-server-7)
ruby(x86-64) = 2.0.0.353-20.el7
Available: ruby-2.0.0.353-22.el7_0.x86_64 (RHN-rhel-x86_64-server-7)
ruby(x86-64) = 2.0.0.353-22.el7_0
Available: ruby-2.0.0.598-24.el7.x86_64 (RHN-rhel-x86_64-server-7)
ruby(x86-64) = 2.0.0.598-24.el7
Available: ruby-2.0.0.598-25.el7_1.x86_64 (RHN-rhel-x86_64-server-7-1-locked)
ruby(x86-64) = 2.0.0.598-25.el7_1
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Can anyone suggest me steps to install ruby-devel using yum?please
Something seems off about your configured repositories.
From your error message, YUM is attempting to install ruby-devel.x86_64 0:2.0.0.598-25.el7_1 from the "RHN-rhel-x86_64-server-optional-7-1-locked" channel, but you currently have ruby-2.0.0.648-29.el7.x86_64 installed from the "#RHN-rhel-x86_64-server-7-latest" channel which will not satisfy the dependency as the release versions do not match.
For YUM to complete the transaction you posted, it would have to install an older version of the RedHat ruby package and I don't think it wants to do that without being explicitly told.
There are a couple options I can think of, depending on how you want to resolve this. My first suggestion is what I would do if I were managing this server, which is to straighten out the repository configuration and discover why yum install ruby-devel is attempting to install an older package (it might have something to do with that locked channel).
The other option is to install that ruby-devel package by any means necessary which may not be good for your RedHat subscription or could break things. You would first replace the installed version of ruby with the older one that matches ruby-devel, then attempt to install ruby-devel:
yum downgrade ruby-2.0.0.598-25
yum install ruby-devel-2.0.0.598-25
I do not have a RedHat machine with a subscription so I would not be able to test if this second suggestion would even work, use at your own risk. I would also recommend again you attempt the first suggestion of fixing your repositories or figure out why one of the channels is locked as that method would be safer and you could get support from RedHat if needed.
Hope that helps

Why can't I uninstall mysql-5.5 & install mysql-5.6 on Amazon Linux machine?

I'm on a 64-bit Amazon Linux machine.
I had previously installed mysql-server 5.5. (using sudo yum install)
However, I soon found out that my application requires MySql-serve 5.6.
So I uninstalled mysql-server 5.5. (using sudo yum remove mysql-server) and now I'm following these instruction to install mysql-server 5.6.
But I'm running into a problem.
when I try to do the second install, I get the following 2 errors:
file /usr/lib64/mysql/libmysqlclient.so.18 from install of mysql-community-libs-5.6.14-3.el6.x86_64 conflicts with file from package mysql55-libs-5.5.46-1.10.amzn1.x86_64
file /etc/my.cnf from install of mysql-community-server-5.6.14-3.el6.x86_64 conflicts with file from package mysql-config-5.5.46-1.10.amzn1.x86_64
Why on earth am I getting these two errors? How do I fix them?
I removed mysql-server-5.5, so why is it conflicting with 5.6?
I did ls on /etc/my.cnf and /usr/lib64/mysql/libmysqlclient.so.18 and the files don't even exist!! If the files don't exist how can they be conflicting with other files?? Who can help explain this?
PS, I tried #msknapp's explanation here: Can't install MySQL 5.6 by RPM, however I don't know what to do after step #1 to install the rpm. I think that step is left unstated.
mysql-server (of whatever version) depends on other packages ( in your case mysql-community-libs mysql-community-server)
When it is installed in the first place with the old version this stuff is installed. When you "uninstall" mysql-server these dependencies are NOT removed.
When you try and install the new version these still existing packages will conflict with the new package. It does not matter if the actual files in the package are there, it is the package and it's listing of what to expect that conflicts.
To resolve your problem figure out what the dependencies of mysql-server were and uninstall them before attemping the install.
This answer https://superuser.com/questions/294662/how-to-get-list-of-dependencies-of-non-installed-rpm-package may be of interest for working out what mysql-server depends on

mysql 5.5 on centos 6.4

I have a requirement for MySQL 5.5, and the box is a CentOS 6.4 64-bit VM.
MySQL 5.1.69 is installed, and won't let me install any of the RPMs from the 5.5 RPMs..
MySQL-client-5.5.32-1.el6.x86_64.rpm
MySQL-devel-5.5.32-1.el6.x86_64.rpm
MySQL-embedded-5.5.32-1.el6.x86_64.rpm
MySQL-server-5.5.32-1.el6.x86_64.rpm
MySQL-shared-5.5.32-1.el6.x86_64.rpm
MySQL-shared-compat-5.5.32-1.el6.x86_64.rpm
MySQL-test-5.5.32-1.el6.x86_64.rpm
So I run yum -y remove mysql and then try to install the newer version. I first of all run
rpm -ivh MySQL-shared-5.5.32-1.el6.x86_64.rpm
rpm -ivh MySQL-shared-compat-5.5.32-1.el6.x86_64.rpm
So far so good. I then try to install the server.
rpm -ivh MySQL-server-5.5.32-1.el6.x86_64.rpm
And I get this..
file /usr/share/mysql/romanian/errmsg.sys from install of MySQL-server-5.5.32-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.69-1.el6_4.x86_64
... and so on. If I google some of those errors, I get this page from StackOverflow..
Installing mysql-libs on server with MySQL-Server5.5
.. but if I look at the advice, it says to install the MySQL-shared-compat-5.5.32-2.el6.x86_64.rpm. But it's already installed. :(
Any advice would be welcome. Thank you.
One way is to install all the RPMs at the same time with yum install MySQL*.rpm, which ideally should take care of all package dependencies and upgrades.
You can also get around this problem by using the --replacefiles option to RPM:
rpm -ivh --replacefiles MySQL-server-5.5.32-1.el6.x86_64.rpm
That uses the error message language files from the server package to overwrite those in the 5.1 version that comes with CentOS.
Had this issue with webtatic repository.
Using remi, epel and rpmforge repository saved me the trouble.
Here is the link I referred :
Cent OS 6.4, Php 5.4, Mysql 5.5 - HowTo