Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
sadams101 Posted June 24, 2019 Posted June 24, 2019 This may be a dumb question...but, my server has multiple versions of PHP, and I only noticed this issue when I changed my cron line to include the PHP 7.3 path. Can't I just run the cron job using the PHP 7.2 path and keep running my site on PHP 7.3? To me it appears that this error appears to be triggered by the cron job. To clarify, if I run the cron using this path: /opt/cpanel/ea-php72/root/usr/bin/php I see no errors...but if I run it using this one: /opt/cpanel/ea-php73/root/usr/bin/php I do see the errors.
Gabriel Torres Posted June 25, 2019 Author Posted June 25, 2019 @sadams101 as discussed in this topic, this is an issue with PHP 7.3, so you will only see it when running PHP 7.3...
sadams101 Posted June 25, 2019 Posted June 25, 2019 I understand, and am running PHP 7.3 without the patch, and without the errors. My point was that I believe the errors are caused by the cron script, which I continue to run under PHP 7.2. With this setup I do not see the errors reported in this thread.
AlexJ Posted June 27, 2019 Posted June 27, 2019 On 6/25/2019 at 2:43 PM, sadams101 said: I understand, and am running PHP 7.3 without the patch, and without the errors. My point was that I believe the errors are caused by the cron script, which I continue to run under PHP 7.2. With this setup I do not see the errors reported in this thread. I tried disabled cron for an hour to figure out .. but i still noticed the error. Can someone please try what's suggested above? I hope it work for someone besides sadams101 and then may be i will just re-install php 7.3 and 7.2 again. @Gabriel Torres @The Old Man @RevengeFNF Thank you!
ASTRAPI Posted June 27, 2019 Posted June 27, 2019 The proper solution is to use the patch or wait around a week for the new version that will include the patch and you will not need to do anything custom...
DSystem Posted June 27, 2019 Posted June 27, 2019 For those who use Centos with remi it is easy to upgrade to PHP v7.3.7RC3 that already has the fix.. https://blog.remirepo.net/post/2019/06/13/PHP-version-7.2.20RC1-and-7.3.7RC1 yum --enablerepo=remi-php73,remi-php73-test update php\*
sadams101 Posted June 27, 2019 Posted June 27, 2019 Update: I am seeing the errors in my logs, so simply running the cron under PHP 7.2 while running the site under 7.3 isn't going to stop this. I do believe that the errors may still be cron-related thought, as I was being emailed errors by the cron job when it ran under PHP 7.3. I'll probably just wait for the update and continue running PHP 7.3 though, as the errors are not causing obvious issues with anyone, and there are only 10-20 a day like this: [27-Jun-2019 00:40:05] WARNING: [pool celiac_com] child 10743 exited on signal 11 (SIGSEGV) after 18775.397204 seconds from start [27-Jun-2019 01:49:06] WARNING: [pool celiac_com] child 31423 exited on signal 11 (SIGSEGV) after 811.090899 seconds from start [27-Jun-2019 02:33:52] WARNING: [pool celiac_com] child 1200 exited on signal 11 (SIGSEGV) after 1775.105461 seconds from start [27-Jun-2019 11:54:21] WARNING: [pool celiac_com] child 29801 exited on signal 11 (SIGSEGV) after 13094.452787 seconds from start [27-Jun-2019 11:54:21] WARNING: [pool celiac_com] child 25982 exited on signal 11 (SIGSEGV) after 16305.524441 seconds from start [27-Jun-2019 11:54:21] WARNING: [pool celiac_com] child 10371 exited on signal 11 (SIGSEGV) after 3071.571008 seconds from start [27-Jun-2019 11:54:21] WARNING: [pool celiac_com] child 6956 exited on signal 11 (SIGSEGV) after 5566.615759 seconds from start [27-Jun-2019 11:54:22] WARNING: [pool celiac_com] child 29800 exited on signal 11 (SIGSEGV) after 13096.658268 seconds from start [27-Jun-2019 11:54:32] WARNING: [pool celiac_com] child 14458 exited on signal 11 (SIGSEGV) after 0.101819 seconds from start [27-Jun-2019 11:54:34] WARNING: [pool celiac_com] child 14463 exited on signal 11 (SIGSEGV) after 1.082474 seconds from start [27-Jun-2019 11:54:34] WARNING: [pool celiac_com] child 14461 exited on signal 11 (SIGSEGV) after 1.655926 seconds from start [27-Jun-2019 11:54:34] WARNING: [pool celiac_com] child 14471 exited on signal 11 (SIGSEGV) after 0.603521 seconds from start [27-Jun-2019 11:54:34] WARNING: [pool celiac_com] child 14472 exited on signal 11 (SIGSEGV) after 0.686002 seconds from start [27-Jun-2019 11:54:35] WARNING: [pool celiac_com] child 14480 exited on signal 11 (SIGSEGV) after 0.085251 seconds from start [27-Jun-2019 11:54:35] WARNING: [pool celiac_com] child 14479 exited on signal 11 (SIGSEGV) after 0.225088 seconds from start [27-Jun-2019 12:10:53] WARNING: [pool celiac_com] child 14477 exited on signal 11 (SIGSEGV) after 978.328896 seconds from start
marklcfc Posted July 4, 2019 Posted July 4, 2019 I've only just found this, I've had the same issue since around when you started the topic. This has been coupled with occasional 503 service unavailable errors ONLY on the home page, after which on the following refresh the recent topics widget has disappeared. It will return a minute later (in admin cp I have sidebar blocks cached to 1 minute). I gave my host the time it happened last night and this was the error [03-Jul-2019 22:22:44] WARNING: [pool mysite-co-uk] child 118140 exited on signal 11 (SIGSEGV - core dumped) after 855.115077 seconds from start [03-Jul-2019 22:22:44] NOTICE: [pool mysite-co-uk] child 119148 started PHP 7.3.7 released today apparently
DSystem Posted July 4, 2019 Posted July 4, 2019 4 hours ago, marklcfc said: PHP 7.3.7 released today apparently Yes. Here it is already updated. Testing ... # php -vPHP 7.3.7 (cli) (built: Jul 3 2019 11:30:22) ( NTS ) Copyright (c) 1997-2018 The PHP Group Zend Engine v3.3.7, Copyright (c) 1998-2018 Zend Technologies with Zend OPcache v7.3.7, Copyright (c) 1999-2018, by Zend Technologies
AlexJ Posted July 4, 2019 Posted July 4, 2019 8 hours ago, marklcfc said: PHP 7.3.7 released today apparently Looks like I need to wait till build shows up sury. I hope it resolves the issue with mod php as well.
AlexJ Posted July 9, 2019 Posted July 9, 2019 On 7/4/2019 at 9:37 AM, DSystem said: Yes. Here it is already updated. Testing ... # php -vPHP 7.3.7 (cli) (built: Jul 3 2019 11:30:22) ( NTS ) Copyright (c) 1997-2018 The PHP Group Zend Engine v3.3.7, Copyright (c) 1998-2018 Zend Technologies with Zend OPcache v7.3.7, Copyright (c) 1999-2018, by Zend Technologies How it is working for you so far?
DSystem Posted July 9, 2019 Posted July 9, 2019 1 hour ago, AlexJ said: How it is working for you so far? Working like a charm. Errors from the previous version have disappeared from the logs 👀
Gabriel Torres Posted July 10, 2019 Author Posted July 10, 2019 Just to confirm that I upgraded to PHP 7.3.7 last night and so far it is working like a charm here as well! 🙂
The Old Man Posted July 10, 2019 Posted July 10, 2019 Hoping and waiting for PHP 7.3.7 to become available via WHM/CPanel Yum Update sometime before the next millennium! I went back to 7.3 in anticipation last week and the 503's are driving me nuts again. Why are they so slow?! 😤
The Old Man Posted July 10, 2019 Posted July 10, 2019 Yay, CPanel are releasing an update to PHP 7.3.7 today! 😊
ASTRAPI Posted July 11, 2019 Posted July 11, 2019 8 days later. Maybe acceptable for the specific error but not for security patches. I can't say that i miss cpanel 😛
Recommended Posts
Archived
This topic is now archived and is closed to further replies.