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. MaximilianKohler

    MaximilianKohler Member

    197
    5
    18
    Jun 23, 2023
    Ratings:
    +29
    Local Time:
    3:41 AM
    Discussion about the system requirements continued here https://community.centminmod.com/th...8-migrations-and-resource-requirements.24324/

    I decided to try again with a 3 vCPU, 4 GB RAM server since Elevate added EPEL repo support.

    For “nano /etc/centminmod/custom_config.inc” I removed “NGINX_VERSION='1.25.3'” because I don’t know why it’s necessary.

    During the php reinstall I noticed a bunch of
    Code:
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libcrypto.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libcrypto.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    /opt/rh/gcc-toolset-11/root/usr/bin/ld: warning: libssl.so.10, needed by /lib/../lib64/libc-client.so, may conflict with libssl.so.1.1
    
    I could post the logs, but since Eva said the recommended method will always be data migration, not Elevated, I'll probably just ignore Elevated.

    Everything so far has been the same as the first time, but after the php reinstall php-fpm is now running (unlike last time), but psql still doesn't work:
    Code:
    service php-fpm status
    psql
    -bash: psql: command not found
    
    Out of curiosity, I checked to see if firewalld was installed. On CentOS 7:
    Code:
    systemctl status firewalld
    ● firewalld.service
       Loaded: masked (/dev/null; bad)
       Active: inactive (dead)
    
    Almalinux after Elevating:
    Code:
    systemctl status firewalld
    ● firewalld.service
       Loaded: masked (Reason: Unit firewalld.service is masked.)
       Active: inactive (dead)
    
    I created a snapshot and the disk size doubled again, from 4 GB prior to Elevating, to 8 GB after.


    Postgres would have to be enabled for me to test listmonk. Would there be some simple commands that I could change the name of an existing vhost, or copy the contents to a new one? IE: current forum is forum.mydomain.com. If I could move the data over to a testforum.mydomain.com I could check if it seems to be working.
     
    Last edited: Dec 9, 2023