Support

June 18, 2020 at 5:16 am

Hi there,

When you say the site went down, what error was thrown?

Why type of hosting are you using?

Multiple requests came from the same IP’s and I’m wondering if there is a script that keeps looping until the server resource gives up?

May I ask what makes you think there’s a script looping?

June 18, 2020 at 6:28 am

With no errors and no additional info other than some IPs there isn’t much you can do yourself.

503 basically just means the server couldn’t keep up with the requests but without knowing why you can troubleshoot this yourself.

Have you checked the error logs for any clues as to what happened?

June 26, 2020 at 5:34 am

Rather than a script looping over taking up the resources, it sounds like your hitting the number of requests your current server can handle.

Which cloud package are you using? Entry?

Are there any PHP settings you would recommend.

The biggest point is to make sure you are using PHP7 as opposed to PHP5 but other than that I don’t have any specific PHP setting recommendations.

Can you send me a test account I can use take run a registration? You can use this form:

https://eventespresso.com/send-login-details/

July 2, 2020 at 10:19 am

So wp-cron is what is taking the server down? That’s the first bit of useful info from the above replieds.

With wp-cron.php, EVERY request that hits your site will trigger a wp-cron.php check due to how it works. Think of it as a ‘fake scheduler’ in that it can’t tell your server that every 5 mins do X but what it can do is whenever there is a request on your site it can check if a job has been ‘scheduled’ and is due to run.

To give e a real example from Event Espresso we us wp-cron to schedule the message queue system to run every 5 mins. So we have a scheduled task that runs for Messages generation, Message Sending, Message Cleanup. Every request that hits your site also trigers a check to see if any of those tasks are due to run (Note that wp-cron is a WordPress feature we utilize, this isn’t a feature added by EE itself).

So, there’s a couple of things you can try.

First, disable the message system within Event Espresso and switch to sending emails instantly. You do this in Event Espresso -> Messages -> Settings.

You’ll see the option ‘Generate and send all messages:’, set that to ‘On same request’.

That tells Event Espresso to just send the messages on the same request that initialized it (the user’s request) and can mean it takes a little longer for the thank you page to load for your users. I recommend you run a full test registration and confirm it loads fine and you receive the emails.

The above does NOT stop wp-cron from being used, it simply tells Event Espresso not to use it for the emails, so next, disable wp-cron and add a ‘real’ corn to the server to hit wp-cron and run any scheduled tasks that need to be run without each and every request needed it. (Your host should know how to do this for you, infact they have a tutorial on it HERE).

The tutorial shows every 30mins, I recommend every 15, but see what works best for you.

July 29, 2020 at 1:06 pm

It’s the same issue, different symptom.

‘error establishing database connection’ == MySQL crashed.

MySQL is your database management system, so if it crashes it can’t, well manage your databases.

Why did MySQL crash? Likely because the load spiked to something higher than your server could cope with.