Hello Experts,

We have just upgraded our system with PHP V5.6.20 from PHP5.4.5. After this the node which got saved in PHP 5.4.5 is not getting saved in PHP 5.6.20 and the node is still in "Edit" Mode.

Sometimes, we get the following error:

Fatal error: Class entry requested for an object without PHP class in /home/xxxxx/public_html/includes/errors.inc on line 59

We are unable to understand what causing this error, but sure something with the latest PHP version and Drupal.

Any pointers, help in resolving the issue is greatly appreciated.

We wanted to take the benfit f PHP 5.620 for performance, but due to this issue, we wanted to remain in PHP5.4.5

Thanks for your attention , suggestion and advice,
SK2013

Comments

sk2013 created an issue. See original summary.

cilefen’s picture

cilefen commented
Issue tags: -node edit, -node save problem, -node

Put a breakpoint on that line and get a stack trace.

cilefen’s picture

cilefen commented
Status: Active » Postponed (maintainer needs more info)
sk2013’s picture

sk2013 commented

Thanks Cilefen.

We have put the break point and we just got blank screen and many times got the following error:

PHP Fatal error: Allowed memory size of 3183476736 bytes exhausted (tried to allocate 2970091520 bytes) in /home/xxxxx/public_html/includes/errors.inc on line 62

So increased to 6GB Memory again it exhausted memory. So we increased again exhausted. Finally we gave 15GB Memory we get to see the fields displayed on the browser. but no error message.

So we decided to downgrade to PHP5.4.45.

May be some one can refer if they got similar issue.

chrisc’s picture

chrisc commented

I have come across this issue, after upgrading to PHP 5.6.20 there is a massive increase in CPU usage, see this thread for some more detail.

The server has 8GB of RAM and 10 CPUs and is running Nginx, PHP5-FPM and Memcache, MySQL is running on another server.

Since the upgrade there have been lots of memory exhausted errors, for example:

[01-May-2016 20:50:38 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 350123 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1520
[01-May-2016 20:51:16 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 350123 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1520
[01-May-2016 20:51:38 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 349943 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1520
[01-May-2016 20:52:49 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 349943 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1520
[01-May-2016 20:55:41 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 332839 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1511
[01-May-2016 20:57:17 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 350101 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1520
[01-May-2016 20:57:47 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 350101 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1520
[01-May-2016 20:59:15 Europe/London] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 350556 bytes) in /var/www/prod/docroot/includes/theme.inc on line 1520

Since then the max memory per process has been increased to 512M and the max number of processes set to match the number of CPUs, 10, and this has prevented the server running out of memory and oomkiller taking services down (this happened yesterday), each process is using all the resources of one CPU.

The server is now staying up but is very slow, I'm probably going to have to downgrade PHP if a fix can't be found very soon.

Are there any more details I can provide which would help track this problem down?

cilefen’s picture

cilefen commented

@sk2013 Are you on Nginx also?

sk2013’s picture

sk2013 commented

Initially we were in just Apache then we have used both, but with Nginx we have got the Background Batch process not running. So we have removed Ngnix and also downgraded to PHP 5.4.45 and the Node Save is working fine now. Background batch process also working fine.Memory usage also fine.

Y'day we had the issue of memory and the server crashed (600GBSSDfor 15GB of data) with 100% disk .

Hope this helps,

chrisc’s picture

chrisc commented

I have downgraded to the last version of PHP for Debian Jessie and this has solved the very high CPU usage problem, however it would be good to find the cause of the problem...

cilefen’s picture

cilefen commented
Status: Postponed (maintainer needs more info) » Active
sk2013’s picture

sk2013 commented

Any one found solution to this peculiar issue with background process and node save when upgrading to higher versions of PHP?

Thanks,

Sk2013

Version: 7.43 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.