Site is non responsive after upgrade
I have been running 20.9 without any issues on 2 web sites. I recently tried upgrading the 2 sites to the latest version of 21.1. One site works fine, the other now never finishes loading and times out. I have reverted back to 20.9 and everything works ok. I don’t see any errors in any logs. I do see alot of SQL statements running while the site is clocking.
What would be the best way to debug this issue?
I am guessing it is something to do with wp-router. I disabled most of the plugins and didn’t make any difference. I tried disabling wp-router, but that basically breaks the site. Is there any time of debuging that is in wpsolr I could use to help pinpoint where it is hanging?
Sorry, the not related was referring to the sql that was executing, not the site issue. Let me try the query monitor plugin. It think it does have something to do with mysql, when the 21.1 plugin is activated running on MAMP on my local machine, mysql starts using alot of CPU. Ill post back anything I find from the query monitor plugin. Thx for your help
Must be something stuck in a loop, it keeps running out of memroy:
Fatal error: Allowed memory size of 6492782592 bytes exhausted (tried to allocate 20480 bytes) in
I have bumped it up to 6G and it is still failing.
I’ll probably have to fall back to 20.9 for now since we have a launch date in the next few weeks. I’ll keeping investigating to see if I can track down the issue when I can.
Is there a way to complete remove the plugin so I can re-install(including the license or any other data stored in the db)? I am wondering if there is some issue with the license being partially installed. On my other site on dev I see the following message “This is a test environment only.”, the dev site I am having an issue with shows “Your license is not active. Please activate it now.”
Your domain name match dev.* or *.dev to be considered as dev.
See https://www.wpsolr.com/forums/topic/test-the-plugin-without-a-payment-method/ for more examples.
You must be logged in to reply to this topic.