Closed Bug 452953 Opened 17 years ago Closed 17 years ago

An error occurred in a database query!

Categories

(support.mozilla.org :: Forum, task)

task
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: evans.antony, Assigned: nkoth)

References

()

Details

(Whiteboard: sumo_only)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1pre) Gecko/20080830031750 Firefox/3.1b1pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1pre) Gecko/20080830031750 Minefield/3.1b1pre Displaying the forum list or an individual post sometimes results in a database error. Sample error message: An error occurred in a database query! Context: File tiki-view_forum.php Url tiki-view_forum.php?locale=en-US&forumId=1 Query: select * from `tiki_modules` where `position`= ? and (`type` is null or `type` !='h') order by `ord` asc Values: 0 l Message: MySQL server has gone away Built query was probably: select * from `tiki_modules` where `position`= 'l' and (`type` is null or `type` !='h') order by `ord` asc Reproducible: Sometimes
I got one too. Is this being caused by increased load due to the kb search not working? An error occured in a database query! Context: File tiki-view_forum_thread.php Url tiki-view_forum_thread.php?locale=en-US&comments_parentId=144900&forumId=1 Query: select `groupName` from `users_usergroups` where `userId`=? Values: 0 18 Message: MySQL server has gone away Built query was probably: select `groupName` from `users_usergroups` where `userId`='18'
Status: UNCONFIRMED → NEW
Ever confirmed: true
Severity: normal → critical
OS: Windows Vista → All
Hardware: PC → All
Target Milestone: --- → 0.6.4
This is happening all the time for me now. I can't get on the forums at all.
Status: NEW → ASSIGNED
Assignee: nobody → nelson
Mark, are you able to find out if this is due to a slow query, and if so, which one? I could do something about it...
We are currently not allowing queries to run for more than 30 seconds. When they hit 30 seconds, they are killed off, causing 'server has gone away' errors. For more information see bug #425135.
patch to allow admin to constraint query to a time range (instead of all time) in r18072(trunk) / r18073(production), as per recommendations in bug 425135 comment 47 Given the critical nature of this bug, when can we push these changes?
I'd be for pushing this if it's not pushing a lot of other stuff. Has stephend had time to look at it?
Blocks: 439749
I've been running a Selenium script which searches both staging and production SUMO, alternatively, for the past 45 minutes, without ado; the script is pretty basic, but varies search terms (numeric, alpha-numeric, alpha, non-sensical, common, etc.) Not sure if that's enough, but it's the best I can do right now...
So -- if this doesn't introduce regressions and fixes the immediate problem I'm okay with updating it as long as we're not pushing a bunch of other crap late on a Friday -- Nelson is there other stuff in this patch or... ?
Filed an IT bug in bug 453910.
By the way - for people wanting to do some forum admin. The workaround if you want to see the forums list is to add &time_control=7200000 (in seconds), e.g. http://support.mozilla.com/tiki-view_forum.php?forumId=1&time_control=7200000
Once the push is done, we need to set the time in the Admin Home... Forums panel. Recommended settings: Limit forum topic listings to recent (hours): 1440 Limit ranking listings to recent posts (hours): 720 Limit ranking listings of last posts or topics (hours): 2
This looks fixed to me. However, tiki-view_forum_thread.php appears to be still very slow (although no db error so far). That is now Bug 453936.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Has anyone seen this recently? I know we were seeing it last week when opening multiple articles concurrently...
I have not seen this error for a few days.
I haven't personally seen this nor heard of anyone else running into it either, so tentatively marking as VERIFIED FIXED. If we see it again, I suggest we file a new bug.
Status: RESOLVED → VERIFIED
Whiteboard: tiki_triage
Whiteboard: tiki_triage → sumo_only
You need to log in before you can comment on or make changes to this bug.