You may want to see if switching your PHP Execution Mode to “CGI” yields different results, or at least a better error message. FCGID isn’t always known for it’s great error messages.
You can switch that in Server Configuration -> Website Options.
Hmm, yeah segfaults are no good and could be a sign of a software bug, or a resource problem.
Do you perhaps have another PHP version available that you could try?
PHP 7.1 isn’t available by default in any of the standard Linux distributions, so I’m curious if there’s something related to it that’s causing the issue you’re experiencing.
Another option you could try is to disable any caching modules… we sometimes see odd things come up with some of the PHP caching options.
Lastly, verify that there’s enough RAM on your server. What is the output of “free -m”?
I know there are folks using the REMI repo with great success (and Diabolico, who wrote a tutorial on how to use REMI, may end up chiming in here :-), but if you’re seeing unusual issues with PHP segfaulting, that might be one thing to look into… whether it’s an issue with packages coming from that particular repo.
We don’t generally recommend packages from any repo other than the default CentOS repo, and then the SCL repo for more recent PHP versions.
Again, not everyone using REMI has that issue… in fact it’s been quite awhile since I’ve run into a PHP segfault issue that severe. But there’s a reason we recommend some repos and not others, and we have seen some unusual issues come from third party repos such as that one
Before you go changing repos though, the other thing I can suggest is to be super-sure that you don’t have any PHP caching modules installed or enabled, as we’ve seen some pretty unusual issues coming from those.
Scrip/software problem with cache (opcache, apcu…)
Problem with a software, e.g. installed scripts, CMS, etc.
Based on your first post i would say something is breaking between Laravel 5.3 and Remi PHP. Did you check if you have installed all PHP modules required for Laravel and did you try to disable any caching. Please note that opcache comes integrated with PHP 5.6 and up but it should be set off by default.
Last but not least, did you try with never version of Laravel (i think last one is 5.4) or you could post on Remi forum, he is very quick to answer to all questions.
As a side note, i’m using Remi PHP 7.1.x for almost 2 months (maybe more) and didnt encounter single problem. Actually this version of PHP is pushing the limits quite high. The one time i had a problem was because of some WP plugin and really bad coding and nothing to do with Remi PHP.
EDIT: Just to rule this out, could you switch back to 7.1 and run php --modules, then post it here.
Could you report this problem to Remi forum https://forum.remirepo.net/. I’m sure he would like to sort it out in case his PHP is the cause of your problem.
have the same behavior on my ubuntu16.4, it returns the error after 31ms in google dev console. I tried to increase the execution time to 600s via server configuration > website option. it works!.
