Search results

It looks like 1.4.0 has been released. I will test to see if that fixes things.

Someone is looking at this and responded to a GitHub issue I created on this: "It seems we are using new packages from the elevate repositories that are not compatible with leapp 0.14, which we have pinned. I will fix this and recreate the latest release wit the fix."

Uh, oh. On a test server, before going to production, I was able to get it to work a few days ago. But in another test run, I got this error: 2024-08-08 15:22:17,030 - INFO - Installing: python2-leapp-0.16.0-2.el7.noarch (elevate) 2024-08-08 15:22:17,030 - INFO - python2-leapp = 0.16.0-2.el7...

I found that modsec was running a custom configuration. I was able to get Apache to start after switching it to a standard configuration. I am going to go through the whole process again on Monday on the test server.

I was unable to get apache to restart after the conversion. I get these error messages from the Diagnose & Repair: error There is a disabled required Apache module: mpm_event error There is a disabled required Apache module: mpm_prefork error There is a disabled required Apache module...