Followed the guide to install pacemaker & corosync enter link description here on a Oracle Linux 8 VM which essentially does the below to access the HA items:
sudo dnf config-manager --enable ol8_appstream ol8_baseos_latest ol8_addons
Which is all fine and installed perfectly. However, now when i try to yum update i get this:
[root#private]# yum update
Last metadata expiration check: 0:01:41 ago on Mon 20 Jun 2022 10:41:09 EDT.
Error:
Problem 1: package corosync-3.1.5-1.el8.x86_64 requires corosynclib(x86-64) = 3.1.5-1.el8, but none of the providers can be installed
- cannot install both corosynclib-3.1.5-2.el8.x86_64 and corosynclib-3.1.5-1.el8.x86_64
- cannot install the best update candidate for package corosynclib-3.1.5-1.el8.x86_64
- cannot install the best update candidate for package corosync-3.1.5-1.el8.x86_64
Problem 2: package pacemaker-2.1.0-8.0.1.el8.x86_64 requires pacemaker-cluster-libs(x86-64) = 2.1.0-8.0.1.el8, but none of the providers can be installed
- cannot install both pacemaker-cluster-libs-2.1.2-4.0.1.el8.x86_64 and pacemaker-cluster-libs-2.1.0-8.0.1.el8.x86_64
- cannot install the best update candidate for package pacemaker-cluster-libs-2.1.0-8.0.1.el8.x86_64
- cannot install the best update candidate for package pacemaker-2.1.0-8.0.1.el8.x86_64
Problem 3: package pacemaker-cli-2.1.0-8.0.1.el8.x86_64 requires pacemaker-libs(x86-64) = 2.1.0-8.0.1.el8, but none of the providers can be installed
- cannot install both pacemaker-libs-2.1.2-4.0.1.el8.x86_64 and pacemaker-libs-2.1.0-8.0.1.el8.x86_64
- cannot install the best update candidate for package pacemaker-libs-2.1.0-8.0.1.el8.x86_64
- cannot install the best update candidate for package pacemaker-cli-2.1.0-8.0.1.el8.x86_64
Problem 4: package pcs-0.10.12-6.0.1.el8_6.1.x86_64 requires pacemaker-cli >= 2.0.0, but none of the providers can be installed
- package pacemaker-cli-2.1.0-8.0.1.el8.x86_64 requires pacemaker-libs(x86-64) = 2.1.0-8.0.1.el8, but none of the providers can be installed
- package pacemaker-cli-2.0.5-9.0.1.el8_4.1.x86_64 requires pacemaker-libs(x86-64) = 2.0.5-9.0.1.el8_4.1, but none of the providers can be installed
- package pacemaker-cli-2.0.5-9.0.1.el8_4.3.x86_64 requires pacemaker-libs(x86-64) = 2.0.5-9.0.1.el8_4.3, but none of the providers can be installed
- package pacemaker-cli-2.0.2-3.el8_1.2.x86_64 requires pacemaker-libs(x86-64) = 2.0.2-3.el8_1.2, but none of the providers can be installed
- package pacemaker-cli-2.0.3-5.el8.x86_64 requires pacemaker-libs(x86-64) = 2.0.3-5.el8, but none of the providers can be installed
- package pacemaker-cli-2.0.3-5.el8_2.1.x86_64 requires pacemaker-libs(x86-64) = 2.0.3-5.el8_2.1, but none of the providers can be installed
- package pacemaker-cli-2.0.4-6.el8.x86_64 requires pacemaker-libs(x86-64) = 2.0.4-6.el8, but none of the providers can be installed
- package pacemaker-cli-2.0.4-6.el8_3.1.x86_64 requires pacemaker-libs(x86-64) = 2.0.4-6.el8_3.1, but none of the providers can be installed
- package pacemaker-cli-2.0.4-6.el8_3.2.x86_64 requires pacemaker-libs(x86-64) = 2.0.4-6.el8_3.2, but none of the providers can be installed
- package pacemaker-libs-2.1.0-8.0.1.el8.x86_64 requires pacemaker-schemas = 2.1.0-8.0.1.el8, but none of the providers can be installed
- package pacemaker-libs-2.0.5-9.0.1.el8_4.1.x86_64 requires pacemaker-schemas = 2.0.5-9.0.1.el8_4.1, but none of the providers can be installed
- package pacemaker-libs-2.0.5-9.0.1.el8_4.3.x86_64 requires pacemaker-schemas = 2.0.5-9.0.1.el8_4.3, but none of the providers can be installed
- package sbd-1.5.1-1.el8.x86_64 conflicts with pacemaker-libs < 2.0.5-4 provided by pacemaker-libs-2.0.2-3.el8_1.2.x86_64
- package sbd-1.5.1-1.el8.x86_64 conflicts with pacemaker-libs < 2.0.5-4 provided by pacemaker-libs-2.0.3-5.el8.x86_64
- package sbd-1.5.1-1.el8.x86_64 conflicts with pacemaker-libs < 2.0.5-4 provided by pacemaker-libs-2.0.3-5.el8_2.1.x86_64
- package sbd-1.5.1-1.el8.x86_64 conflicts with pacemaker-libs < 2.0.5-4 provided by pacemaker-libs-2.0.4-6.el8.x86_64
- package sbd-1.5.1-1.el8.x86_64 conflicts with pacemaker-libs < 2.0.5-4 provided by pacemaker-libs-2.0.4-6.el8_3.1.x86_64
- package sbd-1.5.1-1.el8.x86_64 conflicts with pacemaker-libs < 2.0.5-4 provided by pacemaker-libs-2.0.4-6.el8_3.2.x86_64
- cannot install both pacemaker-schemas-2.1.2-4.0.1.el8.noarch and pacemaker-schemas-2.1.0-8.0.1.el8.noarch
- cannot install both pacemaker-schemas-2.1.2-4.0.1.el8.noarch and pacemaker-schemas-2.0.5-9.0.1.el8_4.1.noarch
- cannot install both pacemaker-schemas-2.1.2-4.0.1.el8.noarch and pacemaker-schemas-2.0.5-9.0.1.el8_4.3.noarch
- cannot install the best update candidate for package sbd-1.5.1-1.el8.x86_64
- cannot install the best update candidate for package pcs-0.10.12-6.0.1.el8_6.1.x86_64
- cannot install the best update candidate for package pacemaker-schemas-2.1.0-8.0.1.el8.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
I have experienced this issue myself today. The message is verbose and hard to read. There is a package that can be updated (corosynclib) but its dependency (corosync) does not have a corresponding update.
Essentially, the corosync package is located in the ol8_addons repository and the corosynclib package is located in the ol8_appstream repository. Currently, there is no corresponding corosync 3.1.5-2 release required by the corosynclib 3.1.5-2 package.
I built the corosync 3.1.5-2 package from the source (SRPM) package (just as a test) and installed it.
rpmbuild --rebuild corosync-3.1.5-2.el8.src.rpm
dnf install corosync-3.1.5-2.el8.rpm
The reason for OracleLinux's missing package is not clear, perhaps it is a mistake and needs reporting to Oracle.
As with corosync, different pacemaker package versions exist in both ol8_addons and ol8_appstream repositories. Fortunately, matching package versions can be installed. To fix the situation I removed all pacemaker packages and installed afresh:
dnf remove pacemaker*
dnf install pacemaker-2.1.2-4.0.1.el8_6.2
Finally, an update should be possible and is error free:
dnf update
Related
I've tried to remove php-common-7.2 but couldn't find where it located.
Problem: package php-pecl-igbinary-3.2.2-1.el8.remi.7.2.x86_64 requires php(api) = 20170718-64, but none of the providers can be installed
- package php-pecl-igbinary-3.2.2-1.el8.remi.7.2.x86_64 requires php(zend-abi) = 20170718-64, but none of the providers can be installed
- cannot install both php-common-7.2.34-3.el8.remi.x86_64 and php-common-7.4.16-1.el8.remi.x86_64
- cannot install both php-common-7.2.34-4.el8.remi.x86_64 and php-common-7.4.16-1.el8.remi.x86_64
- cannot install the best update candidate for package php-pecl-igbinary-3.2.1-1.el8.remi.7.4.x86_64
- problem with installed package php-common-7.4.16-1.el8.remi.x86_64
- package php-common-7.2.24-1.module_el8.2.0+313+b04d0a66.x86_64 is filtered out by modular filtering
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
My server configuration is
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
Apache Web Server
php7.4-cli
using Webmin & virtaulmin`
You are trying to install igbinary extension for PHP 7.2 with PHP 7.4. This cannot work.
For a proper configuration, please follow the Wizard instructions
And not enough information for more help:
rpm -qa php\*
dnf repolist
dnf module list PHP
I want to run ASP.NET MVC application in Debian 10 with Apache.
I have installed latest mono from mono Debian 10 repository using apt.
Trying to install mod_modo using
apt install libapache2-mod-mono
throws error
> Reading package lists... Done Building dependency tree Reading state
> information... Done Some packages could not be installed. This may
> mean that you have requested an impossible situation or if you are
> using the unstable distribution that some required packages have not
> yet been created or been moved out of Incoming. The following
> information may help to resolve the situation:
>
> The following packages have unmet dependencies: libapache2-mod-mono :
> Depends: mono-apache-server (< 4.6) but 4.7.1-0xamarin2+debian10b1 is
> to be installed or
> mono-apache-server4 (< 4.6) but 4.7.1-0xamarin2+debian10b1 is to be installed or
> mono-apache-server2 (< 4.6) but it is not installable
> E: Unable to correct problems, you have held broken
> packages.
How to install mod_mono on Debian 10 ?
/etc/apache2/mods-available contans mod_mono.
Maybe it is sufficient to enable it in apache to get it work ?
/etc/sources.list contains:
deb http://ftp.debian.org/debian buster main contrib non-free
deb http://ftp.debian.org/debian buster-updates main contrib non-free
deb http://security.debian.org buster/updates main contrib non-free
/etc/apt/sources.list.d contains two files:
mono-official-stable-list:
deb https://download.mono-project.com/repo/debian stable-buster main
and pgdg.list:
deb http://apt.postgresql.org/pub/repos/apt/ buster-pgdg main
#deb-src http://apt.postgresql.org/pub/repos/apt/ buster-pgdg main
Update
I tried commands from GAD3R answer.
apt install libapache2-mod-mono
still fails. Error message is a bit different:
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.debian.org/debian buster InRelease
Hit:3 http://ftp.debian.org/debian buster-updates InRelease
Hit:4 http://apt.postgresql.org/pub/repos/apt buster-pgdg InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
7 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libapache2-mod-mono : Depends: mono-apache-server (< 4.4) but 4.7.1-0xamarin2+debian10b1 is to be installed or
mono-apache-server4 (< 4.4) but 4.7.1-0xamarin2+debian10b1 is to be installed
E: Unable to correct problems, you have held broken packages.
Install libapache2-mod-mono from the official debian repository.
sudo rm /etc/apt/sources.list.d/mono-official-stable.list
Then run :
sudo apt update
sudo apt purge mono.
sudo apt autoremove
sudo apt install libapache2-mod-mono
please file a bug report to mono dev team on github.
Recently reinstalled my computer with Ubuntu 14.04.
This pc is to be used to develop ASP.NET mono applications.
So I installed the latest 3.12.0 version of Mono.
Also installed Apache2 (2.4.7 is the latest).
Last thing is to install Mod_Mono. This is where it fails.
sudo apt-get install libapache2-mod-mono
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libapache2-mod-mono : Depends: apache2.2-common but it is not installable
E: Unable to correct problems, you have held broken packages.
So I tried to install apache2.2-common but that does not exist, there is only a apache2.2-bin. I installed that and it still did not solve my problem.
sudo apt-get install apache2.2-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package apache2.2-common is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
apache2-bin:i386 apache2:i386 apache2-data apache2-bin apache2
E: Package 'apache2.2-common' has no installation candidate
Any suggestions to what I can do so I can host my Mono application through apache2?
Solved this issue by installing Apache 2.2.22.
Had a bit of trouble doing that, but finally installed it running this command.
sudo apt-get install apache2=2.2.22-1ubuntu1.7 apache2.2-common=2.2.22-1ubuntu1.7 apache2.2-bin=2.2.22-1ubuntu1.7 apache2-mpm-worker=2.2.22-1ubuntu1.7
Note: you need to add the precise repository to your software sources, else you won't have the package available to install.
Is yum aware of package chronology?
Suppose I build a package MY-PKG-0.40-1 and publish it in a yum repo with createrepo --update. Then I build another package with a lower version (from a different VCS branch), MY-PKG-0.38-5.
yum list recent seems to show the greatest version, not the latest one. However from the man page
yum list recent
List packages recently added into the repositories. This is often not
helpful, but what you may really want to use is
"yum list-updateinfo new" from the security yum plugin.
I've experimented with list-updateinfo new and finding little success. yum list-updateinfo new MY-PKG seems to return repositories the package belongs to...
What I want is something like yum list latest MY-PKG to return 0.38-5, given it's the latest version published to the repository, despite having already published 0.40-1.
The answer here is yes. Since yum manages RPMs and running rpm -qi <package> will list a Build Date field (which is part of the package header).
After digging around on the net, the yum python libraries, and working off some of the code samples on the yum wiki, I was able to code up a working sample which lists the latest version of a package.
#!/usr/bin/python
import sys
import yum
package = sys.argv[1:]
yb = yum.YumBase()
yb.conf.cache = 0 # Must run as root to search packages w/o cache
pl = yb.doPackageLists(patterns=package, pkgnarrow='all', showdups=True)
print 'Searching for latest version of package: ' + str(package[0])
if pl.available:
package = ''
latest = 0
for pkg in sorted(pl.available):
# XXX Works with sqlitesack, unsure if it works with rpmsack
buildtime = pkg['buildtime']
# If we're looking at the latest package, update the version
# and textual name for reference
if max(latest, buildtime) == buildtime:
latest = buildtime
package = pkg
print "Latest Package"
print package
I have tried to install mod_security, but it has the error, so I tried aptitude:
apt-get install libapache-mod-security
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libapache-mod-security : Depends: libapache2-modsecurity but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root#srv16540:~# aptitude install libapache2-modsecurity
The following NEW packages will be installed:
apache2.2-common{ab} libapache2-modsecurity modsecurity-crs{a}
0 packages upgraded, 3 newly installed, 0 to remove and 10 not upgraded.
Need to get 660 kB of archives. After unpacking 2,861 kB will be used.
The following packages have unmet dependencies:
apache2 : Conflicts: apache2.2-common but 2.2.22-1ubuntu1.4 is to be installed.
apache2.2-common : Depends: apache2.2-bin (= 2.2.22-1ubuntu1.4) but 2.4.6-2~precise+1 is installed.
apache2-bin : Conflicts: apache2.2-common but 2.2.22-1ubuntu1.4 is to be installed.
apache2-data : Conflicts: apache2.2-common but 2.2.22-1ubuntu1.4 is to be installed.
The following actions will resolve these dependencies:
**Keep the following packages at their current version:**
1) apache2.2-common [Not Installed]
2) libapache2-modsecurity [Not Installed]
3) modsecurity-crs [Not Installed]
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
I do now know what Keep the following packages at their current version means.
I want to know what does happen if I press yes. Does it replace my current apache2? Do I need to back up before doing this?
ANSWERS
I do now know what Keep the following packages at their current version mean
aptitude is trying to resolve the dependencies and possible conflicts to satisfy your installation request. It then proposes a solution. In your particular case the first solution it finds is to keep everything as it actually is, that's what keep at their current version + [Not installed] means.
I want to know what does happen if I press yes , does it replace my current apache2 ?
No, that solution will basically do nothing.
Do I need back up before ?
As boring as it sounds, backups are a good strategy to save time in the long run. If you're messing with important data then it should be even more important for you.
CONTEXT
I've seen other scenarios make aptitute propose solutions with combinations like these:
Remove the following packages
Keep the following packages at their current version
Leave the following dependencies unresolved
The following packages have been kept back
The following packages will be upgraded
The following packages were automatically installed and are no longer required
The following extra packages will be installed
Suggested packages
The following packages will be REMOVED
(and probably others)
In your case if instead of accepting the solution (or quitting), you reject it by pressing n, then aptitude will try to figure out another scenario that could be useful and propose it to you again. You can iterate through the solutions doing that and if any of them satisfies you then you can accept it.
SOLUTION (?)
As far as I can see by your output:
apache2.2-common : Depends: apache2.2-bin (= 2.2.22-1ubuntu1.4) but 2.4.6-2~precise+1 is installed.
Your problem is that you have apache2-2.4.6-2~precise+1 installed which isn't available from standard Ubuntu precise repositories (most probably installed from this PPA), and you're requesting a package which conflicts with that other one.
I'd take a look at the answers on how to remove PPAs and after you have removed that source I'd reinstall apache 2.2 from the standard repos with this command:
sudo aptitude install apache2
That's exactly what it did for me:
$ sudo apt-get remove apache2-bin
$ sudo apt-get autoremove
$ sudo apt-get install apache2
Open synaptic manager and search for apache2.2-bin. Mark it for removal. Then
sudo apt-get install apache2
Just remove all the content of /var/lib/apt/lists directory:
sudo rm -rf /var/lib/apt/lists/*
then run:
sudo apt-get update