OpenVSwitch won't install on my Alma Linux server - openvswitch

When I am attempting to install OpenVSwitch from the RPM generated from the documentation, it spews out an error, the following. I have python2 installed, python3, and python3.6. I generally do not know why it is showing this, but my 9:40 at night brain can't exactly comprehend much.
[root#Alma-85-amd64-base x86_64]# yum install python2
Last metadata expiration check: 1:15:52 ago on Tue 08 Mar 2022 02:20:48 AM CET.
Package python2-2.7.18-7.module_el8.5.0+2579+77770ab7.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[root#Alma-85-amd64-base x86_64]# rpm -i openvswitch-2.17.0-1.el8.x86_64.rpm
error: Failed dependencies:
python >= 2.7 is needed by openvswitch-2.17.0-1.el8.x86_64
[root#Alma-85-amd64-base x86_64]#

Alright, here's an update. I could not get OpenVSwitch to work on any version of RHEL 8, but it did work on RHEL 7.

Related

Has anyone figured out how to install `moreutils` on Centos8?

Has anyone figured out how to install moreutils on Centos8?
I'm getting this error:
[root#default-bento-centos-8 vagrant]# dnf install moreutils
Last metadata expiration check: 0:19:17 ago on Tue 17 Aug 2021 08:27:50 PM UTC.
Error:
Problem: conflicting requests
- nothing provides perl(IPC::Run) needed by moreutils-0.63-1.el8.x86_64
- nothing provides perl-IPC-Run needed by moreutils-0.63-1.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[root#default-bento-centos-8 vagrant]# dnf -y --enablerepo=PowerTools install moreutils
Error: Unknown repo: 'PowerTools'
I have both the epel-release and perl packages installed.
The enable repo argument is case sensitive and powertools needs to be fully lower cased as opposed to Pascal Cased.
This works:
dnf install epel-release -y
dnf --enablerepo=powertools install moreutils -y

centos 7 get latest apache package

This question comes from my lack of understanding of package managers,
I run yum list and get httpd-2.4.6-40.el7.centos.4.x86_64
https://rpmfind.net/linux/RPM/centos/updates/7.2.1511/x86_64/Packages/httpd-2.4.6-40.el7.centos.4.x86_64.html
Build date: Mon Jul 18 17:32:11 2016
I did yum update && yum install httpd, will this get me the latest version of httpd?
where can I check online to confirm my package/build is the latest?
how can I periodically install security patches for my version of httpd?
update
[centos ~]$ httpd -v
Server version: Apache/2.4.6 (CentOS)
Server built: Jul 18 2016 15:30:14
[centos ~]$ rpm -q --changelog httpd | more
* Mon Jul 18 2016 CentOS Sources <bugs#centos.org> - 2.4.6-40.el7.centos.4
- Remove index.html, add centos-noindex.tar.gz
- change vstring
- change symlink for poweredby.png
- update welcome.conf with proper aliases
As Aaron mentioned, package managers like yum will only apply security patches as they prioritise stability (with security) over new features.
So after you do a "yum update" you will be on a patched version of httpd 2.4.6 which should have all the required security patches right up to the latest httpd release (2.4.23 at time of writing) but none of the other non-security changes (e.g. http/2 support or any of the other features and bug fixes unless security related).
So it's not really 2.4.6 anymore, despite the name, but at same time it's definitely not 2.4.23 either.
You can confirm the patches have been applied by running this command (as detailed here):
rpm -q --changelog httpd | more
Or perhaps, to check for a specific CVE:
rpm -q --changelog httpd | grep CVE-Number
And the vulnerabilities fixed in each version of Apache httpd (which should be back ported within a short space of time by Red Hat/Centos) are here:
https://httpd.apache.org/security/vulnerabilities_24.html or here: https://www.cvedetails.com/version-list/45/66/1/Apache-Http-Server.html
The best way to periodically install security updates is to do a "sudo yum update" regularly or consider installing yum-cron to do this for you. There is still some debate as to whether this should be fully automated in prod.
yum uses only the repositories it is configured to use; not just any RPM on the internet. That would be dangerous. If you have an up-to-date version of CentOS, they will release security updates for httpd. Once installed, a yum update will bring in patches.
CentOS is an Enterprise-level OS. They don't always have the "latest and greatest." You'll see they will stay with the same version, e.g. 2.4, but apply patches to it. The next major release of the OS would then have a more current version, e.g. 3.x. There are few exceptions, like Firefox, where they will stay with the ESR versions.

What provides libicui18n.so.52.1()(64bit) on Fedora (23)?

I'm trying to install libQt5Core from an rpm and I get:
Error: nothing provides libicui18n.so.52.1()(64bit) needed by libQt5Core5-5.5.1-4.1.x86_64
There is newer version:
dnf whatprovides libicui18n*
Last metadata expiration check performed 0:00:14 ago on Fri Jan 29 13:58:14 2016.
libicu-54.1-5.fc23.x86_64 : International Components for Unicode - libraries
Repo : #System
Where do you install the libQt5Core from? The official repositories should not require packages versions that are not available.
Don't use that RPM to install the QT 5 core libraries. I'm guessing that you have a package for openSUSE (because that's what comes up when I Google for "libQt5Core rpm"). In Fedora, the package you want is qt5-qtbase. Install that with:
sudo dnf install qt5-qtbase
It happens that our version in Fedora 23 is also version 5.5.1, so I think that'll be what you really need here.
If you're doing software development, you might want to pull in the KDE Frameworks 5 development group, which is mostly QT stuff and which will get you set up for building programs against that, which might be what you're trying to do:
sudo dnf groupinstall kf5-software-development

An incompatible version 1.1.22 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.24

I installed apache apr on ubuntu 10.04 with
sudo apt-get install libtcnative-1
When I stated my tomcat I got the following error:
Aug 07, 2013 6:57:32 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.22 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.24
How do I have to fix that error?
You have to upgrade your Tomcat native library to a newer version:
sudo apt-get upgrade libtcnative-1
I created a script for compiling Apache Tomcat Native library:
#!/bin/bash
export APR_PATH=/usr/bin/apr-1-config
export JAVA_HOME=/opt/java
export TOMCAT_HOME=/opt/tomcat
export INSTALL_PREFIX=/usr
wajig install libaprutil1-dev make
cd /tmp
rm -Rf tomcat-native-*
tar -zxf $TOMCAT_HOME/bin/tomcat-native.tar.gz
cd /tmp/tomcat-native-*/jni/native
./configure --with-apr=$APR_PATH --with-java-home=$JAVA_HOME --prefix=$INSTALL_PREFIX
make && make install
From the error its clear that your tomcat native is of older version (1.1.22) and service looks for much newer version at least 1.1.24. The latest and stable version of tomcat native is 1.1.27. You can install that. Use the following link to install and fix your current issue.
You can simply do that by installing apr from source and then specify in your setenv the path to library .
Set this in your setenv.sh
export LD_LIBRARY_PATH='$LD_LIBRARY_PATH:/usr/local/apr/lib'
You can follow more here
http://www.sheroz.com/installing-apache-tomcat-native-linux-ubuntu-1204

Install Mono on Centos 5.5 using YUM

How do I install the Mono 2.6.7 runtime on CentOS 5.5 using YUM?
I know how to build Mono from the source. However, according to the page Getting Started With Mono Tools it is possible to install the binaries directly. I'd prefer to install the binaries to avoid having to install all the development pre-requisites on a server with little disk space.
Am I supposed to add a new repository description to YUM? I tried doing that, but I must have done it wrong, because "yum list mono-core" still says the old version (1.2.4-2.el5.centos).
And, why are the .rpm's called "mono-addon-" on the release server? It's a bit confusing. It sounds like the .rpm's are an add-on to Mono. I guess they mean they are an "add-on" to the server(?).
I figured it out.
Create a new repository configuration file
cd /etc/yum.repos.d
vi mono.repo
Add the following lines to the file
[Mono]
name=Mono Stack (RHEL_5)
type=rpm-md
baseurl=http://ftp.novell.com/pub/mono/download-stable/RHEL_5/
gpgcheck=1
gpgkey=http://ftp.novell.com/pub/mono/download-stable/RHEL_5/repodata/repomd.xml.key
enabled=1
Update the YUM cache to be on the safe side
yum clean all
Install the Mono server stack
yum install monotools-addon-server
The installed binaries will end up in "/opt/novell/mono/bin".
You should issue the following command to set up your shell environment so that it finds Mono, mcs and the other Mono tools
source /opt/novell/mono/bin/mono-addon-environment.sh
Verify the version
mono --version
Mono JIT compiler version 2.6.7 (tarball Mon Jul 19 18:28:58 UTC 2010)
Copyright (C) 2002-2010 Novell, Inc and Contributors. www.mono-project.com
TLS: __thread
GC: Included Boehm (with typed GC and Parallel Mark)
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
If you want the Mono environment to be permanent you can issue the following command.
cp /opt/novell/mono/bin/mono-addon-environment.sh /etc/profile.d
Happy Mono'ing!!!
In addition to octonion's post, if, like me, you want to use Apache mod_mono, you need to ensure you install the correct version of mod_mono by running the following, and it will get the right one:
yum install mod_mono-addon
Don't just issue yum install mod_mono. It may install mod_mono 1.2 version from the CentOS extras repository and not what you're actually after.
As a reference, I was getting the following error in /var/log/httpd/error_log when running the incorrect mod_mono version:
Root directory: /
mod_mono and xsp have different versions. Expected '9', got 6
System.InvalidOperationException: mod_mono and xsp have different versions. Expected '9', got 6
It is a silly, but easy mistake to make if you new to this like me.