[wp-trac] [WordPress Trac] #58559: Database error bug in wordpress current version
WordPress Trac
noreply at wordpress.org
Mon Jul 3 17:13:01 UTC 2023
#58559: Database error bug in wordpress current version
--------------------------+------------------------------
Reporter: zoddshop63 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Database | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
--------------------------+------------------------------
Changes (by sabernhardt):
* component: General => Database
Old description:
> 2023-06-16 8:52:53 47 [Warning] Aborted connection 47 to db:
> 'wordpressdb' user: 'wpuser' host: 'localhost' (Got an error reading
> communication packets)
> 2023-06-16 8:52:53 46 [Warning] Aborted connection 46 to db:
> 'wordpressdb' user: 'wpuser' host: 'localhost' (Got an error writing
> communication packets)
>
> I am constantly seeing read and write errors in database due to wordpress
> in the current version. I have been running wordpress for years.
>
> Upon checking the logs the read errors last query is
> SELECT SQL_CALC_FOUND_ROWS wp_posts.ID
> FROM wp_posts
> WHERE 1=1 AND
> (wp_posts.post_author = 2) AND ((wp_posts.post_type = 'post' AND
> (wp_posts.post_status = 'publish')))
>
> ORDER BY wp_posts.post_date DESC
> LIMIT 0, 32
>
> The write error last query is
>
> SELECT DISTINCT post_author FROM wp_posts WHERE post_type = 'post' AND
> post_status = 'publish' LIMIT 2
>
> Both queries execute fine manually. The problem is not related to
> timeouts or max allowed packets as both execute manually.
>
> I noticed they are both increasing the aborted clients value in mysql.
> There is also no quit sent at the end of the mysql connections.
>
> It seems to be a bug within wordpress. I have literally gone through
> everything else possible to solve this bug.
New description:
{{{
2023-06-16 8:52:53 47 [Warning] Aborted connection 47 to db:
'wordpressdb' user: 'wpuser' host: 'localhost' (Got an error reading
communication packets)
2023-06-16 8:52:53 46 [Warning] Aborted connection 46 to db:
'wordpressdb' user: 'wpuser' host: 'localhost' (Got an error writing
communication packets)
}}}
I am constantly seeing read and write errors in database due to wordpress
in the current version. I have been running wordpress for years.
Upon checking the logs the read errors last query is
{{{
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID
FROM wp_posts
WHERE 1=1 AND
(wp_posts.post_author = 2) AND ((wp_posts.post_type = 'post' AND
(wp_posts.post_status = 'publish')))
ORDER BY wp_posts.post_date DESC
LIMIT 0, 32
}}}
The write error last query is
{{{
SELECT DISTINCT post_author FROM wp_posts WHERE post_type = 'post' AND
post_status = 'publish' LIMIT 2
}}}
Both queries execute fine manually. The problem is not related to timeouts
or max allowed packets as both execute manually.
I noticed they are both increasing the aborted clients value in mysql.
There is also no quit sent at the end of the mysql connections.
It seems to be a bug within wordpress. I have literally gone through
everything else possible to solve this bug.
--
--
Ticket URL: <https://core.trac.wordpress.org/ticket/58559#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list