Skip to content
This repository has been archived by the owner on Jun 7, 2022. It is now read-only.

Plug-in does not access panel and exhausts server #2908

Closed
vitorbtorres opened this issue Sep 9, 2019 · 9 comments
Closed

Plug-in does not access panel and exhausts server #2908

vitorbtorres opened this issue Sep 9, 2019 · 9 comments

Comments

@vitorbtorres
Copy link

I'm having trouble with the native WooCommerce Admin plugin (WooCommerce Store Management Dashboard).

While accessing the plug-in panel, I am getting error "508 Resource limit is reached" and the site goes down.

Input processes, physical memory, CPU usage, and IOPS are exhausted on the server when access is available.

Already tried to do everything ... increased the memory of php, among other things.

He is making thousands of requestments.

Version: 0.18 (Plugin)

requests-panel

resourcelimit

estatisticas-server

@corsonr
Copy link
Member

corsonr commented Sep 11, 2019

Reported in 2340122-zd

@vitorbtorres
Copy link
Author

Reported in 2340122-zd

I don't understand.

2340122-zd this topic? Where?

Thank you!

@zandyring
Copy link

@vitorbtorres, @corsonr left an internal note that we use to follow-up with other reports, so you do not need to worry about that note :)

@corsonr
Copy link
Member

corsonr commented Sep 13, 2019

Hey @vitorbtorres, yes, it's been reported by other users too, that's why we're gathering everything here. On a side note, it seems you're using the same server so that might be server related at some point but it's a bit early to tell.

@timmyc
Copy link
Contributor

timmyc commented Dec 2, 2019

@vitorbtorres just checking in to see if newer versions of the plugin have resolved this issue for you?

@GWS13
Copy link

GWS13 commented Dec 6, 2019

We have had a similar issue as described by @vitorbtorres, but we were getting 500 Internal Server errors (instead of 508) and then the website would go down. This problem has occurred since we upgraded our website to WordPress 5.3 and WooCommerce to 3.8.1.

We had Facebook for WooCommerce installed. A chat with hosting revealed the Apache logs showing a bombardment of IP addresses from Facebook. So we deactivated the Facebook plugin. That didn't solve the problem though.

We put the site in maintenance mode, disabled all plugins except for WooCommerce and then enabled the other plugins one at a time while watching the server stats. We found the CPU/memory spikes occurred when navigating to the WooCommerce Admin plugin dashboard itself. Anywhere else in WooCommerce (Orders, Settings, Status, etc) was fine. Once we deactivated the WooCommerce Admin plugin the server stats stay normal.

Since we don't really need the WooCommerce Admin plugin, we decided to remove it.

I want to note we have other websites showing issues with a different plugin -- WooCommerce Services plugin. We don't really need that either and have disabled it on two sites.

To sum, if you don't need the WooCommerce Admin plugin I recommend removing it. Same for Facebook for WooCommerce if the logs show high traffic from Facebook.

I hope this information is helpful.

@timmyc
Copy link
Contributor

timmyc commented Dec 7, 2019

@GWS13 thanks for taking the time to report the issue you had. Would it be possible for you to share some of the apache logs from when the problem happened when visiting the Dashboard page? Also by chance did you import historical data when you installed the wc-admin plugin? Trying to get a sense of what might have led to the issue you were having - so any further details about the hosting environment would be helpful too - an easy way to do this would be to generate a System Report from WooCommerce > Status in your site's wp-admin.

If you would prefer to send this info via email just let me know.

I've tested the WooCommerce Admin dashboard on a number of hosting configurations, with larger test data sets ( 5k, 10k orders ) and haven't encountered this exact issue myself.

Thanks again for the report, and looking forward to getting some more details if possible.

@GWS13
Copy link

GWS13 commented Dec 12, 2019 via email

@timmyc
Copy link
Contributor

timmyc commented Aug 5, 2020

Since we haven't had any further feedback here, I'm going to close this out. If you are still experiencing performance issues please do respond.

@timmyc timmyc closed this as completed Aug 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants