I’m unable to login to the site: https://karavalixpress.com/
It is running on “WordPress with NGINX and SSL packaged by Bitnami” on Amazon ec2.
I also raised a ticket on Bitnami Forums: https://github.com/bitnami/vms/issues/837
Looks like they don’t have any insights into this
I enable the DEBUG MODE, And found these major errors:
WordPress database error: [Table ‘wp_options’ is read only]UPDATE
wp_options
SET option_value
= '1681396523.5065269470214843750000' WHERE option_name
= '_transient_doing_c
WordPress database error: [Table ‘wp_usermeta’ is read only]UPDATE
wp_usermeta
SET meta_value
= 'a:1:{s:64:\"1710e0695c0eb73e731b74b7ba52d26644fc0ae647c48e7c927b5832e090d2ba\";a:4:{s:10:\"expiration\";i:1681569323;s:2:\"ip\";s:14:\"162.158.235.63\";s:2:\"ua\";s:117:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36\";s:5:\"login\";i:1681396523;}}' WHERE user_id
= 4 AND meta_key
= 'session_tokens'
Can anyone help me how to fix this?
]]>For some time i have a problem with slow loading time of the front page of my site https://opserver.mk/ (post loading is ok). I checked everything that i could find on the internet, but could not find the source of the problem. I’ve installed everything from the beggining including a new theme, but after importing database tables post and post meta, the front page could not be loaded. I reduced the number of content to the last 150 days with a code and the site is working now but the front page is again slow.
I used this code to reduce the number of posts:
delete from wpqg_posts
where datediff(now(), wpqg_posts.Post_Date) > 150;
SELECT * FROM wpqg_postmeta pm LEFT JOIN wpqg_posts wp ON wp.ID = pm.post_id WHERE wp.ID IS NULL;
DELETE pm FROM wpqg_postmeta pm LEFT JOIN wpqg_posts wp ON wp.ID = pm.post_id WHERE wp.ID IS NULL;
When i test the page on https://gtmetrix.com/reports/opserver.mk/aiW87Qxl/ i noticed this:
https://opserver.mk/wp-content/uploads/2023/02/problem.jpg
How to find out what is causing that second request and why is so long?!
Tried to turn on slow_query_log with this code, but i don’t have the privilages:
mysql> SET GLOBAL slow_query_log = 1;
Somehow everything is pointing to think that there is some query to the database that it need long time to finish….
]]>Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
Function mcrypt_create_iv() is deprecated since PHP 7.1 and removed since PHP 7.2; Use random_bytes() or OpenSSL instead
Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
The constant \MCRYPT_DEV_URANDOM\" is deprecated since PHP 7.1 and removed since PHP 7.2"
]]>I’ve never seen this error before and have had no issues before the recent security update.
Any help would be gratefully received. I can not see anything untoward in the site health that would flag this.
]]>I get a max_user_connections issue when I activated the plugin on the site. I’ve already checked for other plugins and theme conflict but it’s only occurred when I activated the ultimate member plugin. I’ve tried increasing the max_user_connections but it’ didn’t work. Please kindly help to solve this issue.
User x already has more than ‘max_user_connections’ active connections in /public_html/wp-includes/wp-db.php
Thanks
]]>[26-Jan-2021 05:31:17 UTC] WordPress database error Server shutdown in progress for query SELECT * FROM wp0d_posts WHERE ID = 81792 LIMIT 1 made by require(‘wp-blog-header.php’), wp, WP->main, WP->parse_request, do_action_ref_array(‘parse_request’), WP_Hook->do_action, WP_Hook->apply_filters, CodistoConnect->parse, CodistoConnect->sync, wp_get_attachment_image_src, image_downsize, wp_attachment_is_image, wp_attachment_is, get_post, WP_Post::get_instance
[26-Jan-2021 19:11:07 UTC] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query SELECT * FROM wp0d_posts WHERE ID = 86012 LIMIT 1 made by require(‘wp-blog-header.php’), wp, WP->main, WP->parse_request, do_action_ref_array(‘parse_request’), WP_Hook->do_action, WP_Hook->apply_filters, CodistoConnect->parse, CodistoConnect->sync, wc_get_order, WC_Order_Factory::get_order, WC_Data_Store->__call, WC_Order_Data_Store_CPT->get_order_type, get_post_type, get_post, WP_Post::get_instance
[26-Jan-2021 19:11:07 UTC] PHP Fatal error: Uncaught Error: Call to a member function remove_order_items() on boolean in /home/customer/www/irontime-sales.com/public_html/wp-content/plugins/woocommerce-amazon-ebay-integration/woocommerce-amazon-ebay-integration.php:1629
Stack trace:
Suddenly while accessing my wordpress website there was an error shown “Database connection Failed”.
I have used the repair database option in the cwp_config file and repaired the database. Kindly help me with the below output from the repair function.
Some database problems could not be repaired. Please copy-and-paste the following list of errors to the WordPress support forums to get additional assistance.
wp_users: 45 clients are using or haven’t closed the table properly
wp_usermeta: 48 clients are using or haven’t closed the table properly
wp_posts: 46 clients are using or haven’t closed the table properly
wp_comments: 45 clients are using or haven’t closed the table properly
wp_options: Table is marked as crashed
wp_postmeta: 47 clients are using or haven’t closed the table properly
wp_terms: 22 clients are using or haven’t closed the table properly
wp_term_taxonomy: 44 clients are using or haven’t closed the table properly
wp_term_relationships: 44 clients are using or haven’t closed the table properly
wp_termmeta: 36 clients are using or haven’t closed the table properly
wp_commentmeta: 40 clients are using or haven’t closed the table properly