Toolserver-l

toolserver-l@lists.wikimedia.org

1612 discussions

Maintenance on hyacinth
by River Tarnell 20 Jul '10

20 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am about to remove hyacinth (sql-s[346]-fast) from rotation for some internal testing. It will return to service in the testing configuration in a day or two. In the mean time, cassia (the non-fast server) will continue to serve these clusters, but there will be no redundancy in case of failure. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkxFj5IACgkQIXd7fCuc5vLWtQCgi5ZiDRYTCPWqsl286rujvRCX jesAn2TKWnlxucp0OZt4Xbt4VGomXNke =9zLT -----END PGP SIGNATURE-----

1 0

Software upgrades
by River Tarnell 10 Jul '10

10 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Later today (Saturday) I will upgrade some software on the Solaris login and web servers. A list of all software to be upgraded is at the end of this mail. In general, this should not affect users. However, if you have built local software (e.g. C programs or Perl modules) against libraries in /opt/ts, you should be aware that some libraries have bumped their sovers. The affected libraries are: * libhistory * libjpeg * liblcms * libMagickCore * libMagickWand * libpng * libreadline * libyaz Any software linking against these libraries will need to be recompiled, or it will fail with an error like this: ld.so.1: convert: fatal: libjpeg.so.7: open failed: No such file or directory - river. perl512/TSperl512-DBI 1.611 perl512/TSperl512-Class-MOP 1.03 perl512/TSperl512-Digest-SHA1 2.13 perl512/TSperl512-Moose 1.08 perl512/TSperl512-Mouse 0.62 perl510/TSperl510-Class-MOP 1.03 perl510/TSperl510-DBI 1.611 perl510/TSperl510-App-Cronjob 1.101660 perl510/TSperl510-Digest-SHA1 2.13 perl510/TSperl510-Moose 1.08 perl510/TSperl510-Mouse 0.62 perl5/TSperl5-LWP 5.835 perl5/TSperl5-Email-Abstract 3.002 perl5/TSperl5-Error 0.17016 perl5/TSperl5-IO-Socket-INET6 2.65 perl5/TSperl5-Log-Log4perl 1.29 perl5/TSperl5-Net-Ident 1.23 perl5/TSperl5-POE-C-IRC 6.35 perl5/TSperl5-POE-C-Pluggable 1.26 perl5/TSperl5-WWW-Mechanize 1.64 *audio/TSlibogg 1.2.0 *audio/TSlibvorbis 1.3.1 *database/TSlibmysqlpp 3.1.0 *database/TSsqlite 3.6.23 devel/TSant 1.8.1 devel/TSautoconf 2.66 devel/TSautomake 1.11.1 devel/TSbzr 2.1.2 devel/TSgcc44 4.4.4 devel/TSgit 1.7.1.1 devel/TShg 1.6 devel/TSintltool 0.41.1 devel/TSpkgconfig 0.25 *devel/TSsubversion 1.6.12 devel/TSswig 2.0.0 editors/TSemacs 23.2 editors/TSnano 2.2.4 editors/TSvim 7.2.445 fonts/TSdejavu-fonts 2.31 gnu/TSdiffutils 3.0 gnu/TSgtar 1.23 graphics/TSgnuplot 4.4.0 *graphics/imagemagick 6.6.3-0 *graphics/TSlcms 2.0 graphics/TSgraphviz 2.26.3 *graphics/TSjpeg 8b *graphics/TSliblqr 0.4.1 *graphics/TSlibpng 1.4.3 *graphics/TSlibtiff 3.9.4 *graphics/TSpango 1.28.1 *graphics/TSpixman 0.18.2 *graphics/TSrrdtool 1.4.4 *irc/TSirssi 0.8.15 irc/TSpython26-supybot 0.83.4.1 *libs/TSapr 1.4.2 *libs/TSgmp 5.0.1 *libs/TSlibconfuse 2.7 *libs/TSctemplate 0.97 *libs/TSlibedit 20100424-3.0 *libs/TSlibgsf 1.14.18 *libs/TSicu 4.4.1 *libs/TSicu-gcc 4.4.1 *libs/TSlibsigcxx 2.2.8 libs/TSlibtool 2.2.8 *libs/TSlibxml2 2.7.7 *libs/TSmpfr 3.0.0 *libs/TSpcre 8.10 *libs/TSproj4 4.7.0 *libs/TSreadline 6.1 *libs/TSslang 2.2.2 *libs/TSyaz 4.0.11 mail/TSexim 4.72 net/TSlftp 4.0.9 *net/TSlibevent 1.4.14b *net/TSopenldap 2.4.23 security/TSsudo 1.7.3 sysutils/TSmbuffer 20100526 sysutils/TSnagios-core 3.2.1 *sysutils/TSopenssh 5.5p1+hpn13-v9 *sysutils/TSpbzip2 1.1.1 textproc/TSgawk 3.1.8 textproc/TSgrep 2.6.3 *www/TScurl 7.21.0 www/TSlynx 2.8.7rel.2 www/TSphp53-apc 3.1.3p1 *x11/TSatk 1.30.0 *x11/TSlibXext 1.1.2 *x11/TSlibXrender 0.9.6 *x11/TSlibX11 1.3.4 *x11/TSlibXt 1.0.8 *x11/TSlibxcb 1.6 *x11/TSlibXdmcp 1.0.3 x11/TSx11-xproto 7.0.17 x11/TSx11-xtrans 1.2.5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkw4DXwACgkQIXd7fCuc5vL3KQCbB10AWGwyqqfgk7PFlve8veOZ Ly0AmQHH7ztiyoOkPwbCHJr81pp0ZidN =KFZ5 -----END PGP SIGNATURE-----

1 1

Change of default Perl version from 5.10.1 to 5.12.1
by River Tarnell 09 Jul '10

09 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Some time after next Friday (16th), we will change the default Perl version (that is, /usr/bin/perl) on the Solaris login servers and web servers from 5.10.1 to 5.12.1. This should not require any changes from users; however, you might want to test your tools with /usr/bin/perl5.12. After the change, /usr/bin/perl5.10 will be available for a short period, but will then be removed. If you have a problem with Perl 5.12, rather than changing your tools to use /usr/bin/perl5.10, file a request in JIRA. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkw3HlgACgkQIXd7fCuc5vIWJgCgl4U3TeI/cC7wekW9P1OTge8w sroAnRPcCwIh8pzu9eVoyZ1TCUNjADHN =AU03 -----END PGP SIGNATURE-----

1 0

is it OK to run a websocket server ?
by ThomasV 08 Jul '10

08 Jul '10

In order to celebrate the release of Firefox 4, I have created a tool that forwards recent changes from IRC to a web browser via websockets. Two examples : *Wikipedia's recent changes, unfiltered : http://toolserver.org/~thomasv/wprc.html *The combined recent changes of six Wikisource subdomains. This page plays a sound whenever a wikisource page has been proofread : http://toolserver.org/~thomasv/rcsound.html I would like to know if it is acceptable to let this tool run on the toolserver. It currently uses port 9999, and I have limited the bandwidth to 100 messages per second; I can lower this limit if needed. The code is in /home/thomasv/wsbot/servlet.py Thanks Thomas

2 2

Wikimedia power failure
by River Tarnell 05 Jul '10

05 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Earlier today there was a power failure at one of Wikimedia's facilities in Tampa which affected the master database servers that we replicate from. This caused an interruption in replication for a couple of hours (but no changes were being processed during most of that time). This also caused a short outage of the web services (JIRA, MediaWiki and FishEye) which are hosted in that facility. The problem is now fixed and replication is running normally; however, due to the nature of the failure, there may be inconsistencies in the database between the master and replicated copies. Please report this in JIRA if you notice any problems. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkwxXe8ACgkQIXd7fCuc5vKh0ACgswGEtGuR3tcyeKx2eq/6Ufpo 8mIAoJdef1vhbNWDnQHNFlYOBCITKdn4 =2Asx -----END PGP SIGNATURE-----

1 0

Power outage tomorrow
by River Tarnell 01 Jul '10

01 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, EvoSwitch have informed us that there will be a further power outage tomorrow (July 2) at 03:00 UTC to permanently resolve the cause of the previous outage. The only affected server (damiana) is currently not hosting any services, so there should be no impact to users from this outage. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkwsw/EACgkQIXd7fCuc5vI8bQCgkB9Ty986wwj808P19AbHZp7+ KE4AoJSFuBNQmJ7Kpawah+WJNHj5g4n2 =LmNG -----END PGP SIGNATURE-----

1 0

Power outage
by River Tarnell 30 Jun '10

30 Jun '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, At about 22:30 UTC last night (Tuesday) one of our power circuits went down for about 15 minutes. This affected one node of the HA cluster which was hosting the following services: Sun Grid Engine master server tsbot IRC bot DNS recursor MySQL server for sql-toolserver MySQL replication support infrastructure LDAP server All services failed over to the other node and were online again within 22 seconds. However, MySQL did not respond well to losing its replication connection and had to be restarted manually, causing about 30 minutes replication lag. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkwqh5YACgkQIXd7fCuc5vKQTwCgm1RTRwqQcaSpg7M4IL7brHGi ZF0An0EuetoI6PyQ9/1KYwBIAoym+Ta6 =omgy -----END PGP SIGNATURE-----

3 3

ts-admins language
by River Tarnell 29 Jun '10

29 Jun '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, Just a reminder: although the Toolserver is hosted by Wikimedia Deutschland, not all our admins (i.e., me) are fluent in German. You will therefore get a faster response to your request when you write in English. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkwpn/oACgkQIXd7fCuc5vIBiQCgs0aZWvUy6mcJm4E2yCyy7ZRT VdYAn3dVPD3Nd4BuSlpZPFXbAxt0CueF =mhIj -----END PGP SIGNATURE-----

9 13

Update of kernel and reboot on/of nightshade tomorrow evening.
by DaB. 27 Jun '10

27 Jun '10

Hello all, I need to reboot nightshade, because of a kernel-update. The reboot will take place tomorrow (Monday) at 20 o'clock UTC. The downtime will be between 5 and 15 minutes (5 minutes if nothing goes wrong). You can track the issue at [[MNT-675]] and if you are login on nightshade, you will get several notifies before the reboot too. Sincerly, DaB. -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

1 0

CAPTCHA can be required for logins from toolserver hosts
by Carl (CBM) 24 Jun '10

24 Jun '10

At the moment, logins to enwiki from nightshade.toolserver.org are throwing up a CAPTCHA. This is easy to check by loading http://en.wikipedia.org/wiki/Special:UserLogin in w3m or another browser from that host. Logins from willow.toolserver.org do not require a CAPTCHA at the moment. The CAPTCHA requirement makes it impossible for bots to log in via the API. The fundamental problem is that bots are run automatically, of course. But the API also does not report the CAPTCHA requirement at all, so bot developers are given a "WrongPass" error that they have to investigate to find that a CAPTCHA is the problem. This CAPTCHA situation has happened before, most likely due to some erroneous bot on toolserver triggering it. But individual bot operators cannot fix it, and so to them it has the same effect as a toolserver outage. Moreover, whatever bot operator caused it probably has no way to know it was them. It seems like this may take collaboration between toolserver and wikimedia to fix, but probably the fix will involve at least some change on the wikimedia side. So I have filed a bug at https://bugzilla.wikimedia.org/show_bug.cgi?id=23982 to coordinate discussion there. - Carl

7 9

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