CiviCRM Community Forums (archive)

I'm running into a problem with UpdateMembershipRecord.php
It keeps timing out when run manually from a browser, and when I try to run from SSH/command line, it runs for a while and then terminates unexpectedly. My max_execution_time, max_input_time and memory_limit are plenty high (1800, 1800, 96m).

This is the first time I'm running it after a large import, so I'm not surprised that it would take some time, but I would have expected it would at least finish when run through SSH.

Any ideas?

No error. When running from SSH it just ends abruptly and says "terminated".
When running from http it stops with a blank screen.

I'll take a look at the suggestion for modifying it. I was thinking there might be a bug in the data that's triggering it to stop.

VPS, full root access. I had some conversations with Tech Support to see if there was something I was missing at their end, but I really shouldn't have these issues, especially if I'm running it from the command line.

But who knows. I manually segmented the query and the script completed. So it does appear as though the process is quitting because it's taking too long.

Questions about the script --
The script is set to ignore memberships with a Pending or Canceled status (unless the contact is deceased, in which case the status would be changed to Deceased). I guess the assumption is that those two statuses are manually changed. So one improvement may be to build that criteria into the query so that you start out working with a smaller data set. Seems like you could add "Expired" and "Deceased" to that criteria exclusion.

Though I'm not sure that's a good policy, as it sort of pre-determines the uses of those statuses outside of the interface.

Adding those criteria to the query dropped my resultset in half, and the script ran without a hitch.

Hi,

One way of improving the result is to call it from the cli instead of from curl/wget. By bypassing the webserver, you really improve things, you can nice/ionice it on the cron, and in general it works much better memory or timeouting wise.

In the bin/cli.php you have a wrapper (on the trunk in svn, might be older) that makes it easy to call your code from the cli, and deals with parameters and key and this and that.

Ping me if you can't find your way or need an example of how to use.

X+

Hi,

I'm not saying that the cli should be the only solution, but that's fairly easy to have two wrappers (web request and cli) that access the same code once the the parsing of the params is done.

I'll try to do it on the mail cron, I've been complaining on it for too long about it.

To be continued...

X+