Apologies if this was already asked, but TangoTango wrote a very nifty
search tool, mayflower.
See it here on the test wiki: http://test.wikipedia.org/wiki/Special:Search
(you may need to be logged in)
It's really great, and it got added to commons
But unfortunately it's bumping into the 15 connection limit already.
Please wait, searching for "mayflower"...
Warning: mysqli::mysqli() [function.mysqli-mysqli]: (42000/1226): User
'tangotango' has exceeded the 'max_user_connections' resource (current
value: 15) in /home/tangotango/public_html/mayflower/search.php on line 258
Warning: mysqli::query() [function.mysqli-query]: Couldn't fetch mysqli in
/home/tangotango/public_html/mayflower/search.php on line 287
Warning: main() [function.main]: Couldn't fetch mysqli in
/home/tangotango/public_html/mayflower/search.php on line 469
Warning: mysqli::close() [function.mysqli-close]: Couldn't fetch mysqli in
/home/tangotango/public_html/mayflower/search.php on line 472
Please consider raising that limit, a lot. Not sure how much but a lot
because commons searches are quite frequent.
Work mail: lpieniaz at us.ibm.com
Hobby mail: lar at miltontrainworks.com
> Message: 1
> Date: Sun, 18 Feb 2007 00:25:47 +0100
> From: "DaB." <wp(a)daniel.baur4.info>
> Subject: [Toolserver-l] New limitation of mysql-connections
> To: Toolserver-ML <toolserver-l(a)lists.wikimedia.org>
> Message-ID: <1171754747.3681.2.camel(a)DanielX.intern.baur4.info>
> Content-Type: text/plain; charset="us-ascii"
> Hello all,
> I created a new limitation of 15 mysql-connections at the
> same time by a user (after a user flooded mysql with a few
> dutzend connection a few time ago).
> If someone need more connections, please mail me, the limit
> can set per user.
> Have fun :).
I created a new limitation of 15 mysql-connections at the same time by a
user (after a user flooded mysql with a few dutzend connection a few
If someone need more connections, please mail me, the limit can set per
Have fun :).
the replag of en and non-en is quite high at the moment. I think, it is
not good to have all languages with a high replag. I stoped
en-replication yesterday by a mistake and notice now, that non-en's
replag is decrease fast at the moment. So I think it is better to let
en-sync off for a while untill non-en is near null again. Zedler is just
not fast enough to catch up a high replag of non-en and en at the same
time. Perhaps zedler is fast enough to catch up en, when non-en is near
But there is also a good news for en: I mail to the verein 2 weeks ago
to get the money to buy a secound db-server for en (a copy of commons
and perhaps the user-dbs). I hear from a member of the verein-board a
few days ago, that the proposition was accept and so I wait only for the
With 2 db-server it should be no problem to have all languages with a
low replag for a (long) while.