I've increased the PHP memory limit to 256MB, but I'm getting this error for each cron run:
<b>Fatal error</b>: Allowed memory size of 268435456 bytes exhausted (tried to allocate 118268981 bytes) in <b>/var/www/vhosts/xxx.xxx.com/httpdocs/sites/all/modules/acquia_connector/acquia_agent/acquia_agent_streams.inc</b> on line <b>182</b><br />
I'm using Acquia search and the search file attachment modules. Cron settings are 25 items per run for acquia_search and 10 nodes/30 seconds for the attachment module. Disabling the attachment module seems to fix things. I'm cross posting this in the attachment module issue queue.
Comments
Comment #1
vinmassaro CreditAttribution: vinmassaro commentedWe're seeing the same issue, on a site with 128MB PHP memory limit. Acquia Search settings are set to 1 item per cron run, and attachments are set to 10 nodes/30 seconds.
Comment #2
sterndata CreditAttribution: sterndata commentedI was able to index a bunch of files. I'm assuming that it's hit some large file that makes it very unhappy. Is there a way to determine what file it might be processing at the time it crashes?
Comment #3
Nick_vhSeems like it is still a server issue? As far as I know are the requests for attachments not passing this acquia_agent_http_request function. This is more likely a server issue.
Would you be able to write down the steps that allow us to reproduce this? Including exact module versions etc..
Comment #4
Nick_vhSo, I took a look at the 6.x-1.x acquia search connector :
http://drupalcode.org/project/acquia_search.git/blob/refs/heads/6.x-1.x:...
so it seems the whole POST is indeed sent through this function. Your attachment filesize * amount of items per cron = min available memory. It might be good to lower your amount of cron items or raise your memory.
I do not see this change in 6.x-1.x, however, I am quite certain that the 7.x-1.x version has improved a lot in this sense
Comment #5
Nick_vhComment #6
sterndata CreditAttribution: sterndata commentedNick: I'm sorry, but closing this as cannot reproduce is not acceptable. I'm willing to provide whatever logs/documentation you need. I've plunked down my money for Acquia Search and I really need this to either work all the time or fail gracefully. Feel free to contact me.
Comment #7
Nick_vhOk, I understand.
Could you please file a support ticket using the network login?
I replied numerous times and I have suggested info.
Also, apachesolr 6.x-2.4 is not supported anymore, so that was one reason to close this issue (but might be my fault, as this is the connector queue)
Sorry if that offended you :-)
Comment #8
sterndata CreditAttribution: sterndata commentedI've filed a ticket and am grinding through that process.
Comment #9
coltraneIs there still an issue here?
Comment #10
sterndata CreditAttribution: sterndata commentedAs far as I'm concerned, yes. I got around it by hacking a file size limit into the PHP. It would be nice if either (1) it failed gracefully with an log entry that it's skipping a file that's too large or (2) there were an option for "max file size" and it's the user's responsibility to set a reasonable value. The code currently loads a file into memory and, if it's to big, goes *splat*.
Comment #10.0
sterndata CreditAttribution: sterndata commentedadded results of disabling attachment module
Comment #11
Dane Powell CreditAttribution: Dane Powell at Acquia commentedThe 6.x branch is no longer being supported. If this is still an issue in the 7.x-3.x or 8.x-1.x branches, please change the target version and reopen. Also consider trying the new standalone Acquia Search Solr module.