PHP won't start

DreamlabNL

New member
Joined
Oct 20, 2020
Messages
4
Hi there, i just updated PHP to 7.4.11

It was my 3rd try of installing, somehow this time it installed. It was a better tutorial i quess.
I did it in console, not with CB. Now PHP won't restart.

So at first it looked ok, DirectAdmin was running but all sites were down and a 503 Service unavailable was displaying.
So i reinstalled the whole Custom Build (because it was broken), reinstalled Installatron (because it was broken) and then things came back up.

But not PHP.
It gives me the Script not found message.

I'm on CentOS 7, Custom Build 2.0, Installatron
Running 6 cores and 10Gb ram, so sufficient memory and space.
And yes, i did the systemd = 1 trick

Please help!
 
Hi Richard, yes it does. It says PHP 7.4.11
I used the console and i did this:


cd /usr/local/directadmin/custombuild
./build update
./build set php1_release 7.4
./build set php2_release 7.3
./build set php1_mode php-fpm
./build set php2_mode php-fpm
./build set mod_ruid2 no

Then:

./build php n
./build rewrite_confs
 
I normally do a ./build update after making changes, but this is also correct.
If it says php 7.4.11 then php is running.

You could check with:
Code:
service php-fpm74 status
service php-fpm73 status
to see if both php-fpm services are running. I expect they do which would mean the issue is probably somewhere else.

Doublecheck that mod_ruid2 is not running anymore, by checking the /etc/httpd/conf/extra/httpd-phpmodules.conf file that it does not contain any mod_ruid2.so anymore.

Also run this command:
Code:
httpd -V | grep 'MPM'
should answer with:
Code:
Server MPM:     event

If these are all correcf, then it seems there is another issue which I don't know.
So i reinstalled the whole Custom Build
I presume you used the ./build all d command. If yes, you probably don't need to do this again.
 
Hi there,

We did the whole build all d command but nothing worked.
So eventually we got in touch with a pro.
He came across a not PHP Mail Library that was not build correctly or was corrupted.

He reïnstalled 7.3 and it worked again. But things looked kind of strange on the server he said.
Probably way to many "trial and error" projects that left a trail of rubbish.

So we are setting up a new VPS and will migrate all our sites.

Thanks for the help and quick response!
 
So we are setting up a new VPS and will migrate all our sites.
That might indeed be the best way.
Maybe next time a bit less trial and error, best do things via console, you can see errors immediately if they happen.
And then can ask support on the forum for example.

As for the help and quick response, you're welcome!
Hope your new vps and migration work fast and flawlessly for you.
 
Back
Top