[ace] [New Logentry] odd logbook issues the past couple of days

[cuffe at jlab.org]

Logentry Text:
--
There have been some odd issues with the logbook the past couple of days.  Mostly, these have been in trying to update or submit entries.  In investigating the front-end logbook server, I found that it had been updated and rebooted 2 days ago (as part of CNI's maintenance day I think).  I also noticed that if I used our backup system elog.acc.jlab.org to perform these operations, I had no issues.  The error log on logbooks.jlab.org had server php memory errors like this one:
 
[Fri Sep 23 17:11:28 2022] [error] [client 129.57.64.122] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 147330697 bytes) in /www/logbooks/drupal-7.84/sites/all/modules/elog_archive/elog_archive.module on line 223

The global PHP memory limit allowed for an individual scripts was 384M as specified in the php.ini file.  This file had not been modified in several years.  I increased this value to 512M and this resolved the issue that I was able to reproduce (updating a specific OPS-PR).  Perhaps some up stream default was changed as part of patching or things just use more memory after patching.  

I will watch for more issues over the next few days and increase this again if it seems necessary.



---

This is a plain text email for clients that cannot display HTML.  The full logentry can be found online at https://logbooks.jlab.org/entry/4045887
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/ace/attachments/20220923/61039727/attachment.html>