It was working fine testerday before you logged in.
What did you do ?
This site can’t be reached
xxxxxx.com’s?DNS address?could not be found. Diagnosing the problem.
DNS_PROBE_POSSIBLE
This is a severe alert.
PLEASE ADVISE ASAP
]]>We’ve been long-time users of the Product Feed PRO for WooCommerce plugin, and it has served us well. However, starting yesterday, we’ve encountered a significant issue when attempting to update the XML feed manually. The update process now causes a critical load on our hosting environment, ultimately leading to a server crash.
Previously, we had the “Change products per batch number” set to 200, and this configuration allowed us to efficiently update five XML feeds on each of our seven websites consecutively. However, in response to the recent problem, we attempted to reduce this value to 50, but it appears to have had no impact on the issue. It’s essential to note that there have been no changes made to our hosting environment, and we have not downgraded our service package.
To illustrate the problem, I have attached a screenshot from our hosting monitoring system, displaying the sharp spikes in both CPU and RAM load during attempts to update the XML feeds. The CPU load graph demonstrates the first part, while the second part visualizes the RAM load. These spikes coincide precisely with our efforts to update the XML feeds.
Screenshot: https://i.imgur.com/Wgv7KKs.png
We are reaching out for assistance in resolving this critical issue promptly, as it significantly disrupts our workflow and website performance. Your guidance and support in diagnosing and rectifying this problem would be greatly appreciated.
Thank you for your prompt attention to this matter.
]]>Thanks
]]>The two stars were awarded for some of the other features which do appear to work.
]]>I hope that wordpress core devs and Woocommerce Devs and Admins will see it and respond and please explain why why why is it so?
wordpress is now a total monster when it comes to images.
In combination WordPress + Woocommerce + Most premium Themes there can often be 10 OR more different image sizes getting auto generated when a post/page/product is created.
WordPress has 4 sizes..
woocommercer adds another 3 sizes
Most premium themes add several additional sizes of their own
As an example the Enfold theme by kriesi adds its own 12 additional image sizes.
I understand why these are added for the Main Featured Image what I do not understand is why all these image sizes are generated regardless of where the original image being recreated is used..
What I dont understand is why every image in every post type generates every one of those sizes..
I mean why do we need the woocommmerce sizes generated for images found only within a post or page?
Why do we need all the post/page/prtfolio etc images sizes for a product image that will only every load in woocommerce page and widgets?
This is a core problem that is being ignored by both wordpress and woocommerce
it is complete madness to generate all image sizes for post types when 90% of them will never be used.
it is just insanity creating all and every image size for all and every post type..
but the insanity really explodes if you add multiple images into a post/page/product..
OK its a problem having all the unused unnecessary images but understandable why they are being generated for the MAIN FEATURED IMAGE, the featured image is the one that will be used in widgets, thumbnails, Gallery and other locations etc etc
BUT Why oh why does wordpress/woocommerce generate all of the extra image sizes for every single other image in a post as well as the main featured image?
With woocommerce and a theme like Enfold installed for some reason I have 23 total image sizes in my site..
So we should be able to expect that the worst case scenario is that one of the images (the first image or main featured image will have 23 different sizes created that will be taking up space in the hosting server and that image generation process is going to cause considerable resource ussage on initial post save.
This is extremely wasteful..
But it get worse..
A lot worse
There is absolutely no need to generate any additional sizes for additional images that are found in the main body of a post or page or product description..
But by deafault wordpress DOES generate all of those sizes for all images in a post
so in a post/page or woo product that has 10 total images in the description , the first one we can consider the main image or “featured image”
we will get 230 total images generated (23 size versions for each of the 10 images) !!!
WTF GUYS …
Wordpress Woocommerce Admins Please address this madness.
additional body images should not have ANY additional sizes generated.
they will never be called anywhere, they are in the post body so why?
this is causing so many problems
If it creates 23 image for the first image only that will be 500 X 23 = 11500
then there would be 9 more images per post 9×500=4500
so worst case scenario should be 16000 (if it was restricted to just the first image getting multiplied)
that is IF the core was making sure NOT to generate those extra images..
But the reality is that a woocommerce site using a premium theme like Enfold with 500 products in it and 10 images per product will generate 115,000 images!
that is just pure INSANITY!
and it really hurts if you bulk add products…
OR use a plugin like REGENERATE THUMBNAILS!
When will the ADMINS and DEVS at WordPress and Woocommerce address this crital issue..
It is a huge and major flaw but nobody seems to really want to deal with it.
often when there are issues related to images theme developers or wordpress forum admins throw around oh just use the “Regenerate Thumbs” or “Simple Image Sizes” plugins and regenerate your thumbnails. .
Either they are totally unaware of the implications or they just don’t care if regenerating thumbs with those plugins Takes your server down..
so if you have that 500 product store with 10 images per product page you just ordered your server to create 125000 images right now so at best case its going to take quite a while to complete but more than likely even on a high end dedicated server you can expect your CPU and memory to hit 100% and crash your server guys, better hope your not on a shared server or you can kiss your account goodbye until you ring and beg your host to unban your account.
and good luck trying to successfully run asnd download a site backup!
too many innodes anybody?
please wordpress admins and devs fix this insanity.
Every wordpress user should be worried and concerned about this issue and should be demanding that it be addressed.
surely its not a hard issue to fix!
first of all make sure that those extra images are only for the designated featured image and NOT every single additional image in every single post type.
OK, Rant over.. I just hope it gets heard.
]]>PHP Notice: Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3736
PHP Notice: Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3738
PHP Notice: Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3740It destroys several database tables and totally consumes the cpu and memory of the server. I’ve been finding more and more people with the same errors wondering what causes it, so you might want to take a look at it.
]]>Really hope you guys can help me! My debug.log is showing a lot of notices/warnings and after a while my server shuts down. The server can run well for days, or just seconds before it crashes and needs to be reset (there is no patern). It looks like it has something to do with the WP database and querys but I can’t figure out what to do.
These 3 lines just keep on repeating themself
PHP Notice: Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3736
PHP Notice: Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3738
PHP Notice: Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3740And every so often this line pops up
PHP Notice: get_wp_title_rss was called with an argument that is <strong>outdated</strong> since version 4.4.0. Use <code>document_title_separator</code>-filter instead . in /wp-includes/functions.php on line 4045
This goes on for awhile and eventually my server decides to shut down
PHP Warning: mysqli_real_connect(): MySQL server has gone away in /home/vespacia/public_html/wp-includes/wp-db.php on line 1531
PHP Warning: mysqli_real_connect(): Error while reading greeting packet. PID=5183 in /home/vespacia/public_html/wp-includes/wp-db.php on line 1531
PHP Warning: mysqli_real_connect(): (HY000/2006): MySQL server has gone away in /home/vespacia/public_html/wp-includes/wp-db.php on line 1531
PHP Warning: mysqli_query(): MySQL server has gone away in /home/vespacia/public_html/wp-includes/wp-db.php on line 1924
PHP Warning: mysqli_query(): Error reading result set's header in /home/vespacia/public_html/wp-includes/wp-db.php on line 1924
PHP Warning: mysqli_real_connect(): (HY000/2002): Connection refused in /home/vespacia/public_html/wp-includes/wp-db.php on line 1531
PHP Warning: Error while sending QUERY packet. PID=5139 in /home/vespacia/public_html/wp-includes/wp-db.php on line 1924
PHP Warning: mysqli_real_connect(): (HY000/2002): No such file or directory in /home/vespacia/public_html/wp-includes/wp-db.php on line 1531
WordPress databasefout MySQL server has gone away bij query
SELECT l.ID, post_title, post_content, post_name, post_parent, post_author, post_modified_gmt, post_date, post_date_gmt
FROM (
SELECT wp_posts.ID
FROM wp_posts
WHERE wp_posts.post_status = 'publish'
AND wp_posts.post_type = 'reply'
AND wp_posts.post_password = ''
AND wp_posts.post_date != '0000-00-00 00:00:00'
ORDER BY wp_posts.post_modified ASC LIMIT 100 OFFSET 12200
)
o JOIN wp_posts l ON l.ID = o.ID
gemaakt door require('wp-blog-header.php'), wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WPSEO_Sitemaps->redirect, WPSEO_Sitemaps->build_sitemap, WPSEO_Post_Type_Sitemap_Provider->get_sitemap_links, WPSEO_Post_Type_Sitemap_Provider->get_posts
PHP Warning: mysqli_real_connect(): (HY000/2002): Connection refused in /wp-includes/wp-db.php on line 1531
PHP Warning: mysqli_real_connect(): (HY000/2002): No such file or directory in /wp-includes/wp-db.php on line 1531
PHP Warning: Error while sending QUERY packet. PID=5167 in /wp-includes/wp-db.php on line 1924
PHP Notice: wpdb was called <strong>incorrectly</strong>. wpdb must set up a database connection for the use of 'escaping'. Read <a href="https://codex.www.ads-software.com/Debugging_in_WordPress"> WordPress troubleshooting </a> for more information. (This message has been added in version 3.6.0.) in /home/vespacia/public_html/wp-includes/functions.php on line 4161
PHP Warning: mysqli_real_connect(): (08004/1040): Too many connections in /home/vespacia/public_html/wp-includes/wp-db.php on line 1531
PHP Warning: mysqli_real_connect(): (HY000/1040): Too many connections in /home/vespacia/public_html/wp-includes/wp-db.php on line 1531I also came across a couple of these lines but there are only a few of them
WordPress database error Table 'wp_options' is marked as crashed and should be repaired bij query SELECT option_value FROM wp_options WHERE option_name = '_transient_external_ip_address_77.170.21.115' LIMIT 1 gemaakt door require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce->init, WC_Customer->__construct, WC_Data_Store->read, WC_Customer_Data_Store_Session->read, WC_Customer_Data_Store_Session->set_defaults, wc_get_customer_default_location, WC_Geolocation::geolocate_ip, WC_Geolocation::get_external_ip_address, get_transient, get_option
WordPress database error Duplicate entry '_transient_external_ip_address_77.170.21.115' for key 'option_name' bij query INSERT INTO <code>wp_options</code> (<code>option_name</code>, <code>option_value</code>, <code>autoload</code>) VALUES ('_transient_external_ip_address_77.170.21.115', '2a01:7c8:aab6:b:5054:xxxx:xxxx:xxxx', 'no') ON DUPLICATE KEY UPDATE <code>option_name</code> = VALUES(<code>option_name</code>), <code>option_value</code> = VALUES(<code>option_value</code>), <code>autoload</code> = VALUES(<code>autoload</code>) gemaakt door require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce->init, WC_Customer->__construct, WC_Data_Store->read, WC_Customer_Data_Store_Session->read, WC_Customer_Data_Store_Session->set_defaults, wc_get_customer_default_location, WC_Geolocation::geolocate_ip, WC_Geolocation::get_external_ip_address, set_transient, add_option
WordPress database error Table 'wp_options' is marked as crashed and should be repaired bij query SELECT option_value FROM wp_options WHERE option_name = '_transient_external_ip_address_77.170.xxx.xxx' LIMIT 1 gemaakt door require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce->init, WC_Customer->__construct, WC_Data_Store->read, WC_Customer_Data_Store_Session->read, WC_Customer_Data_Store_Session->set_defaults, wc_get_customer_default_location, WC_Geolocation::geolocate_ip, WC_Geolocation::get_external_ip_address, get_transient, get_option
WordPress database error Duplicate entry '_transient_external_ip_address_77.170.xxx.xxx' for key 'option_name' bij query INSERT INTO <code>wp_options</code> (<code>option_name</code>, <code>option_value</code>, <code>autoload</code>) VALUES ('_transient_external_ip_address_77.170.xxx.xxx', '149.210.xxx.xxx', 'no') ON DUPLICATE KEY UPDATE <code>option_name</code> = VALUES(<code>option_name</code>), <code>option_value</code> = VALUES(<code>option_value</code>), <code>autoload</code> = VALUES(<code>autoload</code>) gemaakt door require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce->init, WC_Customer->__construct, WC_Data_Store->read, WC_Customer_Data_Store_Session->read, WC_Customer_Data_Store_Session->set_defaults, wc_get_customer_default_location, WC_Geolocation::geolocate_ip, WC_Geolocation::get_external_ip_address, set_transient, add_optionEdit, and these:
PHP Notice: Undefined index: host in /wp-includes/canonical.php on line 461
PHP Notice: Undefined index: host in /wp-includes/canonical.php on line 462
PHP Notice: Undefined index: host in /wp-includes/canonical.php on line 463
PHP Notice: Undefined index: host in /wp-includes/canonical.php on line 465
PHP Notice: Undefined index: scheme in /wp-includes/canonical.php on line 482WordPress 4.9.8, theme and all plugins are up to date.
Apache version: Apache/2.2.27
PHP version: 7.1.0
MySQL version: 5.1.73
(If needed I have acces to everything)
Best regards,
Alrik