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

vinmassaro’s picture

We'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.

sterndata’s picture

I 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?

Nick_vh’s picture

Seems 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..

Nick_vh’s picture

So, 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

Nick_vh’s picture

Status: Active » Closed (cannot reproduce)
sterndata’s picture

Status: Closed (cannot reproduce) » Active

Nick: 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.

Nick_vh’s picture

Ok, 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 :-)

sterndata’s picture

I've filed a ticket and am grinding through that process.

coltrane’s picture

Status: Active » Postponed (maintainer needs more info)

Is there still an issue here?

sterndata’s picture

As 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*.

sterndata’s picture

Issue summary: View changes

added results of disabling attachment module

Dane Powell’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

The 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.