Toolserver-l August 2009

toolserver-l@lists.wikimedia.org

48 participants
32 discussions

Phoenix appending stdout to .out file
by Mike.lifeguard 05 Aug '09

05 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have been using phoenix and cron to keep my IRC bots alive for some time, however I never previously needed to see their output. The bots are written in python, and use print(), which sends data to stdout. When running in terminal or screen for example, this is the screen. However, when using phoenix, the claim is that stdout is redirected to be appended to a .out file. However, it seems not to actually be doing that, and the outfile contains only phoenix's output (useless, can we have a --quiet option?), and not the output of the bot (useful). I've also become a tad confused with the crontab entries. Currently, they have >/dev/null so emails aren't sent ten thousand times a day or whatever - would this also redirect the output of the actual python script? An answer here, or on https://wiki.toolserver.org/view/Phoenix would be most welcome. Thanks, - -Mike.lifeguard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkp5BqoACgkQst0AR/DaKHvaugCbBGpbsd4CPiuzFFpSjCF2d18O iRgAoJY7jquVnY3AWigSZPPY2Sa5C0f+ =GASa -----END PGP SIGNATURE-----

4 4

The Norwegian toolserver
by Lars Aronsson 05 Aug '09

05 Aug '09

Earlier this spring, there was some talk, perhaps within the newly founded Wikimedia Norway chapter, to set up a common server in Norway for analysing database dumps and running bot scripts, i.e. a toolserver with everything except the database replication. Did this happen? Are there a bunch of such servers around the world today? Is there a list of such servers? Should we encourage people to do this, or should we try to concentrate work (and pool resources) to the (real / German) toolserver? Concentrating to fewer servers has the advantage that people can get a single account there, and join each project that is already there. Distributing over multiple, independent servers has the advantage of offloading the central server. It might also seem like an attractive project for a new Wikimedia chapter, since a server of their own looks like an achievement in itself. But it is also a waste of resources to maintain separate servers, if these resources could instead be pooled. -- Lars Aronsson (lars(a)aronsson.se) Aronsson Datateknik - http://aronsson.se

16 32

s1 maintenance
by River Tarnell 05 Aug '09

05 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, at some point either today or over the weekend i will be reimporting s1. the server holding s1 will be reinstalled at the same time. there will be a few hours of downtime while the new database is imported, then some replication lag. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkpzDysACgkQIXd7fCuc5vLBhgCeL+W3m6bdLYJKU4pxmL8X6Tax nqIAniBi5hCTamr/v933mEAy0MLhNxLC =UOp1 -----END PGP SIGNATURE-----

2 3

Re: [Toolserver-l] where's enwiki_p on s1?
by Lilewyn 05 Aug '09

05 Aug '09

I'm curious, would it be worthwhile to add a tsadmin-editable textbox to status.toolserver.org, that way the toolserver admins could just point at it in the future, and we users would eventually learn to check there for service ETAs instead of asking directly? ~ Kylu ----- Original Message ---- Date: Tue, 4 Aug 2009 18:43:43 -0400 From: Aryeh Gregor <Simetrical+wikilist(a)gmail.com> Subject: Re: [Toolserver-l] where's enwiki_p on s1? To: toolserver-l(a)lists.wikimedia.org Message-ID: <7c2a12e20908041543v3655df44xb1f59b2a3cbc8580(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Tue, Aug 4, 2009 at 2:31 PM, DaB.<WP(a)daniel.baur4.info> wrote: > the truth is that we don't know it. If all goes well, it take a few days (I > think River meant "days" insteadt of "hours") to reimport a cluster. Should we > say next time "It need 1 month" and then after maybe 4 days "We are back > ealier!" (the Scotty-methode) - would that help? We can give the best estimate we have, and revise it occasionally as things progress. Like "The dump should take something like 2-4 days if all goes well, and potentially much longer if errors occur and it has to be restarted." If the initial estimate turns out to be wrong, we can revise it. In this case we gave a bad estimate and then didn't give revised estimates once the original estimate was clearly wrong. That's an understandable mistake on our part given the givens (volunteers etc.), but it's also understandable that it will annoy users if we forget to give them essential information, and we shouldn't be snapping at them for getting annoyed at our failures. __________________________________________________________________ Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php

2 1

where's enwiki_p on s1?
by Ja Ga 05 Aug '09

05 Aug '09

Is it coming back soon? All my stuff is broken, and people are losing patience. - Jason

10 14

directory offline
by Stefan Kühn 04 Aug '09

04 Aug '09

Hello, since yesterday the directory /mnt/user-store is offline. I need this directory for the big dumps. Please reactivate this directory. Thanks Stefan

3 3

Fwd: [Commons-l] Maintainers of collection of flickr tools
by Casey Brown 03 Aug '09

03 Aug '09

Some people on these lists might be interested. ---------- Forwarded message ---------- From: Bryan Tong Minh <bryan.tongminh(a)gmail.com> Date: Mon, Aug 3, 2009 at 6:35 AM Subject: [Commons-l] Maintainers of collection of flickr tools To: Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org> Hi all, In the past few years I have been creating some Flickr related tools. These are: * FlickreviewR: A bot that reviews the licenses from images uploaded from Flickr * FlickreviewR human reviewer: A bot that re-reviews reviews by humans * Flickr upload bot: A web interface that allows easy access FlickreviewR has over 110k edits and with Flickr upload bot over 12k uploads have been performed. Unfortunately I have not always been able to care of those bots decently. Therefore I would like to propose to add maintainers to those bots; preferably as a stable toolserver project on stable.toolserver.org. Who would be interested in maintaining these bots? The bots are written in Python and use the mwclient library to edit and upload, which I also wrote. I will also give commit access to mwclient on SourceForge to maintainers. The FlickreviewR bots' code are in relatively good shape, reasonably ok documented and can be easily understood I believe. The Flickr upload bot however has horrible code. It was basically my first large webapp and I had some strange design ideas by then. I have attempted rewriting it, but have not had the time yet. Feel free to forward this mail to other people who might be interested in co-maintaining. Regards, Bryan _______________________________________________ Commons-l mailing list Commons-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/commons-l

1 0

How to use the Postgis-Database on Cassini
by Peter Körner 03 Aug '09

03 Aug '09

I would like to ask if anyone knows how and from where to use the postgis database on cassini. When logging on to cassini directly I'm able to query the local postgresql-database from command line, but on cassini I didn't find a perl or python module which enables me to connect to the database, nor is there php installed. From nightshade and willow I can't connect to cassini via command line nor IMHO via python or perl. I know that the osm-integration is a new thing, but it would be so cool if I could use the existing world-database on cassini to build my tools upon. So where should I run my tool (cassini, nightshade/willow or wolfsbane) and how could i connect to cassinis database? I already asked on maps-l but as i'm unsure if this question also touches the other toolservers, i'll go on and post it here too. please forgive me if i shouldn't have done this. I'm very new to the toolservers so I'm unsure about who's responsible for what. Peter

2 2

01 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, in the past we provided the login.toolserver.org alias, which pointed at the login server. we have decided to deprecate this alias, because: 1. it didn't really work, since changing login server requires much more work than just changing an alias. 2. now we have two login servers, it's not clear which 'login' should refer to. to avoid breaking anything, we will leave the alias in place, but i suggest updating any uses of it to refer to a particular login server (nightshade or willow). - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkpldMIACgkQIXd7fCuc5vJKFwCfRiFThpcVMWt/9Hbk8XU7nBLN +VYAniFNrOE6vkHV/v6QAhBBYfNJimDC =bi5p -----END PGP SIGNATURE-----

9 11

Stable editcounter URL breakage and JIRA issues
by Ilmari Karonen 01 Aug '09

01 Aug '09

It seems that the URL <http://stable.toolserver.org/editcount> (note, no trailing slash) is returning a 302 redirect to <http://localhost:4880/editcount/>, which is obviously not going to work. The URL <http://stable.toolserver.org/editcount/> with a slash works fine, though. Also, I tried to report this issue on JIRA (<https://jira.toolserver.org/>), but it seems my account (vyznev) can only create issues on the "Account Approval" project, even though I've successfully files issues on other projects in the past. Also, the JIRA link on the stable editcounter page points to the old URL <https://jira.ts.wikimedia.org/browse/EDITCOUNTER>, which gives a big error message about an expired and invalid SSL certificate. -- Ilmari Karonen

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Toolserver-l August 2009