We've recently been getting orphaned posts in our database. I've looked through other threads here about orphaned posts, and the common problems do not seem to be at work:
--The forum has been on line since 2003, we have done no imports;
--We do not delete users as policy, and the users involved are regular posters with plenty of other posts;
--We do not hard delete anything, only soft delete or move threads to an admin area;
--All the posts in question are orphaned because they reference a thread not in the database.
There are 120 of them so far. 118 of them have occurred after we upgraded to 3.7.3 on 8/27, 111 are after we applied PL1 on 9/2. Other than that I cannot find any pattern to them. Here's a short list of what I see:
myisamchk shows no errors, nor are any logged in the mysql error log. In fact, I have not even had any user complaints - I found this quite by accident when trying to figure out something else.
Any thoughts? Has anyone else seen this?
What I'm going to do is create a new thread in the admin section and assign that thread's ID to all these posts, then let the mod crew try to figure out where they came from. But the most recent ones were yesterday, and I'd like to figure out the cause & stop it.
FWIW during the period from 9/2 to the present we have had 2,200 new threads and almost 160,000 new posts, so this is a very small percentage of the activity but still it's odd.
--The forum has been on line since 2003, we have done no imports;
--We do not delete users as policy, and the users involved are regular posters with plenty of other posts;
--We do not hard delete anything, only soft delete or move threads to an admin area;
--All the posts in question are orphaned because they reference a thread not in the database.
There are 120 of them so far. 118 of them have occurred after we upgraded to 3.7.3 on 8/27, 111 are after we applied PL1 on 9/2. Other than that I cannot find any pattern to them. Here's a short list of what I see:
Code:
mysql> select post.postid, post.threadid, post.userid, from_unixtime(post.dateline) as posted from post left outer join thread on (post.threadid = thread.threadid) where thread.threadid is null; +---------+----------+--------+---------------------+ | postid | threadid | userid | posted | +---------+----------+--------+---------------------+ | 2315531 | 66393 | 32180 | 2008-06-21 17:11:42 | | 2431019 | 68171 | 13692 | 2008-07-30 02:47:02 | | 2545340 | 69505 | 33207 | 2008-08-23 19:28:19 | | 2572707 | 69773 | 2868 | 2008-08-28 14:39:31 | | 2573186 | 69781 | 34749 | 2008-08-28 16:53:57 | | 2573191 | 69781 | 33554 | 2008-08-28 16:54:47 | | 2582730 | 69855 | 34252 | 2008-08-29 20:02:38 | | 2583904 | 69874 | 34777 | 2008-08-29 22:33:23 | | 2583916 | 69874 | 34777 | 2008-08-29 22:34:09 | | 2583923 | 69874 | 32899 | 2008-08-29 22:34:39 | | 2594728 | 69989 | 33992 | 2008-08-31 18:42:25 | | 2607507 | 70121 | 34268 | 2008-09-02 21:32:10 | | 2612085 | 70227 | 34241 | 2008-09-03 15:46:50 | | 2612144 | 70227 | 1837 | 2008-09-03 15:55:40 | <snipped> | 2771382 | 72513 | 34858 | 2008-10-03 18:44:13 | | 2772948 | 72526 | 34590 | 2008-10-04 00:21:16 | | 2773676 | 72543 | 34954 | 2008-10-04 09:33:43 | | 2773688 | 72543 | 34535 | 2008-10-04 09:42:52 | +---------+----------+--------+---------------------+ 120 rows in set (50.61 sec)
Any thoughts? Has anyone else seen this?
What I'm going to do is create a new thread in the admin section and assign that thread's ID to all these posts, then let the mod crew try to figure out where they came from. But the most recent ones were yesterday, and I'd like to figure out the cause & stop it.
FWIW during the period from 9/2 to the present we have had 2,200 new threads and almost 160,000 new posts, so this is a very small percentage of the activity but still it's odd.
Comment