Trying to update cassandra from 1.0.11-1 to 1.1.12-1 on Centos 5.5. Read the docs on http://www.datastax.com/docs/1.1/install/upgrading and tried the advised method: yum install apache-cassandra11 to get the package installed; however, am getting depsolving problems.
Is the correct way to update Cassandra is to yum remove and then yum install?
[root#cass01 ~]# yum install apache-cassandra11.noarch
Loaded plugins: allowdowngrade, fastestmirror
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
Excluding Packages from CentOS-5 - Updates
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package apache-cassandra11.noarch 0:1.1.12-1 set to be updated
--> Processing Conflict: apache-cassandra11 conflicts apache-cassandra1
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package apache-cassandra1.noarch 0:1.0.11-1 set to be updated
--> Processing Conflict: apache-cassandra11 conflicts apache-cassandra1
--> Finished Dependency Resolution
apache-cassandra11-1.1.12-1.noarch from datastax has depsolving problems
--> apache-cassandra11 conflicts with apache-cassandra1
Error: apache-cassandra11 conflicts with apache-cassandra1
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
[root#cass01 ~]#
Related
When running:
sudo yum update
I get:
Loaded plugins: amzn_workspaces_filter_updates, halt_os_update_check, priorities, update-motd
remi-php74 | 3.0 kB 00:00:00
18186 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package python-s3transfer.noarch 0:0.1.13-1.0.1.el7 will be obsoleting
---> Package python2-s3transfer.noarch 0:0.3.3-1.amzn2.0.1 will be obsoleted
--> Processing Dependency: python2-s3transfer for package: awscli-1.18.147-1.amzn2.0.1.noarch
--> Processing Dependency: python2-s3transfer >= 0.3.0 for package: python2-boto3-1.15.6-1.amzn2.0.1.noarch
--> Finished Dependency Resolution
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I tried "rpm -Va --nofiles --nodigest", but doesn't change anything (yum update throws the same response).
If I try:
sudo yum update --skip-broken
I get:
Loaded plugins: amzn_workspaces_filter_updates, halt_os_update_check, priorities, update-motd
amzn2-core | 3.7 kB 00:00:00
firefox | 2.9 kB 00:00:00
workspaces-internal-dependencies | 2.2 kB 00:00:00
18186 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package python-s3transfer.noarch 0:0.1.13-1.0.1.el7 will be obsoleting
---> Package python2-s3transfer.noarch 0:0.3.3-1.amzn2.0.1 will be obsoleted
--> Processing Dependency: python2-s3transfer for package: awscli-1.18.147-1.amzn2.0.1.noarch
--> Processing Dependency: python2-s3transfer >= 0.3.0 for package: python2-boto3-1.15.6-1.amzn2.0.1.noarch
Packages skipped because of dependency problems:
python-s3transfer-0.1.13-1.0.1.el7.noarch from ol7_latest
I am not a Linux expert, and I do not know how to get past this error. What should I remove or add and how?
I am having problems installing mod_ssl onto my AWS Apache instance...
[ec2-user#ip-172-31-18-185 ~]$ yum install mod_ssl
Loaded plugins: priorities, update-motd, upgrade-helper
You need to be root to perform this command.
[ec2-user#ip-172-31-18-185 ~]$ sudo yum install mod_ssl
Loaded plugins: priorities, update-motd, upgrade-helper
Resolving Dependencies
--> Running transaction check
---> Package mod_ssl.x86_64 1:2.2.34-1.16.amzn1 will be installed
--> Processing Dependency: httpd-mmn = 20051115 for package: 1:mod_ssl-2.2.34-1.16.amzn1.x86_64
--> Processing Dependency: httpd = 2.2.34-1.16.amzn1 for package: 1:mod_ssl-2.2.34-1.16.amzn1.x86_64
--> Running transaction check
---> Package httpd.x86_64 0:2.2.34-1.16.amzn1 will be installed
--> Processing Dependency: httpd-tools = 2.2.34-1.16.amzn1 for package: httpd-2.2.34-1.16.amzn1.x86_64
--> Processing Dependency: apr-util-ldap for package: httpd-2.2.34-1.16.amzn1.x86_64
--> Running transaction check
---> Package apr-util-ldap.x86_64 0:1.5.4-6.18.amzn1 will be installed
---> Package httpd-tools.x86_64 0:2.2.34-1.16.amzn1 will be installed
--> Processing Conflict: httpd24-2.4.33-2.78.amzn1.x86_64 conflicts httpd < 2.4.33
--> Processing Conflict: httpd24-tools-2.4.33-2.78.amzn1.x86_64 conflicts httpd-tools < 2.4.33
--> Finished Dependency Resolution
Error: httpd24-tools conflicts with httpd-tools-2.2.34-1.16.amzn1.x86_64
Error: httpd24 conflicts with httpd-2.2.34-1.16.amzn1.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[ec2-user#ip-172-31-18-185 ~]$
I have tried running sudo yum install 24mod_ssl to no avail? It says No package 24mod_ssl available.
What can I do?
In case someone has missed Andra's comment above, like I did the first time I looked at this post:
To solve the conflict you are having install the following module instead:
sudo yum install mod24_ssl.x86_64
Your apache modules is conflicting. see here
httpd24-tools conflicts with httpd-tools-2.2.34-1.16.amzn1.x86_64. It looks like you have chose pre installed apache AMI and have installed apache again on it.
I'm trying to update MongoDB 2.4 to 2.6 on my 64-bit CentOS machine. I have removed the old 10gen repository package and created the /etc/yum.repos.d/mongodb.repo file with the new configuration as explained here.
However, when I run sudo yum install mongodb-org, I get the following error:
Error: mongodb-org conflicts with mongodb-org-server
This is the output in the shell:
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mongodb-org.x86_64 0:2.6.1-0.1.rc0 will be installed
--> Processing Dependency: mongodb-org-server = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-shell = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-mongos = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Processing Dependency: mongodb-org-tools = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64
--> Running transaction check
---> Package mongodb-org-mongos.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-server.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-shell.x86_64 0:2.6.1-0.1.rc0 will be installed
---> Package mongodb-org-tools.x86_64 0:2.6.1-0.1.rc0 will be installed
--> Processing Conflict: mongodb-org-2.6.1-0.1.rc0.x86_64 conflicts mongo-10gen-server
--> Finished Dependency Resolution
Error: mongodb-org conflicts with mongodb-org-server
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Has anyone else encountered anything similar? What is the best course of action here? Should I try using the --skip-broken option? I did a fresh installation in a new box a couple of days ago and did not encounter any problems.
Thanks for your help with this.
My best guess is that the yum build was broken when they updated to version 2.6.1-0.1.rc0.
For a temporary fix you could:
Try the unstable version, which is currently 2.5.5
yum install mongodb-org-unstable
or the regular mongodb package that comes with OS
yum install -y mongodb mongodb-server
Actually I had the same problem, the process that worked for me was:
Stop all mongo processes
service mongoInstance stop
Remove mongodb
yum remove -y mongodb
If not removed yet
rpm -e --noscripts mongodb-server
After that you may install mongodb-org and re-enable your processes.
During the release of version 2.6.1-rc0, packages were accidentally published into the MongoDB yum and apt repositories such that new and upgrade requests would install the release candidate 2.6.1-rc0 instead of 2.6.0 (stable release).
Users expecting to install, upgrade to, or retain version 2.6.0 may have inadvertently installed version 2.6.1-rc0, which is a release candidate and not recommended for production use. However, we do not expect that accidentally updating to 2.6.1-rc0 will adversely affect your data or operations.
The packages were incorrectly published on April 22, 5:30pm EDT. The issue was resolved on April 23, 11:30AM EDT. Users who attempted to install or upgrade to version 2.6.0 during this time were affected by this issue.
More information for this issue can be found here: https://jira.mongodb.org/browse/SERVER-13691
Ernie Hershey from MongoDB just answered my post on the MongoDB user group:
https://groups.google.com/forum/#!topic/mongodb-user/5xRQW7ER4hE
Basically, there is a bug in how MongoDB RC packages are generated. So you need to run yum makecache before running yum install mongodb-org. That should fix the problem.
I have a helper rpm package which is used to install the necessary dependencies in order for some software to work; the problem is that the dependency packages required are the 32bit ones, which can't be installed on CentOS 64bit without the --setopt=protected_multilib=false flag.
To manually install the dependencies I'd just run:
# yum install --setopt=protected_multilib=false libXrandr.i686
# yum install --setopt=protected_multilib=false gtk2.i686
# yum install --setopt=protected_multilib=false libXtst.i686
This would correctly install the 32bit version of the packages.
The problem appears when installing the helper package directly, as it seems there's no way to force --setopt=protected_multilib=false for the dependencies.
When trying to install the package (locally, using yum --nogpgcheck --setopt=protected_multilib=false localinstall centos_helper-0-0.x86_64.rpm) I get the following error:
Examining centos_helper-0-0.x86_64.rpm: centos_helper-0-0.x86_64
Marking centos_helper-0-0.x86_64.rpm to be installed
Loading mirror speeds from cached hostfile
* base: mirror.dattobackup.com
* extras: mirror.metrocast.net
* rpmforge: mirror.de.leaseweb.net
* updates: mirror.dattobackup.com
Resolving Dependencies
--> Running transaction check
---> Package centos_helper.x86_64 0:0-0 will be installed
--> Processing Dependency: libXrandr.i686 for package: centos_helper-0-0.x86_64
--> Processing Dependency: gtk2.i686 for package: centos_helper-0-0.x86_64
--> Processing Dependency: libXtst.i686 for package: centos_helper-0-0.x86_64
--> Finished Dependency Resolution
Error: Package: centos_helper-0-0.x86_64 (/centos_helper-0-0.x86_64)
Requires: gtk2.i686
Error: Package: centos_helper-0-0.x86_64 (/centos_helper-0-0.x86_64)
Requires: libXrandr.i686
Error: Package: centos_helper-0-0.x86_64 (/centos_helper-0-0.x86_64)
Requires: libXtst.i686
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
This is the same error I get when trying to install the dependencies by hand without the protected_multilib=false flag.
The .spec file I'm using to create the package has the following content:
Summary: CentOS helper file
Name: centos_helper
Version: 0
Release: 0
License: Public
Group: Applications/System
Requires: libXrandr.i686,gtk2.i686,libXtst.i686
%description
Installer CentOS helper package
%files
Any way to have the dependencies correctly install?
You might want to look at http://www.rpm.org/wiki/PackagerDocs/ArchDependencies
I prefer referencing sonames myself, that way yum will look up what dependancy to install.
I've had major CentOS upgrades failing because if this.
This if for recent RPM versions only : 4.6 or so. If you're on something older :
Requires: real-soname.so.1()(64bit), real-soname.so.1, packagename
From memory, you might need a tweak.
I am trying to install yum-utils package to resolve a broken installation, but it fails due to a conflict:
sudo yum install yum-utils --skip-broken
returns
Loaded plugins: fastestmirror, priorities, security, update-motd
Loading mirror speeds from cached hostfile
Setting up Install Process
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
The program yum-complete-transaction is found in the yum-utils package.
--> Running transaction check
---> Package yum-utils.noarch 0:1.1.30-6.11.amzn1 will be installed
--> Processing Conflict: yum-utils-1.1.30-6.11.amzn1.noarch conflicts system-release <= 2011.09-1.33
--> Finished Dependency Resolution
Packages skipped because of dependency problems:
yum-utils-1.1.30-6.11.amzn1.noarch from amzn-updates
I am finding myself in a catch-22 situation and I don't know how to resolve it. Cannot install any package with yum because of a broken installation (it recommends to run yum-complete-transaction which is in yum-utils), but installing yum-utils also fails.
Any help would be greatly appreciated.
Thanks,
M
Okay, I ran into the same problem - yum bombed out and I couldn't install yum-complete-transaction.
In the end, what I did was copy /usr/sbin/yum-complete-transaction across from another Amazon instance, then ran it and after it finished the remaining transactions installed the 'yum-utils' package.
I know this is probably not the 'most correct' method to fix it, but it worked and quite frankly, if it's stupid but worked, it's not stupid :)