Toolserver-l

toolserver-l@lists.wikimedia.org

1612 discussions

unschedule outage
by River Tarnell 16 Jul '09

16 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, at some time this morning (around 4AM GMT) there was a cooling issue at our colo which caused zedler (sql) to shut down. unfortunately no admins were around to fix it, so the total outage time was around 12 hours. the server is now up. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkpfTMEACgkQIXd7fCuc5vIexQCfWid297Suqhumd1bXrHEtK6X5 9jUAn23Brid2+l+U03iT6OgfdBH2VLzi =k9FL -----END PGP SIGNATURE-----

1 0

Wikimania
by Daniel Kinzler 16 Jul '09

16 Jul '09

Hi all I'm chairing a panel about the Toolserver at wikimania. So far I'm on my own (well, Mark might come along). Who will be there and would like to talk about what the toolserver is, how it works, or what coll stuff we have? I'd of course like to have some other admin with me, but "normal" users are welcome too. Having perhaps four people on stage would be nice. -- daniel

5 6

To people using pywikipedia framework
by Matias 12 Jul '09

12 Jul '09

Hi!, I recently got my toolserver account. Looking for a way to set my bots (using pywikipedia framework) to run, I noticed many people using the framework haven't set the correct access flags to their "login-data" dir (inside your /home dir). This could lead to someone using those files to run your bot accounts.Although only other toolserver users can see these files, its still an issue . Please make at least that dir "not readable" for anyone but "owner". --Pyr0.

2 1

unscheduled outage
by River Tarnell 07 Jul '09

07 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, there was an unscheduled outage at ~17:20 UTC for around 15 minutes, caused by a kernel panic on the NFS server (hyacinth). the cause is currently unknown. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkpSNW0ACgkQIXd7fCuc5vIXJwCcC6X/KSoRQxbw7Hhx9Pg5IMVo RGMAnixFovl7Sel53XoEQvvcTOw7dF/2 =fYOt -----END PGP SIGNATURE-----

2 3

Updating /mnt/user-store/stats hourly
by emijrp 06 Jul '09

06 Jul '09

Hi; Can anyone update /mnt/user-store/stats hourly? Thanks, regards

3 7

s2 server status
by River Tarnell 05 Jul '09

05 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, the new s2 server (daphne) is online, and should have caught up with replication later today. however, it is using a new MySQL build (version 5.1.35), which contains a critical InnoDB bug causing server crashes when innodb_locks_unsafe_for_binlog is enabled. since we need this option to support long queries, we won't switch servers until a patch is available. (this is a new bug, unrelated to the previous one.) i hope this will happen later this week. when we switch, user databases currently on the s2 server will _not_ be moved, and the 'sql' alias will continue to point at the old server (zedler). therefore, if you have created tables on the old server which you need to join to s2 databases, you will need to move these to the new server yourself. do not move normal user databases, they should remain on 'sql' as before. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAko+R7MACgkQIXd7fCuc5vIV9gCdGvqGabLQCienTQOB3Lk5ClyP l3EAoIZebLgBV8X6zeUIspNZNn1C8mlE =uYxB -----END PGP SIGNATURE-----

2 3

downtime
by River Tarnell 03 Jul '09

03 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, we lost power for unknown reasons last night, causing an outage of the Toolserver. most of the platform is back up, but s3 (yarrow) remains down. as we had downtime anyway, i took the opportunity to move stable to the new server. the old stable server (willow) is now offline. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkpNUyQACgkQIXd7fCuc5vLYgACgvU7x5J12wdvK7epJLqX7iLnA U/sAn2CvLg0tJTpc+mTBjieNFlXqvdnj =E+ap -----END PGP SIGNATURE-----

2 4

Little Project Idea
by K. Peachey 28 Jun '09

28 Jun '09

Heres a little side project idea for anyone interested: I often see people wanting dumps of one or two articles from a Wikipedia wiki (most commonly en) and most commonly have to resort to screen scraping via third party tools which isn't very nice and some times even blocked (at the squid level) although there is the API, it isn't exactly the most easier system for anyone to use. What might be nice is a little tool where people can enter a few article names in a box and click a button and have it produce the static html dumps of the desired article(/s).

7 10

[stable] server migration
by River Tarnell 21 Jun '09

21 Jun '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, given the current low uptake of stable server usage, we have decided we cannot afford to dedicate an entire server to it, which ends up being mostly idle. therefore we will be migrating the stable server to a zone (virtual machine) on hyacinth, which is also the new /home server. there should be no change in either reliability or performance as a result. unlike the previous move, no user intervention will be required this time. we are currently copying the existing /users and /projects directories to the new server. at switchover time, an incremental rsync will be done to copy any changes since then. you can log into the new server now, using the hostname "newstable.toolserver.org"; however, i recommend not changing any files, as they will be overwritten when the next copy is done. if you would prefer to edit files on the new server, let me know and i will exclude your project from the automatic copy. (it may take a while until you can log in, since not all .ssh directories have been copied yet.) i *do* recommend doing a quick sanity check of your software on the new server; for example, that any software or libraries it needs are available and work correctly. downtime for the final migration will be on Monday, 6th June, in line with the maintenance schedule for stable. we might begin the downtime slightly earlier than usual (5AM UTC) to allow time for the file copies. i would like to change to ZWS at the same time as the migration; if your project has no yet confirmed that it works with ZWS, *please* consider trying to do so before the migration, as it will make things much easier for us. this applies to: * wma * wmfgcbot if you are unable to complete the web server migration yourself, please ask for help, either on IRC or the mailing list. the move is accompanied by a more recent version of the TS package repository (/opt/ts), which includes newer versions of Perl, Python and other software. this is documented in more detail at: <https://wiki.toolserver.org/view/Solaris_software> for projects using third-party Python modules currently installed in /opt/ts/lib/python2.4/lib/site-packages, these will still be available after the move. however, we recommend changing to the Toolserver Python. after the move is complete, the existing stable server (willow) will be repurposed into a general login server. more details on this will follow later. lastly, we are still interested in more stable projects. stable server projects can have multiple maintainers, which reduces the workload on one maintainer, and means tools don't die when their maintainers leave. we are currently considering disabling the unmaintained web tools of expired user accounts, meaning these tools will stop working. stable tools will only be disabled if *all* maintainers leave, and no new maintainer can be found. additionally, the stable Toolserver has a well-defined maintenance schedule to avoid downtime during peak times, and has much less unplanned downtime than the normal Toolserver. if you would like to move a project to stable, open a request in the TS project in JIRA, describing the project and listing the initial maintainer(s). - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAko8YXMACgkQIXd7fCuc5vKkogCgkUtkExNsFNbczDCq9d4IbT6v S0sAmgLHns9mqnkzDwMjkICWpVnNJsI1 =11m+ -----END PGP SIGNATURE-----

7 9

communication with wiki communities
by Daniel Kinzler 17 Jun '09

17 Jun '09

Hi all during wikimedia germany's brithday party yesterday, I was asked to look into improving the communication between toolserver folks and the wiki communities using the toolserver. We have become an important part of their infrastructure, and when things break, they notice - but often don't know who to ask about it. So, I would like to propose a few things to improve this situation. 1) There should be a short description of the toolserver, with the relevant links, in the project namespace of each wiki that us the toolserver significantly. That page should be maintained by the local community of course, but I think it would be ideal if a toolserver user who is also a member of that community would help with that, or even start the page. I will do this for the german wikipedia soon. 2) we, the toolserver admins, should use the toolserver blog more to communicate what's going on with the TS. I guess several of the messages I posted here lately should have gone to the blog too. Maybe blog posts could be forwarded to toolserver-l automatically? posting the same thing to several places is annoying... 3) we should incurage people to describe their tools on the toolserver wiki, kind of like the description pages for extension on mediawiki.org. Perhaps we should have a guideline for this? The idea is to promote some more information about who we are, what we do, and how the toolserver works. And we should also help people to find the right person to contact when things break. What do you think? -- daniel

13 27

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