Either tsbot or the Query killer are broken I just got an email about
a killed query (Not the issue) and query killer said the lag was
around 14000 seconds while tsbot and the relag graph are showing
almost no lag.
Sorry for the spam, but the ContentHandler changes especially may affect
you -- if you have any time this weekend or next week to do some
testing, we'd appreciate it. Thanks.
-Sumana
-------- Original Message --------
Subject: Please notice and report big glitches - changes coming
Date: Fri, 12 Oct 2012 17:14:05 -0400
From: Sumana Harihareswara <sumanah(a)wikimedia.org>
Organization: Wikimedia Foundation
To: Coordination of technology deployments across languages/projects
<wikitech-ambassadors(a)lists.wikimedia.org>
On Monday we start deploying a new version of MediaWiki, 1.21wmf2, to
the sites, starting with mediawiki.org and 2 test wikis
(https://www.mediawiki.org/wiki/MediaWiki_1.21/Roadmap). 1.21wmf2 will
have 3 big new things in it and we need your help to test on the "beta"
test site http://deployment.wikimedia.beta.wmflabs.org/wiki/Main_Page
now to see if there are any really critical bugs.
1) The new ContentHandler (
https://www.mediawiki.org/wiki/ContentHandler ) might affect handing of
CSS and JavaScript pages, import/export (including PDF export), and API
stuff, especially when rendering and editing. I'd suggest we also look
out for issues in template rendering, images and media handling,
localisation, and mobile device access. (merged on Oct 9)
2) High-resolution image support. This work-in-progress will try to
give higher-res images to high-density screens that can support it, like
new Retina displays. More info at
https://gerrit.wikimedia.org/r/#/c/24115/ . One of the bigger risks of
the high res stuff is load-based, since we may see substantial new load
on our image scalers. So *all* image scaling might be impacted. (merged
on Oct 11)
3) "Sites" is a new backend to represent and store information about
sites and site-specific configuration. This code is meant to replace
the current interwiki code, but does not do so just yet. Still, keep an
eye out for site-specific configuration or interwiki issues.
Right now the version of MediaWiki on the beta cluster dates from 9 Oct
and thus has ContentHandler but not the high-res image support or Sites.
So please test on the beta sites now and look out for these issues on
your sites in the weeks ahead.
https://www.mediawiki.org/wiki/Category:MediaWiki_test_plans has some
ideas on how to find errors.
Thanks! With your help we can find bugs early and get them fixed before
they affect lots of readers and editors.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hello all,
a few users contacted me about their not running cron-tasks. A often found
problem is, that the cron-lines of these user are like the following:
0 0 * * * DoSomething
or
0 * * * * DoSomething
In a ideal world that would be no problem, but in real world that CAN be a
problem. Why? Because many users have the same idea and our submit-hosts fail
than with
(CRON) CAN'T FORK (child_process): Not enough space.
Last night 41 tasks were successful started at midnight, an unknown number
failed.
Of course we could just hit the problem with buying new hardware, but most
time of the day these hosts do idle.
So how to solve this problem? It's easy: Spread the load. Most times a task
(like a bot) do not care if it is started a few minutes earlier or later. So
choose a minute that is unlike 0 and not divisible without remainder by 5.
If it really does not matter for you when your task starts, then take the
position of the first letter of your user-name and add 2 ("dab" → "d" → 4 → 6).
To not produce a misunderstanding: If your task REALLY needs to start at
minute 0 (or at midnight): do it. An of course cron-tasks are failing for
other reasons to, so contact me (jira-bug preferred) if you have a problem.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello all,
like announced in July [1] the default arch of SGE will switch soon from
solaris to *. Originally that should happen at 1. October, but I forgot
the re-announce it and I'm sure some of you forgot about it too. So the switch
is hereby announced for
9. October, 20:00 UTC.
Jobs that are executed after this timestamp and has no arch-option will run on
any host (linux or solaris) instead of a solaris-host.
There are 4 ways for you to prepare (sorted):
-Make sure that you program runs on linux AND solaris, add "arch=*".
-Make sure that you program runs only on linux, add "arch=lx".
-Make sure that you program runs only on solaris, add "arch=sol".
-Do nothing, pray and see things break.
(Somehow I have the feeling most of you will choose 4…, please make me wrong).
Sincerely,
DaB.
[1] http://lists.wikimedia.org/pipermail/toolserver-announce/2012-
July/000506.html
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello all,
doing last check-ups before the switch of SGE's arch tonight I discovered that
the linux-hosts had a problem with the mail-system. I fixed the problem, but
now all mails that were stored will be delivered to you – so if you receive
many emails about SGE-jobs (and other things) that are a few days old, that's
nothing to worry.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello,
I will add more disk space to rosemary / sql-s1-user on
12th October 19:00-22:00 UTC
The user databases for s1 will not be accessible for about two hours.
sql-s1-rr (without user tables) will stay available during the maintenance.
Cheers
nosy
Hello,
I will add more disk space to adenia / sql-user on
10th October 19:00-21:00 UTC
The user databases will not be accessible for about one hour.
Cheers
nosy
Hi,
is there an option to have qsub/qcronsub mail me the output
of a command instead of writing it to disk? Something simi-
lar to regular cron/at?
TIA,
Tim
Hello all,
in these days WMDE (the chapter that finance the toolserver) is discussing the
budget for the next year (2013); you can find it at [1]. At the moment there is
no money for new toolserver-hardware in this budget and the CEO Pavel Richter
is unwilling to change this ([2] in german) – because he fears that there will
be a Wikilabs in 2014. It is not possible for me to run the toolserver for
another year with the current hardware – you all know why. For this reason I
will request a change of the budget at the general meeting at November, so
there will be a vote about. If this vote should fail (and we get no money for
new hardware), I am going to retire from my job as root at 30. December 2012.
I'm not longer able to tolerant the behavior of the german chapter and the WMF
in matter of the toolserver; I do this for free and for fun, and it is not
longer fun.
Sincerely,
DaB.
P.S: If you are in a board of a chapter that gives money to WMDE for the
toolserver: Make sure that it will be spend for hardware.
[1]
http://meta.wikimedia.org/wiki/Wikimedia_Deutschland/2013_annual_plan_draft…
[2]
meta.wikimedia.org/wiki/Talk:Wikimedia_Deutschland/2013_annual_plan_draft/d…
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
(Dutch below)
After the successful hackathon in 2012 it's time for the Wikimedia
Nederland Hackathon 2012. The Hackathon will take place on Saturday 10
November, the day after our annual Wikimedia Nederland Conference.
The approach is the same as last year: We'll arrange a location, food
and drinks. You all come with your laptops and good ideas. Some possible
topics:
* TS-reports
* Good old Mediawiki
* Pywikipedia
* Wikidata
* GLAMwiki toolset project
* Open Cultuur Data
* ...
This hackathon doesn't aim, like the Berlin Hackathon, to be a global
Hackathon. It aims to be more of a regional hackathon. We have a very
limited budget for travel and accommodation
More information and registration at
https://nl.wikimedia.org/wiki/Hackathon_2012/en
------------
Na de succesvolle hackathon in 2011 is het op zaterdag 10 november tijd
voor de Wikimedia Nederland Hackathon 2012. Dit is de dag na de
Wikimedia Conferentie Nederland.
De opzet zal hetzelfde zijn als vorig jaar: Wij zorgen voor een locatie,
hapjes en drankjes. Jullie komen met de laptops en de goede ideeën. Een
aantal mogelijke onderwerpen:
* TS-reports
* Good old Mediawiki
* Pywikipedia
* Wikidata
* GLAMwiki toolset project
* Open Cultuur Data
* ...
Deze Hackathon richt zich niet, zoals de Hackathon in Berlijn, op alle
ontwikkelaars wereldwijd, maar heeft een meer regionaal karakter. We
hebben dan ook een zeer beperkt budget voor reizen en accommodatie.
Meer informatie en inschrijven op
https://nl.wikimedia.org/wiki/Hackathon_2012
Maarten Dammers
Wikimedia Nederland