Toolserver-l

toolserver-l@lists.wikimedia.org

1612 discussions

New hardware ordered
by Lilewyn 18 Jan '09

18 Jan '09

When we named nightshade, the theme was "poisonous plants". Current servers (from https://wiki.toolserver.org/view/Servers ) * Hemlock * Nightshade * Willow * Zedler (Not a poisonous plant, but names after Johann Heinrich Zedler, who was an 18th century German encyclopedist. This is in keeping with the WMF naming scheme.) * Yarrow * Vandale (As above, but Van Dale was Dutch.) * Clematis (Poisonous plant, not an encyclopedist) Short, usable, and thematic (poisonous plant) names might be: * Azalea * Daphne * Digitalis * Foxglove * Hellebore * Holly * Lilly * Oleander * Privet * Wolfsbane * Yew "Daphne", "Holly" and "Lilly" have the distinction of also being female names, which would give us another opportunity to confuse those trying to understand our naming schema. I'm rather fond of Azalea personally, though I think someone reminded me recently that "nightshade" was my suggestion, so I'll sit this one out. ~ Kylu __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/

13 16

Re: [Toolserver-l] Toolserver-l Digest, Vol 39, Issue 13
by Betacommand 18 Jan '09

18 Jan '09

My suggestion for the new server name is wolfsbane also Betacommand

1 0

commons-s1 replication lag
by Eusebius 15 Jan '09

15 Jan '09

Hi there, When looking at the replication lag, I see that s3 is not replicating and I understand the impact of it on the relationship between the tools and the projects hosted on s3. But I also see that commons-s1 is not replicating, and I don't understand anymore: if it is a replica of the Commons DB, tools working on Commons should be affected by it, right? But it seems not to be the case. What didn't I understand? Regards, Eusebius

2 1

potential abuse by 84.114.164.84
by Daniel Schwen 12 Jan '09

12 Jan '09

While looking at the access statistics of the Query-to-map tool I discovered that a large portion of the hits are generated by one single austrian DSL IP (90000 hits yesterday (9% of all hits that day), 55000 hits so far today, ). Seemingly random queries to lots of tools. Example: 84.114.164.84 - - [11/Jan/2009:14:03:43 +0000] "HEAD /%7Ekolossos/wp-world/umkreis.php?la=pt&lon=16.285&lat=48.134444&rang=50&map=1 HTTP/1.1" 200 0 "-" "Jakarta Commons-HttpClient/3.1" 84.114.164.84 - - [11/Jan/2009:14:03:49 +0000] "HEAD /~para/earth.php?latdegdec=48.134444&londegdec=16.285&scale=300000 HTTP/1.1" 301 0 "-" "Jakarta Commons-HttpClient/3.1" 84.114.164.84 - - [11/Jan/2009:14:03:49 +0000] "HEAD /~kolossos/wp-world/umkreis.php?la=nl&lon=16.285&lat=48.134444&rang=50&map=1 HTTP/1.1" 301 0 "-" "Jakarta Commons-HttpClient/3.1" 84.114.164.84 - - [11/Jan/2009:14:03:50 +0000] "HEAD /~kolossos/wp-world/umkreis.php?la=pt&lon=16.285&lat=48.134444&rang=50&map=1 HTTP/1.1" 301 0 "-" "Jakarta Commons-HttpClient/3.1" What is going on here? Proxy? Daniel P.S.: there is a webserver on that IP. Looks like a broken Mediawiki installation, a broken forum installation. No further info though.

6 5

Toolserver status for Signpost
by Aude 11 Jan '09

11 Jan '09

I am preparing the Technology Report for this week's edition of the Signpost on enwiki. (see http://en.wikipedia.org/wiki/User:Aude/Technology_report) I have some idea about how toolserver works, aware that there are issues with replication and that Yarrow (one of the servers) was down. What is the status now? It sounds like things are not 100% back to normal. How long (estimated) will it take to be back to normal? There are a number of tools linked from the featured article candidates pages. Are these all working 100%? What other tools are affected? http://en.wikipedia.org/wiki/Wikipedia:Featured_article_candidates/Typhoon_… Any information for the Signpost would be most appreciated. Cheers, -Aude

3 7

s3 replication is halted
by River Tarnell 07 Jan '09

07 Jan '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, as Wikimedia deleted the MySQL binlogs required for replicating s3 on the Toolserver, replication is now halted. a full dump/import is required to fix replication. because disk space on yarrow is limited at the moment, and we are about to receive new servers, i might wait until this before reimporting. (however, if that's likely to take a long time, i might do it sooner.) - river. -----BEGIN PGP SIGNATURE----- iD8DBQFJYWeSIXd7fCuc5vIRAo03AJ9ouEHS98oTwKPugzcUsc8Lp+LmSgCffFmd gK3xul+k9UinKPPHH5Q3PWg= =pnlB -----END PGP SIGNATURE-----

9 22

1200 MB every night
by emijrp 05 Jan '09

05 Jan '09

Hi; I run a script that downloads 1200 MB every night (from http://dammit.lt/wikistats/) to generate some stats (http://es.wikipedia.org/wiki/Wikipedia:Ranking_de_visitas). Any problem with that bandwidth usage? 30GB by month. Thanks, regards

5 5

maintenance 28th to 31st Dec: all servers
by River Tarnell 05 Jan '09

05 Jan '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 at some point between these two dates (exact date isn't yet known), Wikimedia will performance maintenance at the knams hosting facility, where the Toolserver is hosted. this will involve downtime for all servers as we will be moving to a new rack. i will combine this maintenance with the next Toolserver quarterly maintenance, which was previously scheduled for January 5th. the total outage period will be several hours. - river. -----BEGIN PGP SIGNATURE----- iD8DBQFJS08dIXd7fCuc5vIRAiVUAKCEKhl4a/K1J0gyoRHoZbocgtfGqgCeP4L5 P5rCTBWgi6D0nU4m7aWglE8= =dsYJ -----END PGP SIGNATURE-----

4 12

IPv6 on stable - thank you
by Marcin Cieslak 02 Jan '09

02 Jan '09

Hi, Big thank you for providing IPv6 for the stable toolserver. I think I was using it unknowingly since around Dec 14th, excellent idea - so thanks again. --Marcin

1 0

new web server testing (redux)
by River Tarnell 28 Dec '08

28 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, in one week i plan to enable the new web server on hemlock. this will hopefully solve the problems people are seeing with long-running scripts. until then, people should test their sites with the new server. you can do this by using 'toolserver.org:81' in the URL, instead of 'toolserver.org'. for example, if your tool is at: http://toolserver.org/~johnsmith/mytool.php you would use: http://toolserver.org:81/~johnsmith/mytool.php if everything works correctly, you do not need to do anything. if you have a problem, and cannot solve it yourself, please let me know and i'll investigate. if you use rewrite rules, you need to convert them to the new server's rewrite format. this page explains how to do that: https://wiki.toolserver.org/view/ZWS please do not distribute the toolserver.org:81 URLs (except for testing), as they will stop working in a week. if you are having problems with the current web server, and would like to be moved to the new one before a week, let me know. people who requested this during the last test have been moved to the new server already. that is: kalan agony luxo pathoschild the final change to the new web server, assuming there are no major problems, will be Tuesday, 2nd December. - river. -----BEGIN PGP SIGNATURE----- iD8DBQFJLCIwIXd7fCuc5vIRAkNMAJ0ZDE/5yb4HPyQElbQdEPiCSbKpbwCeK0sa bzTPCF5R7krqlYhCHkywuY4= =w8kw -----END PGP SIGNATURE-----

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Toolserver-l