On Tue, 10 May 2016 10:03:53 +0100 James Smith <js5@xxxxxxxxxxxx> wrote: > Setting up apache server-status module is always a good idea - as you > can (try) and see the information about load/requests etc. I have set it up but it doesn't help if Apache isn't serving pages. > wp-cron.php is a wrapper script around a whole system of potentially > complex functions which maintain the database (garbage collect etc) > it depends on what modules you have enabled how this is effecting the > rest of the server. > > If it is locking every word press script you may find that every > apache child eventually handles a word press request (99 after the > cron job locked wordpress) and so there are no free apache children > to handle requests for static content... That seems to be the problem. And, you may have suggested a way to check what's running. When everything locks up I can't see the status page and if I kill the problem process I can't see what it was but I guess I can kill a couple of other sites and that may allow the status page to run. If it happens again I will try that. I say "if" because I am trying something and so far it seems to be working. I realized that this was a recent problem and that I recently upgraded to 2.4.20. I reverted to 2.4.18 last night and so far so good. I will report after a few days or sooner if it happens again. -- D'Arcy J.M. Cain System Administrator, Vex.Net http://www.Vex.Net/ IM:darcy@xxxxxxx VoIP: sip:darcy@xxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx