[ea-php81] PHP commands always "Aborted" after installation with EasyApache4

[Delmore]

Hello guys,

I'm using WHM on a Centos 7 with most AlmaLinux env.

Recently I wanted to upgrade my PHP version on my cPanel accounts from 8.0.12 to 8.1.2.
After following some documentation, I ended up installing the new version via EasyApache4
I disabled ea-php80 and enabled ea-php81.
Also, I switched my PHP version on each cPanels via MultiPHP Manager from 8.0 to 8.1. (with php handler cgi)
Then, I restarted my HTTP apache server via WHM back office.

Probleme is, from there, every single PHP command I try, outputs "Aborted".

I have absolutly no idea where to begin with since i don't have any other information.
I will try to find & dig up some logs.

Just strange that apache does not return a single issue.
My php.ini seems fine, and my ea-php81 too.

Thanks.

EDIT: I was so desesperate that I rebooted the server on OVH. And now my WHM won't start... PING on server works.
Should I open an other ticket for that issue ?

 

[cPRex]

Hey there! It sounds like there are more serious underlying issues with the system if cPanel is no longer able to start. It would be best to submit a ticket to our team directly so we could check the machine and see what is happening.

If you are able to submit a ticket please post the number here so I can follow along and keep this thread updated.

 

[Delmore]

If you are able to submit a ticket please post the number here so I can follow along and keep this thread updated.

I can't since I can't access my Support Access ID ... All I have is the licensed IP address & the license number

 

[quietFinn]

EDIT: I was so desesperate that I rebooted the server on OVH. And now my WHM won't start... PING on server works.

You can boot the server in rescue mode, you might see what is the problem.
How do you know that WHM won't start? Can you connect using SSH?

 

[cPRex]

You can always email [email protected] to start the support ticket process even if there are issues with your access ID.

 

[Delmore]

You can boot the server in rescue mode, you might see what is the problem.
How do you know that WHM won't start? Can you connect using SSH?

SSH is not even working. I know WHM won't start because OVH offer a KVM interface to see server "desktop". Server is running as expected. I'm not an expert but there is no error or red messages.

You can always email [email protected] to start the support ticket process even if there are issues with your access ID.

Thanks, I will do that

 

[Delmore]

Sry for the double post but I am now in rescue mode on my server.
I can acces all my system files and I am trying to create a dump of my database.
Unfortunatly, mysql command does not work.
I think i need to call it directly from the folder where it is located.

Which dir is it ?

In forums they say :
/etc/init.d/mysql (not on my server)
/usr/bin or even /usr/sbin/ (them, no mysql in here)

With find command I have:
/mnt/root/etc/chkserv.d/mysql
/mnt/root/etc/logrotate.d/mysql
but both have permission denied

Thanks

PS: Also I sent my ticket to your support via email & and the other hand OVH told me that everything is fine on my server (yeah... except WHM won't start)

Following post is a duplicate i missed click

 

[cPRex]

I don't believe the MySQL tools will work in rescue mode so any "mysql" or "mysqldump" commands will not be an option. Unfortunately that leaves you with more basic tools like tar, which aren't always ideal for the system.

With the system so broken that SSH isn't even working, it would be best to work with a professional administrator to ensure that any data loss is minimized.

 

[Delmore]

Yesterday, I found out that it was a .ini file for a php extension which took too much memory.

In fact, after installing ea-php81, I did some change in the default provided php.ini.
In here, memory limit was set to 32M (yeah ... it seems very low to me for a default value) which is way insufficient to load my full_php_browscap.ini

Running php -v generated a error_log in ea-php81 folder I did not see !
I just think that with this "corrupted" php, rebooting the all thing was a very bad idea.

It make sense to me that, in this situation, WHM is unable to restart ...

Anyway, I updated that memory limit in rescue mode & now all is working as expected. What a relief !

Thanks you all & long live "rescue mode"

 

[cPRex]

I'm glad you were able to get things working!