Trying to upgrade Linux Centos/Redhat from 5.x to 6.x version without formatting the os,
need to know any steps for the upgrade from 5.x to 6.x
Based on this, you can simply run the flowing command to upgrade distribution and kernel:
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.9 (Santiago)
# arch
x86_64
# yum upgrade -y
Related
Ansible 2.9.7 is running on RHEL 7.9 server.
We are planning to upgrade the Ansible to latest version.
As per documentation, there are many Ansible versions released after 2.9.7 and latest one is Ansible 7 (ansible-core and ansible).
Can you advise which version would be the appropriate one to upgrade from 2.9.7 on the existing RHEL 7.9 server ? Does latest Ansible versions support RHEL 7.9 ?
Can you advise which version would be the appropriate one to upgrade from 2.9.7 on the existing RHEL 7.9 server?
This will depend on your environment and capabilities.
... just like to note that within Enterprise Packages for Linux (EPEL) a version with bug fixes is available, Ansible v2.9.27.
~/test$ yum provides ansible
...
ansible-2.9.27-1.el7.noarch : SSH-based configuration management, deployment, and task execution system
Repo : EPEL-7
Does latest Ansible versions support RHEL 7.9?
Since it is written in Python it is somehow agnostic about the underlying OS, but it will depend on the Python version installed.
If you don't plan to install another Python environment and stay with the distributed version from the OS, Python 2.7, then you are bound up to Ansible v2.11. See Ansible Community Topic Issue #54.
~/test$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.9 (Maipo)
~/test$ ansible --version
ansible [core 2.11.12]
config file = /home/user/test/ansible.cfg
configured module search path = [u'/home/user/.ansible/plugins/modules', u'/home/user/.ansible/collections/ansible_collections']
ansible python module location = /home/user/.local/lib/python2.7/site-packages/ansible
ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
executable location = /home/user/.local/bin/ansible
python version = 2.7.5 (default, May 27 2022, 11:27:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]
jinja version = 2.11.3
libyaml = True
If you can install another Python environment you can use higher Ansible versions.
Please take note that certain modules, Ansible Galaxy, Collections, etc. may have own requirements and dependencies.
Further Documentation Links
Installing Ansible - Prerequisites (v2.9)
Installing Ansible - Requirements (latest)
Releases and maintenance (latest)
I have a RedHat Linux Server with version 8 and Podman included version 4.2.0. But we need to have Podman version 3.3. Here my questions:
1- Where can i get the Podman version 3.3 ?
3 - How to install the Podman version 3.3 if can i get it ?
I've tried to get Podman version 3.3 from google. But i couldn't find it. If you can give a hand where i can to get it, will be a good help.
I'm confused about which Linux Kernel is used to run Heroku apps, and the docs don't seem to spell it out.
Heroku offers "stacks" synced to Ubuntu LTS releases, and I just upgraded one of our apps from Heroku-18 (Ubuntu 18.04) to Heroku-20 (Ubuntu 20.04), and I was curious as to whether that would constitute a Linux Kernel upgrade.
So, before I upgraded the stack, I logged into a dyno and ran the following (on Heroku-18):
~ $ cat /proc/version_signature
Ubuntu 4.4.0-1097.102-aws 4.4.262
~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic
and then after upgrading to Heroku-20:
~ $ cat /proc/version_signature
Ubuntu 4.4.0-1097.102-aws 4.4.262
~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
So, upgrading did NOT change the Kernel version 4.4.262, which appears to have been released March 2021 (10 months ago).
The docs for Ubuntu 20 say that it's based on LTS Linux 5.4, so why is Heroku continuing to use the older 4.4.x Kernel? When might this be upgraded, and how might it be communicated?
I was also curious what the Kernel version would be for Heroku's container stack; I'm not sure how to find this out, but given the above, I'm betting that it too would be 4.4.x. This matters to me because I'm curious to try out io_uring and some other recent Linux Kernel developments, but it seems like I'd have to wait a long time to try out something like that on Heroku.
I have CloudLinux release 7.6 in my server and I used to have wkhtmltopdf linux generic version 0.12.4 previously. I am trying to upgrade wkhtmltopdf to version 0.12.5 and I noticed they no longer have generic linux version.
How do I install the latest version of wkhtmltopdf in my server that uses CloudLinux?
Can I safely install and use the 0.12.5 version for CentOS 7 instead or is my only option is to continue using the 0.12.4 generic linux version on CloudLinux?
I have installed the CentOS 7 build version of Wkhtmltopdf in my CloudLinux Release 7 and its works fine. I have been using it in my production server for a week now and havent had any issues. Since CentOS and CloudLinux are RHEL compatible, it works fine.
I installed the binaries like this:
$ wget https://downloads.wkhtmltopdf.org/0.12/0.12.5/wkhtmltox-0.12.5-1.centos7.x86_64.rpm
$ rpm -Uvh wkhtmltox-0.12.5-1.centos7.x86_64.rpm
$ which wkhtmltopdf
/usr/local/bin/wkhtmltopdf
Thanks to #Rup in comments who helped me with this.
For those who are using Cloud Linux and need to install the latest version (now 12.6) - you might get dependancy errors using the above method.
I used:
yum install -y https://github.com/wkhtmltopdf/packaging/releases/download/0.12.6-1/wkhtmltox-0.12.6-1.centos7.x86_64.rpm
Based on suggestion by ashkulz on Github
I am trying to install MarkLogic-RHEL6-8.0-5.x86_64.rpm on CENTos7 - and getting this error:
[root#localhost marklogic]# rpm -i MarkLogic-RHEL6-8.0-5.x86_64.rpm
error: Failed dependencies:
libsasl2.so.2()(64bit) is needed by MarkLogic-8.0-5.x86_64
libc.so.6(GLIBC_2.11) is needed by MarkLogic-8.0-5.x86_64
Could not find any way to resolve this using yum or any other way.
OS version is:
[root#localhost marklogic]# cat /etc/*elease
CentOS Linux release 7.2.1511 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="centos.org/";
BUG_REPORT_URL="bugs.centos.org/";
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
CentOS Linux release 7.2.1511 (Core)
CentOS Linux release 7.2.1511 (Core)
Thanks in advance - help would be appreciated.
You used the installer for Red Hat 6 / CentOS 6. Try the one for Red Hat Enterprise Linux, Version 7: http://developer.marklogic.com/products
HTH!
RHEL 7 uses the newer libsasl2.so.3. However, MarkLogic requires libsasl2.so.2. Unfortunately there is no symlink to libsasl2.so.2 by default.
For MarkLogic 8 on RHEL 7x and CentOS 7x, you need to manually create a symbolic link in /usr/lib64
/usr/lib64/libsasl2.so.2 --> /usr/lib64/[your sasl version - mine is libsasl2.so.3.0.0]