Problems with PHP 5.6.16 and Evo 1.0.15

Does anyone know of any compatibility issues with 1.0.15 and PHP 5.6.16? (My server is also running Apache 2.4.16 and MySQL 5.6.27.)

My hosting provider (Lunarpages) upgraded PHP last night and all my ModX Evo sites are failing and throwing 500 server errors. One possible solution I stumbled upon was to simply run a reinstall, which actually worked for about 3 minutes--the site was back up and I was able to log in to the Manager, etc.--and then for no apparent reason it started failing again.

I have confirmed that the MySQL login credentials are correct and everything else is just as it was Wednesday when things were working properly (except for the new version of PHP).

Here are the errors I am getting, both in the error log on the site and the server log:

Site errors:

[11-Dec-2015 09:35:38 America/Los_Angeles] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 72 bytes) in /home/ether6/public_html/schiff/manager/includes/document.parser.class.inc.php on line 3651

[11-Dec-2015 09:35:38 America/Los_Angeles] PHP Warning: mysql_connect(): Access denied for user 'ether6_mborum'@'localhost' (using password: YES) in /home/ether6/public_html/schiff/manager/includes/extenders/dbapi.mysql.class.inc.php on line 93

Server errors:

[Fri Dec 11 09:48:25.272624 2015] [:error] [pid 974704] (12)Cannot allocate memory: [client 24.5.37.217:49917] couldn't create child process: /opt/suphp/sbin/suphp for /home/ether6/public_html/schiff/index.php


I have opened a support ticket with Lunarpages, but they aren't being very helpful or responsive just yet. They have confirmed, more or less, that PHP 5.6.16 is the only version now available to me.

I appreciate any tips on how to address this. I am not a terribly strong sysadmin or PHP debugger.

Thank you,
Michael

Which PHP version was it before? Maybe it is just a change of the database extender in "manager/includes/config.inc.php" from mysql to mysqli.

Looks like at least two things going on here:

First
Quote from: etherweave at Dec 11, 2015, 05:57 PM

[11-Dec-2015 09:35:38 America/Los_Angeles] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 72 bytes) in /home/ether6/public_html/schiff/manager/includes/document.parser.class.inc.php on line 3651

[Fri Dec 11 09:48:25.272624 2015] [:error] [pid 974704] (12)Cannot allocate memory: [client 24.5.37.217:49917] couldn't create child process: /opt/suphp/sbin/suphp for /home/ether6/public_html/schiff/index.php

These sets of errors imply that you were in an out of memory condition at 32M (33554432 bytes) of memory. That's a bit stingy; the default for PHP has been 128M since 5.3. See: http://php.net/manual/en/ini.core.php and scroll down or search in-page for "memory_limit".

I'd ask your host if they can up your memory limit.

Second
Quote from: etherweave at Dec 11, 2015, 05:57 PM

[11-Dec-2015 09:35:38 America/Los_Angeles] PHP Warning: mysql_connect(): Access denied for user 'ether6_mborum'@'localhost' (using password: YES) in /home/ether6/public_html/schiff/manager/includes/extenders/dbapi.mysql.class.inc.php on line 93

Has this particular error happened since you checked (reset?) your MySQL password, or has it gone away since then? It seems odd that a access credential failure would be intermittent, as you reported.

The following appears to the the upgrade announcement from your host: http://www.lunarforums.com/hosting-server-bulletins/php-and-mysql-upgrade-scheduled-lpcp-fourth-batch-dated-09-dec-2015-2am-pst/. Check out the paragraphs there that start with "MySQL users that were last updated more than approximately 6 months ago...".

That may have applied to you and caused this particular server error. If you checked/reset your password, it would seem, per the host's announcement, that would have fixed this particular error.

Quote from: clareoconsulting at Dec 11, 2015, 08:28 PM

These sets of errors imply that you were in an out of memory condition at 32M (33554432 bytes) of memory. That's a bit stingy; the default for PHP has been 128M since 5.3. See: http://php.net/manual/en/ini.core.php and scroll down or search in-page for "memory_limit".

I'd ask your host if they can up your memory limit.

I have come to the same conclusion and will be asking them to do this.

Quote from: clareoconsulting at Dec 11, 2015, 08:28 PM

That may have applied to you and caused this particular server error. If you checked/reset your password, it would seem, per the host's announcement, that would have fixed this particular error.

Yes, exactly. I *just* discovered this is the case. Change MySQL passwords has resolved the issue.

THANK YOU so much for getting back to me and for basically affirming what took me a little longer to discover. I really appreciate it!

Michael

Since you get a warning with mysql_connect() you should also change the database extender like this: http://stackoverflow.com/a/31125115/3954959

I invite everyone to test and a week to release the official version:
https://github.com/modxcms/evolution/releases/tag/v.1.1RC
now Evo work up to PHP7

Quote from: dmi3y at Dec 29, 2015, 10:35 PM

I invite everyone to test and a week to release the official version:
https://github.com/modxcms/evolution/releases/tag/v.1.1RC
now Evo work up to PHP7

Great work, Dmitry. Isn't a little bit too ambitious to "test and a week to release" during New Year's holidays?
I'm going to try it mid January, it looks like really busy start of year 2016.