Last modified: 2010-06-26 09:38:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T5121, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 3121 - Watchlist Error in MediaWiki 1.4.7
Watchlist Error in MediaWiki 1.4.7
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.4.x
PC Windows 2000
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-11 21:14 UTC by Ninam
Modified: 2010-06-26 09:38 UTC (History)
0 users

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


Attachments

Description Ninam 2005-08-11 21:14:30 UTC
Configuration:
    MediaWiki: 1.4.7 
    PHP: 5.0.3 (apache) 
    MySQL: 4.1.10-nt-max-log

A database query fails in SpecialWatchlist. With empty db SpecialWatchlist works
correct. On 3rd or 4th submission got an answer: 

Database Error

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 "LinkCache::addLinkObj". MySQL returned error "2006: MySQL
server has gone away (localhost)".

With new user situation is normal with empty Watchlist until few changes.
Comment 1 Brion Vibber 2005-08-12 05:00:21 UTC
Check MySQL's error log.
Comment 2 Ninam 2005-08-12 14:13:11 UTC
snap from ErrorLog
<quote>
050812 15:46:41  InnoDB: Started; log sequence number 0 6079002
F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-max-nt: ready for connections.
Version: '4.1.10-nt-max-log'  socket: ''  port: 3306  MySQL Community Edition (GPL)
050812 16:19:00 [Warning] Aborted connection 24 to db: 'ninam' user: 'nina' host: `localhost' (Got 
an error reading communication packets)</quote> ?
Comment 3 Rob Church 2005-12-15 19:50:14 UTC
No follow-up for a few months, so assuming this is resolved or was abandoned or
taken to the mailing list. Chances are it was an end-user's server problem, and
it doesn't affect a recent release version.

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


Navigation
Links