Open garethrees opened 6 years ago
I've had a quick look this afternoon following a chat with @crowbot. The various limits set for the foi
user either haven't changed, or have increased. There are no OOM killer messages associated with the errors, or kernel messages suggesting limits have been reached, so it doesn't appear to be down to config from the old host that we'd missed transferring to the new one for any of the more obvious things, and everything seems to be captured in git anyway. I'll have a bit more of a think and another look in a day or two.
Just looking at when these started and how many we've had:
Looking through this again, it seems to me that the exception is being triggered while parsing an attachment of some kind. I wonder if this commit might be the culprit, this gets passed into the call to open4 via the library in commonlib, I think? (Bit shaky here, could do with a more skilled Ruby developer to have a look too!)
Yeah, that probably has something to do with it (in that its limiting memory allocation), but that commit was made in 2013. I'm not sure why we started seeing so frequently (~100 instances) since late November 2017.
Seen a few of these
NoMemoryError: failed to allocate memory
since we moved server.