Welcome to Centmin Mod Community
Register Now

Elevated CentMinMod Stack from EL7 TO EL8 [How We DID]

Discussion in 'Install & Upgrades or Pre-Install Questions' started by brijendrasial, Nov 21, 2023.

  1. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    Hello Members,

    Today we elevated one of our centminmod stack server running centos7 to almalinux8. The stack successfully upgraded and websites are running on it. Remember we did that on our test server not on production. The server is VPS. We are still finding out how it performs and if there is some modules missing. The guide is based on instruction from https://wiki.almalinux.org/elevate/ELevate-quickstart-guide.html
    NOTE: This elevate was done on VPS

    1) We upgraded the system and rebooted it.

    Code:
    yum update -y
    reboot
    2) Next We installed elevate latest repo

    Code:
    yum install -y http://repo.almalinux.org/elevate/elevate-release-latest-el$(rpm --eval %rhel).noarch.rpm
    3) Installed leapp packages


    Code:
    yum install -y leapp-upgrade leapp-data-almalinux
    4) Did preupgrade checkup

    Code:
    leapp preupgrade
    While doing preupgrade checkup we found the below error

    Code:
    cat /var/log/leapp/answerfile
    Code:
    [remove_pam_pkcs11_module_check]
    # Title:           None
    # Reason:         Confirmation
    # =================== remove_pam_pkcs11_module_check.confirm ==================
    # Label:           Disable pam_pkcs11 module in PAM configuration? If no, the upgrade process will be interrupted.
    # Description:     PAM module pam_pkcs11 is no longer available in RHEL-8 since it was replaced by SSSD.
    # Type:           bool
    # Default:         None
    # Available choices: True/False
    # Unanswered question. Uncomment the following line with your answer
    # confirm =
    We confirmed the removal of module.

    Code:
    leapp answer --section remove_pam_pkcs11_module_check.confirm=True
    To proceed with the upgrade we have to uninstall the module as they were conflicting.

    Code:
    yum remove libwebp7 cmake3 bash-completion -y
    5) We are all set. Now lets upgrade

    Code:
    leapp upgrade
    6) Once the upgrade is completed we rebooted the system.

    Code:
    reboot
    7) You will see system will be rebooted with new kernel and OS. Now lets add almalinux installation files for centminmod.

    Code:
    cd /usr/local/src
    mv centminmod centminmod.old
    git clone -b 130.00beta01 --depth=5 https://github.com/centminmod/centminmod.git centminmod
    8) Setup below or you can skip it.

    Code:
    vi /etc/centminmod/custom_config.inc
    Code:
    CENTOS_ALPHATEST='y'
    NGINX_VERSION='1.25.3'
    NGINX_ONETWOTHREE_COMPAT='y'
    DEVTOOLSETTEN='n'
    DEVTOOLSETELEVEN='y'
    SELFSIGNEDSSL_ECDSA='y'
    PHPFINFO='y'

    9) Deleted old epel repository and reinstalled it.

    Code:
    rm -rf /etc/yum.repos.d/epel.repo
    yum reinstall epel-release -y
    10) Installed GeoIP for nginx to work properly.

    Code:
    yum install GeoIP GeoIP-devel -y
    cp -a /usr/share/GeoIP/GeoLiteCity.dat /usr/share/GeoIP/GeoIPCity.dat
    11) Now recompile nginx and php with option 4 and 5.
    Code:
    centmin
    At the end of compilation nginx and php-fpm started working fine.

    Lets reinstall mariadb

    Code:
    rm -rf /etc/yum.repos.d/mariadb.repo
    Code:
    vi /etc/yum.repos.d/mariadb.repo
    Code:
    [mariadb]
    name = MariaDB
    baseurl = http://yum.mariadb.org/10.5/rhel8-amd64
    module_hotfixes=1
    gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
    gpgcheck=1
    Code:
    yum install MariaDB-server MariaDB-shared MariaDB-client MariaDB-common galera -y
    Code:
    systemctl start mariadb
    systemctl status mariadb
    mysql_upgrade
    Now I added bash-completion package again.

    Code:
    dnf install bash-completion -y
    Our machine is working fine with the test site deployed on it. We are looking more if something is missing or broken. I will keep you updated.

    UPDATE: Pure-ftp was missing after upgrade. Ran centmin to fix its configuration

    Code:
    dnf install pure-ftpd -y
    systemctl start pure-ftpd
    systemctl status pure-ftpd
    centmin
    
    UPDATE: Running centmin was giving below error.
    Code:
    /usr/local/bin/pcretest: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
    /usr/local/bin/pcretest: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
    We recompiled pcre

    Code:
    cd /usr/local/src
    wget https://centminmod.com/centminmodparts/pcre/pcre-8.45.tar.gz
    tar zxvf pcre-8.45.tar.gz
    cd pcre-8.45
    ./configure --enable-utf8 --enable-unicode-properties --enable-pcre16 --enable-pcre32 --enable-pcregrep-libz --enable-pcregrep-libbz2 --enable-pcretest-libreadline --enable-jit
    make
    make install
    /usr/local/bin/pcre-config --version
     
    Last edited: Nov 21, 2023
  2. MaximilianKohler

    MaximilianKohler Member

    157
    3
    18
    Jun 23, 2023
    Ratings:
    +18
    Local Time:
    9:13 PM
  3. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    well yes I installed almalinux 8 on top of centos7. We are testing the elevated system. For now it seems stable but we will update the thread on more findings.
     
  4. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    Everything looks good and working perfectly fine.
     
  5. eva2000

    eva2000 Administrator Staff Member

    52,169
    11,995
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,498
    Local Time:
    2:13 PM
    Nginx 1.25.x
    MariaDB 10.x
    Wow thanks for sharing @brijendrasial interesting adventures. I haven't had the free time to try this myself yet so thanks :D
     
  6. OxaByte

    OxaByte New Member

    2
    2
    3
    Jun 28, 2020
    Ratings:
    +2
    Local Time:
    9:43 AM
    thanks I tried it actually works. thanks for this tutorial
     
  7. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    @OxaByte in case of any issue let me know.
     
  8. MaximilianKohler

    MaximilianKohler Member

    157
    3
    18
    Jun 23, 2023
    Ratings:
    +18
    Local Time:
    9:13 PM
    I followed your directions on a test server and I got the same error you did, but also an extra one (Multiple devel kernels installed) that seems to have caused it to fail:
    Code:
    leapp preupgrade
    
    ============================================================
                         UPGRADE INHIBITED
    ============================================================
    
    Upgrade has been inhibited due to the following problems:
        1. Inhibitor: Multiple devel kernels installed
        2. Inhibitor: Missing required answers in the answer file
    Consult the pre-upgrade report for details and possible remediation.
    
    ============================================================
                         UPGRADE INHIBITED
    ============================================================
    
    
    Debug output written to /var/log/leapp/leapp-preupgrade.log
    
    ============================================================
                               REPORT
    ============================================================
    
    A report has been generated at /var/log/leapp/leapp-report.json
    A report has been generated at /var/log/leapp/leapp-report.txt
    
    ============================================================
                           END OF REPORT
    ============================================================
    
    Answerfile has been generated at /var/log/leapp/answerfile
    
    Code:
    cat /var/log/leapp/answerfile
    [remove_pam_pkcs11_module_check]
    # Title:              None
    # Reason:             Confirmation
    # =================== remove_pam_pkcs11_module_check.confirm ==================
    # Label:              Disable pam_pkcs11 module in PAM configuration? If no, the upgrade process will be interrupted.
    # Description:        PAM module pam_pkcs11 is no longer available in RHEL-8 since it was replaced by SSSD.
    # Reason:             Leaving this module in PAM configuration may lock out the system.
    # Type:               bool
    # Default:            None
    # Available choices: True/False
    # Unanswered question. Uncomment the following line with your answer
    # confirm =
    
    
    Code:
    leapp answer --section remove_pam_pkcs11_module_check.confirm=True
    I checked it with
    Code:
    nano /var/log/leapp/answerfile
    Code:
    yum remove libwebp7 cmake3 bash-completion -y
    leapp upgrade
    
    2023-11-21 16:35:04.614 ERROR    PID: 25215 leapp:
    ============================================================
                         UPGRADE INHIBITED
    ============================================================
    
    2023-11-21 16:35:04.615 ERROR    PID: 25215 leapp: Upgrade has been inhibited due to the following problems:
    2023-11-21 16:35:04.617 ERROR    PID: 25215 leapp:     1. Inhibitor: Multiple devel kernels installed
    
    ============================================================
                         UPGRADE INHIBITED
    ============================================================
    
    Upgrade has been inhibited due to the following problems:
        1. Inhibitor: Multiple devel kernels installed
    Consult the pre-upgrade report for details and possible remediation.
    
    ============================================================
                         UPGRADE INHIBITED
    ============================================================
    
    
    Debug output written to /var/log/leapp/leapp-upgrade.log
    
    ============================================================
                               REPORT
    ============================================================
    
    A report has been generated at /var/log/leapp/leapp-report.json
    A report has been generated at /var/log/leapp/leapp-report.txt
    
    ============================================================
                           END OF REPORT
    ============================================================
    
    Answerfile has been generated at /var/log/leapp/answerfile
    2023-11-21 16:35:04.645 ERROR    PID: 25215 leapp: Upgrade workflow failed, check log for details
    
    Code:
    cat /var/log/leapp/answerfile
    [remove_pam_pkcs11_module_check]
    # Title:              None
    # Reason:             Confirmation
    # =================== remove_pam_pkcs11_module_check.confirm ==================
    # Label:              Disable pam_pkcs11 module in PAM configuration? If no, the upgrade process will be interrupted.
    # Description:        PAM module pam_pkcs11 is no longer available in RHEL-8 since it was replaced by SSSD.
    # Reason:             Leaving this module in PAM configuration may lock out the system.
    # Type:               bool
    # Default:            None
    # Available choices: True/False
    confirm = True
    
     
  9. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    did you reboot the server after installing new kernel?
     
  10. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    or you need to remove old kernel to upgrade.
     
  11. MaximilianKohler

    MaximilianKohler Member

    157
    3
    18
    Jun 23, 2023
    Ratings:
    +18
    Local Time:
    9:13 PM
    I have it set up to notify me when a reboot is needed for a new kernal. I just rebooted anyway and ran "leapp preupgrade", and got the same "Inhibitor: Multiple devel kernels installed" warning.

    Here's what leapp-report.txt says:
    Code:
    Risk Factor: high (inhibitor)
    Title: Multiple devel kernels installed
    Summary: DNF cannot produce a valid upgrade transaction when multiple kernel-devel packages are installed.
    Remediation: [hint] Remove all but one kernel-devel packages before running Leapp again.
    [command] yum -y remove kernel-devel-3.10.0-1160.92.1.el7 kernel-devel-3.10.0-1160.99.1.el7 kernel-devel-3.10.0-1160.95.1.el7
    Key:
    ----------------------------------------
    Risk Factor: high
    Title: Packages from unknown repositories may not be installed
    Summary: 1 packages may not be installed or upgraded due to repositories unknown to leapp:
    - kernel-uek (repoid: ol8-uek)
    Remediation: [hint] Please file a bug in http://bugzilla.redhat.com/ for leapp-repository component of the Red Hat Enterprise Linux product.
    Key:
    ----------------------------------------
    Risk Factor: high
    Title: Packages not signed by Red Hat found on the system
    Summary: The following packages have not been signed by Red Hat and may be removed during the upgrade process in case Red Hat-signed packages to be removed during the upgrade depend on them:
    - MariaDB-client
    - MariaDB-common
    - MariaDB-compat
    - MariaDB-devel
    - MariaDB-server
    - MariaDB-shared
    - centmin-libatomic_ops
    - clang
    - clang-devel
    - containerd.io
    - datamash
    - docker-buildx-plugin
    - docker-ce
    - docker-ce-cli
    - docker-ce-rootless-extras
    - docker-compose-plugin
    - elevate-release
    - epel-release
    - figlet
    - galera-4
    - gpg-pubkey
    - haveged
    - hc-utils
    - iftop
    - ius-release
    - jemalloc
    - jemalloc-devel
    - jpegoptim
    - jq
    - leapp
    - leapp-data-almalinux
    - leapp-deps
    - leapp-upgrade-el7toel8
    - leapp-upgrade-el7toel8-deps
    - libc-client
    - libicu62
    - libicu62-devel
    - libimagequant
    - liblzf
    - liblzf-devel
    - libmcrypt
    - libmcrypt-devel
    - libnghttp2
    - libnghttp2-devel
    - libpq5
    - libpq5-devel
    - libraqm
    - libtidy
    - libtidy-devel
    - libuv
    - libzstd
    - libzstd-devel
    - llvm
    - llvm-libs
    - llvm5.0
    - llvm5.0-devel
    - llvm5.0-libs
    - moreutils
    - mytop
    - nghttp2
    - oniguruma
    - oniguruma5php
    - oniguruma5php-devel
    - pbzip2
    - percona-release
    - perl-Time-Duration
    - pgdg-redhat-repo
    - pigz
    - pngquant
    - postgresql15
    - postgresql15-contrib
    - postgresql15-devel
    - postgresql15-libs
    - postgresql15-server
    - pure-ftpd
    - pwgen
    - pxz
    - python2-leapp
    - python2-pip
    - re2c
    - redis
    - remi-release
    - rhash
    - rpmforge-release
    - smem
    - uw-imap-devel
    - xxhash
    - xxhash-devel
    - xxhash-libs
    - zstd
    Key:
    ----------------------------------------
    Risk Factor: high
    Title: Difference in Python versions and support in RHEL 8
    Summary: In RHEL 8, there is no 'python' command. Python 3 (backward incompatible) is the primary Python version and Python 2 is available with limited support and limited set of packages. Read more here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_basic_system_settings/#using-python3
    Remediation: [hint] Please run "alternatives --set python /usr/bin/python3" after upgrade
    Key:
    ----------------------------------------
    Risk Factor: high
    Title: GRUB core will be updated during upgrade
    Summary: On legacy (BIOS) systems, GRUB core (located in the gap between the MBR and the first partition) does not get automatically updated when GRUB is upgraded.
    Key:
    ----------------------------------------
    Risk Factor: medium
    Title: Module pam_pkcs11 will be removed from PAM configuration
    Summary: Module pam_pkcs11 was surpassed by SSSD and therefore it was removed from RHEL-8. Keeping it in PAM configuration may lock out the system thus it will be automatically removed from PAM configuration before upgrading to RHEL-8. Please switch to SSSD to recover the functionality of pam_pkcs11.
    Remediation: [hint] Configure SSSD to replace pam_pkcs11
    Key:
    ----------------------------------------
    Risk Factor: low
    Title: Postfix has incompatible changes in the next major version
    Summary: Postfix 3.x has so called "compatibility safety net" that runs Postfix programs with backwards-compatible default settings. It will log a warning whenever backwards-compatible default setting may be required for continuity of service. Based on this logging the system administrator can decide if any backwards-compatible settings need to be made permanent in main.cf or master.cf, before turning off the backwards-compatibility safety net.
    The backward compatibility safety net is by default turned off in Red Hat Enterprise Linux 8.
    It can be turned on by running:  "postconf -e compatibility_level=0
    It can be turned off by running: "postconf -e compatibility_level=2
    
    In the Postfix MySQL database client, the default "option_group" value has changed to "client", i.e. it now reads options from the [client] group from the MySQL configuration file. To disable it, set "option_group" to the empty string.
    
    The postqueue command no longer forces all message arrival times to be reported in UTC. To get the old behavior, set TZ=UTC in main.cf:import_environment.
    
    Postfix 3.2 enables elliptic curve negotiation. This changes the default smtpd_tls_eecdh_grade setting to "auto", and introduces a new parameter "tls_eecdh_auto_curves" with the names of curves that may be negotiated.
    
    The "master.cf" chroot default value has changed from "y" (yes) to "n" (no). This applies to master.cf services where chroot field is not explicitly specified.
    
    The "append_dot_mydomain" default value has changed from "yes" to "no". You may need changing it to "yes" if senders cannot use complete domain names in e-mail addresses.
    
    The "relay_domains" default value has changed from "$mydestination" to the empty value. This could result in unexpected "Relay access denied" errors or ETRN errors, because now will postfix by default relay only for the localhost.
    
    The "mynetworks_style" default value has changed from "subnet" to "host". This parameter is used to implement the "permit_mynetworks" feature. The change could result in unexpected "access denied" errors, because postfix will now by default trust only the local machine, not the remote SMTP clients on the same IP subnetwork.
    
    Postfix now supports dynamically loaded database plugins. Plugins are shipped in individual RPM sub-packages. Correct database plugins have to be installed, otherwise the specific database client will not work. For example for PostgreSQL map to work, the postfix-pgsql RPM package has to be installed.
    
    Key:
    ----------------------------------------
    Risk Factor: low
    Title: Grep has incompatible changes in the next major version
    Summary: If a file contains data improperly encoded for the current locale, and this is discovered before any of the file's contents are output, grep now treats the file as binary.
    The 'grep -P' no longer reports an error and exits when given invalid UTF-8 data. Instead, it considers the data to be non-matching.
    In locales with multibyte character encodings other than UTF-8, grep -P now reports an error and exits instead of misbehaving.
    When searching binary data, grep now may treat non-text bytes as line terminators. This can boost performance significantly.
    The 'grep -z' no longer automatically treats the byte '\200' as binary data.
    Context no longer excludes selected lines omitted because of -m. For example, 'grep "^" -m1 -A1' now outputs the first two input lines, not just the first line.
    
    Remediation: [hint] Please update your scripts to be compatible with the changes.
    Key:
    ----------------------------------------
    Risk Factor: low
    Title: Dosfstools incompatible changes in the next major version
    Summary: The automatic alignment of data clusters that was added in 3.0.8 and broken for FAT32 starting with 3.0.20 has been reinstated. If you need to create file systems for finicky devices that have broken FAT implementations use the option -a to disable alignment.
    The fsck.fat now defaults to interactive repair mode which previously had to be selected with the -r option.
    
    Remediation: [hint] Please update your scripts to be compatible with the changes.
    Key:
    ----------------------------------------
    Risk Factor: low
    Title: Some enabled RPM repositories are unknown to Leapp
    Summary: The following repositories with Red Hat-signed packages are unknown to Leapp:
    - centos-sclo-rh
    And the following packages installed from those repositories may not be upgraded:
    - devtoolset-7-gcc-c++
    - llvm-toolset-7-runtime
    - devtoolset-10-gcc-c++
    - devtoolset-10-runtime
    - llvm-toolset-7-compiler-rt
    - devtoolset-7-runtime
    - devtoolset-10-libstdc++-devel
    - llvm-toolset-7-clang-libs
    - devtoolset-10-gcc
    - llvm-toolset-7-clang
    - llvm-toolset-7-libomp
    - devtoolset-7-gcc
    - devtoolset-10-binutils
    - devtoolset-7-binutils
    - devtoolset-7-libstdc++-devel
    - llvm-toolset-7-llvm-libs
    Remediation: [hint] You can file a request to add this repository to the scope of in-place upgrades by filing a support ticket
    Key:
    ----------------------------------------
    Risk Factor: low
    Title: chrony using non-default configuration
    Summary: chrony behavior will not change in RHEL8
    Key:
    ----------------------------------------
    Risk Factor: info
    Title: Current PAM and nsswitch.conf configuration will be kept.
    Summary: There is a new tool called authselect in RHEL8 that replaced authconfig. The upgrade process was unable to find an authselect profile that would be equivalent to your current configuration. Therefore your configuration will be left intact.
    Key:
    ----------------------------------------
    Risk Factor: info
    Title: SElinux disabled
    Summary: SElinux disabled, continuing...
    Key:
    ----------------------------------------
    
    I guess I run this command:
    Code:
    yum -y remove kernel-devel-3.10.0-1160.92.1.el7 kernel-devel-3.10.0-1160.99.1.el7 kernel-devel-3.10.0-1160.95.1.el7
    I wasn't sure if I needed to remove one of the kernals listed so that the command only removes 2 of them. But I ran it with all 3 and then proceeded with "leapp preupgrade" and "leapp upgrade" and got a pass.

    I see stuff like postgresql15 possibly being removed, so I'll probably wait for eva to look everything over before trying it on a production server.

    Code:
    vi /etc/centminmod/custom_config.inc
    I've never seen this command before, and it didn't allow me to edit the file the same as "nano". So I used nano instead and added the lines to my existing config:
    Code:
    MARCH_TARGETNATIVE='n'
    LETSENCRYPT_DETECT='y'
    VHOSTCTRL_CLOUDFLAREINC='y'
    NGINX_ZERODT='y'
    PHP_PGO='y'
    
    NGINX_ZERODT='y'
    
    ENABLE_MARIADBTENTWOUPGRADE='y'
    ENABLE_MARIADBTENTHREEUPGRADE='y'
    ENABLE_MARIADBTENFOURUPGRADE='y'
    
    NEEDRESTART_CHECK='y'
    POSTGRESQL='y'
    
    CENTOS_ALPHATEST='y'
    NGINX_VERSION='1.25.3'
    NGINX_ONETWOTHREE_COMPAT='y'
    DEVTOOLSETTEN='n'
    DEVTOOLSETELEVEN='y'
    SELFSIGNEDSSL_ECDSA='y'
    PHPFINFO='y'
    
    Everything seemed fine till "11) Now recompile nginx and php with option 4 and 5". Then nginx seemed to get stuck:
    Code:
    Success: Nginx make ok
    
    cat: /usr/local/nginx/logs/nginx.pid: No such file or directory
    ---------------------------------------------------------------------------
    nginx master id:
    
    ---------------------------------------------------------------------------
    ---------------------------------------------------------------------------
      PID  PPID USER     %CPU    VSZ WCHAN  COMMAND
    ---------------------------------------------------------------------------
                _   _         _                __  __         _
               | \ | |  __ _ (_) _ __  __  __ |  \/  |  __ _ | | __ ___
               |  \| | / _` || || '_ \ \ \/ / | |\/| | / _` || |/ // _ \
               | |\  || (_| || || | | | >  <  | |  | || (_| ||   <|  __/
               |_| \_| \__, ||_||_| |_|/_/\_\ |_|  |_| \__,_||_|\_\\___|
                       |___/
                            ___              _          _  _
                           |_ _| _ __   ___ | |_  __ _ | || |
                            | | | '_ \ / __|| __|/ _` || || |
                            | | | | | |\__ \| |_| (_| || || |
                           |___||_| |_||___/ \__|\__,_||_||_|
    
    Tue Nov 21 19:50:33 UTC 2023
    Success: Nginx was installed properly
    
    
    ---------------------------------------------------------------------------
    nginx master id:
    ---------------------------------------------------------------------------
    ---------------------------------------------------------------------------
    kill -USR2
    kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
      PID  PPID USER     %CPU    VSZ WCHAN  COMMAND
    
    -rwxr-xr-x 1 root root 4.7M Nov 21 19:50 /usr/local/sbin/nginx
    -rwxr-xr-x 1 root root 4.7M Oct 24 22:01 /usr/local/sbin/nginx.old
    ---------------------------------------------------------------------------
    ---------------------------------------------------------------------------
    kill -WINCH
    kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
      PID  PPID USER     %CPU    VSZ WCHAN  COMMAND
    ---------------------------------------------------------------------------
    ---------------------------------------------------------------------------
     waiting for old nginx worker processes to exit...
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
     checking... worker child PPID= exists
    ^C[20:01][root@centos7test src]#
    
    FYI, "current nginx version" was blank when I first opened the CLI after updating to AlmaLinux:
    Code:
    ===============================================================================
    * Nginx Update May Be Available via centmin.sh menu option 4
    * see https://centminmod.com/nginx.html#nginxupgrade
    ===============================================================================
    * Current Nginx Version:
    * Latest Nginx Mainline Available: 1.25.3 (centminmod.com/nginxnews)
    ===============================================================================
    
    ===============================================================================
     Centmin Mod local code is up to date at /usr/local/src/centminmod
     no available updates at this time...
    ===============================================================================
    
    After manually exiting from the "waiting for old nginx worker processes to exit" prompts, I opened up a new window to check if the nginx version still showed as blank and it didn't.
    Code:
    nginx -v
    nginx version: nginx/1.25.3 (211123-194743-almalinux8-kvm-851925b)
    
    I also got the centmin menu error, and fixed it later on with your commands.
    Code:
    centmin
    /usr/local/src/centminmod /usr/local/src
    
    /usr/local/bin/pcretest: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
    /usr/local/bin/pcretest: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
    
    I continued with the PHP reinstall, and the rest of it and everything seemed fine.

    I tried to load this docker test website, and it said "connection refused". After running ngxrestart it loaded.
     
  12. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    I see you have successfully upgraded though. Are you facing any issue now?
     
  13. MaximilianKohler

    MaximilianKohler Member

    157
    3
    18
    Jun 23, 2023
    Ratings:
    +18
    Local Time:
    9:13 PM
    Not that I know of. I did it on a test server that's a clone of my production which only has a forum. I haven't tried to get the forum running on the test server. I've been trying to get a Listmonk email server running, and it seems to be in the same state as prior to upgrading to AlmaLinux.
     
  14. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    I see please do a staging on test server and verify.
     
  15. MaximilianKohler

    MaximilianKohler Member

    157
    3
    18
    Jun 23, 2023
    Ratings:
    +18
    Local Time:
    9:13 PM
    I'm a noob and I don't see a simple guide. Via search, I see your Wordpress script, and this link from eva that's complicated. I made my test server by creating a new server from a snapshot. That was easy, but I can't think of a simple way to get a 2nd forum running.

    EDIT: looks like postgresql got uninstalled:
    Code:
    psql
    -bash: psql: command not found
    
    postgres --version
    -bash: postgres: command not found
    
    Code:
    locate bin/postgres
    /usr/bin/postgresql-15-setup
    /usr/pgsql-15/bin/postgres
    /usr/pgsql-15/bin/postgresql-15-check-db-dir
    /usr/pgsql-15/bin/postgresql-15-setup
    /var/lib/docker/overlay2/c2df15efdae9a641a2b73f7ff5e538701db7950f737e2679292740cba6e211c4/diff/usr/lib/postgresql/13/bin/postgres
    
    locate bin/psql
    /usr/bin/psql
    /usr/pgsql-15/bin/psql
    /var/lib/docker/overlay2/c2df15efdae9a641a2b73f7ff5e538701db7950f737e2679292740cba6e211c4/diff/usr/bin/psql
    /var/lib/docker/overlay2/c2df15efdae9a641a2b73f7ff5e538701db7950f737e2679292740cba6e211c4/diff/usr/lib/postgresql/13/bin/psql
    
    yum -q list postgresql* | tr -s ' ' | column -t
    Installed                                Packages
    postgresql15-libs.x86_64                 15.5-1PGDG.rhel7        @System
    Available                                Packages
    postgresql-jdbc.noarch                   42.7.0-1PGDG.rhel8      pgdg-common
    postgresql-jdbc-javadoc.noarch           42.7.0-1PGDG.rhel8      pgdg-common
    postgresql-odbc.x86_64                   10.03.0000-3.el8_6      appstream
    postgresql-odbc-tests.x86_64             10.03.0000-3.el8_6      appstream
    postgresql-unit11.x86_64                 7.2-1.rhel8             pgdg11
    postgresql-unit12.x86_64                 7.2-1.rhel8.1           pgdg12
    postgresql-unit13.x86_64                 7.2-1.rhel8.1           pgdg13
    postgresql-unit_11.x86_64                7.4-1.rhel8             pgdg11
    postgresql-unit_12.x86_64                7.4-1.rhel8             pgdg12
    postgresql-unit_13.x86_64                7.4-1.rhel8             pgdg13
    postgresql-unit_14.x86_64                7.4-1.rhel8             pgdg14
    postgresql-unit_15.x86_64                7.4-1.rhel8             pgdg15
    postgresql11.x86_64                      11.22-2PGDG.rhel8       pgdg11
    postgresql11-contrib.x86_64              11.22-2PGDG.rhel8       pgdg11
    postgresql11-devel.x86_64                11.22-2PGDG.rhel8       pgdg11
    postgresql11-docs.x86_64                 11.22-2PGDG.rhel8       pgdg11
    postgresql11-libs.x86_64                 11.22-2PGDG.rhel8       pgdg11
    postgresql11-llvmjit.x86_64              11.22-2PGDG.rhel8       pgdg11
    postgresql11-odbc.x86_64                 16.00.0000-1PGDG.rhel8  pgdg11
    postgresql11-plperl.x86_64               11.22-2PGDG.rhel8       pgdg11
    postgresql11-plpython.x86_64             11.22-2PGDG.rhel8       pgdg11
    postgresql11-plpython3.x86_64            11.22-2PGDG.rhel8       pgdg11
    postgresql11-pltcl.x86_64                11.22-2PGDG.rhel8       pgdg11
    postgresql11-server.x86_64               11.22-2PGDG.rhel8       pgdg11
    postgresql11-tcl.x86_64                  3.0.0-1.rhel8           pgdg11
    postgresql11-test.x86_64                 11.22-2PGDG.rhel8       pgdg11
    postgresql12.x86_64                      12.17-2PGDG.rhel8       pgdg12
    postgresql12-contrib.x86_64              12.17-2PGDG.rhel8       pgdg12
    postgresql12-devel.x86_64                12.17-2PGDG.rhel8       pgdg12
    postgresql12-docs.x86_64                 12.17-2PGDG.rhel8       pgdg12
    postgresql12-libs.x86_64                 12.17-2PGDG.rhel8       pgdg12
    postgresql12-llvmjit.x86_64              12.17-2PGDG.rhel8       pgdg12
    postgresql12-odbc.x86_64                 16.00.0000-1PGDG.rhel8  pgdg12
    postgresql12-plperl.x86_64               12.17-2PGDG.rhel8       pgdg12
    postgresql12-plpython.x86_64             12.17-2PGDG.rhel8       pgdg12
    postgresql12-plpython3.x86_64            12.17-2PGDG.rhel8       pgdg12
    postgresql12-pltcl.x86_64                12.17-2PGDG.rhel8       pgdg12
    postgresql12-server.x86_64               12.17-2PGDG.rhel8       pgdg12
    postgresql12-tcl.x86_64                  3.0.0-1.rhel8           pgdg12
    postgresql12-test.x86_64                 12.17-2PGDG.rhel8       pgdg12
    postgresql13.x86_64                      13.13-2PGDG.rhel8       pgdg13
    postgresql13-contrib.x86_64              13.13-2PGDG.rhel8       pgdg13
    postgresql13-devel.x86_64                13.13-2PGDG.rhel8       pgdg13
    postgresql13-docs.x86_64                 13.13-2PGDG.rhel8       pgdg13
    postgresql13-libs.x86_64                 13.13-2PGDG.rhel8       pgdg13
    postgresql13-llvmjit.x86_64              13.13-2PGDG.rhel8       pgdg13
    postgresql13-odbc.x86_64                 16.00.0000-1PGDG.rhel8  pgdg13
    postgresql13-plperl.x86_64               13.13-2PGDG.rhel8       pgdg13
    postgresql13-plpython3.x86_64            13.13-2PGDG.rhel8       pgdg13
    postgresql13-pltcl.x86_64                13.13-2PGDG.rhel8       pgdg13
    postgresql13-server.x86_64               13.13-2PGDG.rhel8       pgdg13
    postgresql13-test.x86_64                 13.13-2PGDG.rhel8       pgdg13
    postgresql14.x86_64                      14.10-2PGDG.rhel8       pgdg14
    postgresql14-contrib.x86_64              14.10-2PGDG.rhel8       pgdg14
    postgresql14-devel.x86_64                14.10-2PGDG.rhel8       pgdg14
    postgresql14-docs.x86_64                 14.10-2PGDG.rhel8       pgdg14
    postgresql14-libs.x86_64                 14.10-2PGDG.rhel8       pgdg14
    postgresql14-llvmjit.x86_64              14.10-2PGDG.rhel8       pgdg14
    postgresql14-odbc.x86_64                 16.00.0000-1PGDG.rhel8  pgdg14
    postgresql14-plperl.x86_64               14.10-2PGDG.rhel8       pgdg14
    postgresql14-plpython3.x86_64            14.10-2PGDG.rhel8       pgdg14
    postgresql14-pltcl.x86_64                14.10-2PGDG.rhel8       pgdg14
    postgresql14-server.x86_64               14.10-2PGDG.rhel8       pgdg14
    postgresql14-tcl.x86_64                  3.0.0-1.rhel8           pgdg14
    postgresql14-test.x86_64                 14.10-2PGDG.rhel8       pgdg14
    postgresql15.x86_64                      15.5-2PGDG.rhel8        pgdg15
    postgresql15-contrib.x86_64              15.5-2PGDG.rhel8        pgdg15
    postgresql15-devel.x86_64                15.5-2PGDG.rhel8        pgdg15
    postgresql15-docs.x86_64                 15.5-2PGDG.rhel8        pgdg15
    postgresql15-libs.x86_64                 15.5-2PGDG.rhel8        pgdg15
    postgresql15-llvmjit.x86_64              15.5-2PGDG.rhel8        pgdg15
    postgresql15-odbc.x86_64                 16.00.0000-1PGDG.rhel8  pgdg15
    postgresql15-plperl.x86_64               15.5-2PGDG.rhel8        pgdg15
    postgresql15-plpython3.x86_64            15.5-2PGDG.rhel8        pgdg15
    postgresql15-pltcl.x86_64                15.5-2PGDG.rhel8        pgdg15
    postgresql15-server.x86_64               15.5-2PGDG.rhel8        pgdg15
    postgresql15-tcl.x86_64                  3.0.0-1.rhel8           pgdg15
    postgresql15-test.x86_64                 15.5-2PGDG.rhel8        pgdg15
    postgresql_anonymizer11.noarch           0.3.1-1.rhel8           pgdg11
    postgresql_anonymizer11.x86_64           0.7.1-1.rhel8           pgdg11
    postgresql_anonymizer12.noarch           0.3.1-1.rhel8.1         pgdg12
    postgresql_anonymizer12.x86_64           0.7.1-1.rhel8           pgdg12
    postgresql_anonymizer13.x86_64           0.7.1-1.rhel8           pgdg13
    postgresql_anonymizer_11.x86_64          1.1.0-5PGDG.rhel8       pgdg11
    postgresql_anonymizer_11-llvmjit.x86_64  1.1.0-5PGDG.rhel8       pgdg11
    postgresql_anonymizer_12.x86_64          1.1.0-5PGDG.rhel8       pgdg12
    postgresql_anonymizer_12-llvmjit.x86_64  1.1.0-5PGDG.rhel8       pgdg12
    postgresql_anonymizer_13.x86_64          1.1.0-5PGDG.rhel8       pgdg13
    postgresql_anonymizer_13-llvmjit.x86_64  1.1.0-5PGDG.rhel8       pgdg13
    postgresql_anonymizer_14.x86_64          1.1.0-5PGDG.rhel8       pgdg14
    postgresql_anonymizer_14-llvmjit.x86_64  1.1.0-5PGDG.rhel8       pgdg14
    postgresql_anonymizer_15.x86_64          1.1.0-5PGDG.rhel8       pgdg15
    postgresql_anonymizer_15-llvmjit.x86_64  1.1.0-5PGDG.rhel8       pgdg15
    postgresql_faker_11.noarch               0.4.0-1.rhel8           pgdg11
    postgresql_faker_11.x86_64               0.5.3-1.rhel8           pgdg11
    postgresql_faker_12.noarch               0.4.0-1.rhel8           pgdg12
    postgresql_faker_12.x86_64               0.5.3-1.rhel8           pgdg12
    postgresql_faker_13.noarch               0.4.0-1.rhel8           pgdg13
    postgresql_faker_13.x86_64               0.5.3-1.rhel8           pgdg13
    postgresql_faker_14.noarch               0.4.0-1.rhel8           pgdg14
    postgresql_faker_14.x86_64               0.5.3-1.rhel8           pgdg14
    postgresql_faker_15.x86_64               0.5.3-1.rhel8           pgdg15
    postgresqltuner.noarch                   1.0.1-4.el8             epel
    
    
    php logs https://pastebin.com/rnWgLVsu - minimal
    full https://www.dropbox.com/scl/fi/askw...rade.log?rlkey=zxc2zo281h341tw7xi4ensb31&dl=0
     
    Last edited: Nov 23, 2023
  16. brijendrasial

    brijendrasial Active Member

    201
    145
    43
    Mar 21, 2018
    Ratings:
    +227
    Local Time:
    9:43 AM
    1.13.9
    10.0.22-MariaDB
    on my vps I will test it and check.
     
  17. MaximilianKohler

    MaximilianKohler Member

    157
    3
    18
    Jun 23, 2023
    Ratings:
    +18
    Local Time:
    9:13 PM
  18. eva2000

    eva2000 Administrator Staff Member

    52,169
    11,995
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,498
    Local Time:
    2:13 PM
    Nginx 1.25.x
    MariaDB 10.x
  19. eva2000

    eva2000 Administrator Staff Member

    52,169
    11,995
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,498
    Local Time:
    2:13 PM
    Nginx 1.25.x
    MariaDB 10.x
    Just a reminder that one reason CentOS 7 to AlmaLinux 8 in place upgrades might not work is due to minimum and recommended system resource requirements. EL8 OSes will require at least 2x the memory installed to run properly.
    • CentOS 7 - min = 1GB, recommended = 2GB with 2GB swap disk
    • EL8 - min = 2GB, recommended = 4GB with 4GB swap disk
    So while you may have a CentOS 7 VPS with 1GB memory and 2GB swap, migrating in place to AlmaLinux 8 on same VPS specs won't run properly on EL8.
     
  20. buik

    buik “The best traveler is one without a camera.”

    1,965
    513
    113
    Apr 29, 2016
    Flanders
    Ratings:
    +1,632
    Local Time:
    6:13 AM
    Because most users are installing EL via an Internet ISO or image and updates via public based HTTP(s) yum repos.

    The official "Minimum required memory" is 3GB.
    Trough that is the absolutely bare minimum without (L)EMP stack.
    A CMM based server with less than 8GB memory. I wouldn't even get started on for various reasons already.