In a loop: libpq.so dependency

[vjoomens]

Hi,

After release 1.4.8 of the upgrade tool I've finally been able to do a full conversion form Centos 7 to Almaliniux 8.1

Only 1 issue remains.

After the upgrade, the plesk services failed to start. This was due to the presence of the libpq.so library. After removal of library postgresql10-libs-10.23-1PGDG.rhel7.x86_64 and a reboot, all seems to work fine.

So I tried removing all postgres packages before starting the upgrade. Removing package postgresql10-libs-10.23-1PGDG.rhel7.x86_64 failed because of dependencies. Force removing the package resulted in failure running the upgrade tool @ 16.18.

Please advise.

[SandakovMM]

Hi @vjoomens
You can try removing PostgreSQL as a Plesk component using the plesk installer.

By the way, could you please share the feedback archive generated after the conversion with the issue? Maybe I will be able to figure out how to avoid problem on the tool side.

[vjoomens]

@SandakovMM funny thing, Plesk says PostgreSQL is not installed:

So I remove all binaries before starting the upgrade with yum remove. Unfortunately I cannot remove PostgreSQL libs, there are many dependencies with plesk binaries.

[vjoomens]

@SandakovMM all seems to be running well, but the pre-upgrade stops here:

2025-05-26 17:19:39,271 - DEBUG - Invoking action 'pause before reboot'
2025-05-26 17:19:39,271 - INFO - Do: pause before reboot
2025-05-26 17:19:39,273 - ERROR - Failed: pause before reboot. The reason: [Errno 5] Input/output error
2025-05-26 17:19:39,275 - DEBUG - Going to write json '/usr/local/psa/var/centos2alma/actions.json' with new data
2025-05-26 17:19:39,281 - INFO - Unable to obtain lockfile '/usr/local/psa/var/centos2alma/centos2alma.lock': [Errno 5] Input/output error
2025-05-26 17:19:39,347 - INFO - Going to free lockfile '/usr/local/psa/var/centos2alma/centos2alma.lock'...

I then do a manual reboot. The process continues...

I have removed all (but 1) postgres library before doing the upgrade. After the upgrade, the remaining library was gone!

And the upgrade completses successfully.

[vjoomens]

@SandakovMM when doing a full yum update before running the centos2alma tool, I now get this error:

https://dlm.mariadb.com/repo/mariadb-server/10.11/yum/rhel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Proberen andere mirror...
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (MariaDB Server),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=mariadb-main ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable mariadb-main
        or
            subscription-manager repos --disable=mariadb-main

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=mariadb-main.skip_if_unavailable=true

failure: repodata/repomd.xml from mariadb-main: [Errno 256] No more mirrors to try.
https://dlm.mariadb.com/repo/mariadb-server/10.11/yum/rhel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

I ifxed it for now with this command:

yum-config-manager --save --setopt=mariadb-main.skip_if_unavailable=true

Please advise if this is OK. Or do I need to change the repo?

[SandakovMM]

Hay @vjoomens,
I'm not entirely sure whether this setup will pass the pre-checks without issues. I’ll try to verify it in the next few days. In the meantime, please let me know if check that before me.

Also, I noticed that the MariaDB 10.11 repository is available for RHEL 8 (https://dlm.mariadb.com/repo/mariadb-server/10.11/yum/rhel/8/x86_64/repodata/repomd.xml) , so it’s likely that Leapp will be able to retrieve the necessary packages and proceed with the conversion.

[vjoomens]

@SandakovMM it looks like I have a successful upgrade! I will run some more tests the coming days and have scheduled the final upgrade this weekend.

Or do you have an update for the tool coming up?

[SandakovMM]

Or do you have an update for the tool coming up?

Yes, I’m planning to release a new version of the tool by next Wednesday