A shutdown was triggered Error when rebuilding list

Hmm interesting.. shutdowns are usually caused by things outside the plugins control (although occasionally that something is bad unexpected data but that usually leaves a visible message)

the message returned by whatever caused the php shutdown should be echoed below in
html tags

(the plugin traps the shutdown so it can gently show hat the message was)

Message should also be sent to your php error log. You could have a look at that (probably need ftp access to do that)

Perhaps it's running out of runtime ?
How big is your user and usermeta ? (see the about section in the settings). when it starts getting up around 8-10K of users system doesn't always cope (depends how much user meta)

Also occasionally a corrupted db table - could look in phpmyadmin see if anything is flagged as needing repair

Sometimes it is that the php install does not have all the php functions required enabled - but that people usually find out on first run (eg multibyte support)

let me know what you find out please

Umm – that should be the < code > tag above !

Hi Anmari,

Thanks for the tips. Definitely helped me with some ideas. I am still having problems, but don’t want to make the problem worse as I can still operate well enough, though your plugin helps immensely in daily operations.

I am still getting that error. Here is what I have tried.

1) https://www.ads-software.com/support/topic/rebuild-cache-fails-when-caching-huge-list

if ( ! defined( ‘WP_MAX_MEMORY_LIMIT’ ) ) {
define( ‘WP_MAX_MEMORY_LIMIT’, ‘xxxM’ );
}

I went from 40 to 64 memory there. I see the change on the About screen. I am on a shared server with Midphase – support over there added a php.ini file with some added memory there in the public_html directory. Not sure if they have to match, but expect the php.ini is the overlord. Anyway, the about screen now shows 64. Same error.

2) I did look at the myPhpAdmin databased and they looked fine at a glance. I do have a lot of users (12k) and was able to export some with times to help me ID some I can delete. I would like to avoid that and since I have more memory now, figured I might be able to get running again and try the User Last Login Plugin going forward to remove dead users. But that will take a while and it a bit rough cut anyway. Still erroring so….

3) Tried deactivating/reactivating the plugin. Didn’t seem to help.

I have exported my reports for AMR, so I expect I could uninstall the plugin and add it from scratch. Think that might reset things?

I do have a lot of users, but am hesitant to go that way unless I have to (and frankly, given the memory increase and the nature of this error, not sure that would really help).

Mind if I ask your advice given the above and your experience? In any case, hope this dialogues helps someone else too. Though, clearly would be better info if I actually get it solved.

Thanks again for the plugin and your speedy response.

This is what I am working on – DAC
Cloud Desktop

Yiks – yes 12K might be pushing it.

Because of it’s orignal needs and attempting to cater for third parties doing stuff, the query is perhaps not the most efficient.
Also the cacheing (csv complicated query origins ) also puts a load. You may have to go to coding a dedicated query.

There is a rewrite planned so that if a site is using wp as intended (user meta good etc) it willbe more efficient and push any weird stuff to add-ons for the plugins causing the weird stuff. BUT won’t be anytime terribly soon as requires careful planning to cater for compatibility.

Part of the reason actually that the plugin started was in an attempt to slice and dice user records to be able to identify and get rid of ‘deadwood’ ie: non good users AND non good user meta.

Any ways that you can reduce the query by excluding users using user or usermeta fields (not weird 3rd party ones) – makeing reports smaller – may help.

Often there is a lot of usermeta lying around – see the “excluded user meta” menu option in admin – it will show number of records with that usermeta. If you know for sure it is no longer in use, – there is an option to tick delete.

However I suspect that the best benefit will come from trimming the user database.

Backup First!

Hey,

Got it. Certainly understandable. 12k did seem like a bunch. I tried trimming the meta data but still the same error. I will try some other things tomorrow or so. Will let you know how/if I resolve.

I appreciate the support and the fine plugin. It really helped me quite a bit over the last couple of years.

Thanks again,