Last modified: 2005-06-09 17:48:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 2159 - not working not working
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-05-12 18:09 UTC by luzi82
Modified: 2005-06-09 17:48 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description luzi82 2005-05-12 18:09:25 UTC
Warning:  mysql_query(): Unable to save result set in
/usr/local/apache/common-local/php-1.4/includes/Database.php on line 349

 A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:

    (SQL query hidden)

from within function "indexShowToplevel". MySQL returned error "1053: Server
shutdown in progress (".
Comment 1 Domas Mituzas 2005-05-14 14:06:51 UTC
works for me, could be overloaded database response though. 
Comment 2 Zigger 2005-05-15 15:32:35 UTC
I just got the same error on the same page.  If it's an overload response, can
the detection and reporting be improved?  Or is it really a database server
having to be shutdown urgently?
Comment 3 Zigger 2005-05-15 15:34:30 UTC
(In reply to comment #2)
The reported IP address was, "Served by ...".
Comment 4 Ævar Arnfjörð Bjarmason 2005-05-15 15:49:39 UTC
Warning: mysql_query(): Unable to save result set in
/usr/local/apache/common-local/php-1.4/includes/Database.php on line 349

from within function "indexShowToplevel". MySQL returned error "1053: Server
shutdown in progress (".
Comment 5 Brion Vibber 2005-05-15 20:30:38 UTC
Yes, that's an overload issue. The long queries get killed and the error isn't handled well.
Comment 6 Zigger 2005-06-09 17:48:07 UTC
This "error" is returned as an html fragment:

<br />
<b>Warning</b>:  mysql_query(): Unable to save result set in
<b>/usr/local/apache/common-local/php-1.4/includes/Database.php</b> on line
<b>349</b><br />
Error in fetchObject(): MySQL server has gone away
<li>GlobalFunctions.php line 513 calls wfbacktrace()</li>
<li>Database.php line 505 calls wfdebugdiebacktrace()</li>
<li>Database.php line 1466 calls databasemysql::fetchobject()</li>
<li>LoadBalancer.php line 188 calls databasemysql::getstatus()</li>
<li>LoadBalancer.php line 333 calls loadbalancer::getreaderindex()</li>
<li>DatabaseFunctions.php line 52 calls loadbalancer::getconnection()</li>
<li>MessageCache.php line 304 calls wfgetdb()</li>
<li>MessageCache.php line 249 calls messagecache::getfromcache()</li>
<li>GlobalFunctions.php line 435 calls messagecache::get()</li>
<li>GlobalFunctions.php line 344 calls wfmsgreal()</li>
<li>OutputPage.php line 620 calls wfmsg()</li>
<li>Database.php line 386 calls outputpage::databaseerror()</li>
<li>Database.php line 333 calls databasemysql::reportqueryerror()</li>
<li>Database.php line 698 calls databasemysql::query()</li>
<li>Database.php line 625 calls databasemysql::select()</li>
<li>SpecialAllpages.php line 78 calls databasemysql::selectfield()</li>
<li>SpecialAllpages.php line 29 calls indexshowtoplevel()</li>
<li>SpecialPage.php line 305 calls wfspecialallpages()</li>
<li>SpecialPage.php line 215 calls specialpage::execute()</li>
<li>index.php line 101 calls specialpage::executepath()</li>

This was from but a few minutes
previously it was returning the more common "(SQL query hidden)" variant without
the backtrace.  See bug 1109#c11 for another "gone away" error with a backtrace
from "action=submit" on

Note You need to log in before you can comment on or make changes to this bug.