Hello all,
for a important kernel-update I need to reboot the linux-boxes today. The
reboot will happen
TODAY, 20:00 UTC.
The linux userland-boxes will be away for ~10min and the database-servers
(sql-s2 and sql-s2) for 30min (all values are estimates). Solaris-boxes are
not affected. The reboots will happen sequentially so SGE should re-schedule
tasks between the boxes so the downtime for each task should be short.
You can follow the progress at [1].
Sincerely,
DaB.
[1] https://jira.toolserver.org/browse/MNT-1297
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
I just started replication on the fresh dump of s5 and will import commons
later tonight. For tomorrow I plan a second try to move the user-databases
from the old s5-host to the new one. So I hereby announce a read-only-time of
s5 for
TOMORROW, 21:00 UTC
of unknown length (should take not that long because the owner of the biggest
databases contacted me telling that no movement is needed) – at minimum a few
hours.
I will also dump wikidata from this fresh dump and import it everywhere during
the next hours (so a correct wikidata-copy should be everywhere soon again).
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
to (hopefully) speed up s2 I need to restart mysql to bring some config-changes
live. Because of this there will be a downtime for sql-s2 starting
TOMORROW, 22:00 UTC.
The downtime should be less than 1h. You can follow the progress at [1].
Sincerely,
DaB.
[1] https://jira.toolserver.org/browse/MNT-1296
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
during the maintenance window yesterday evening the hole cluster was down for
~30min starting ~21:20 UTC. The problem was independent of the maintenance
working, but caused the window to extend.
The problem was an out-of-memory on one of our HA-nodes. Unfortunately the box
did not restart itself and its ha-buddy did not detect the problem too, so the
services of the out-of-memory-box were not switched to the other box. This
caused the hole cluster to stand until I manually rebooted the host. I will
look if I can find some kind of sensor for that; in worst case I will enable
our old "reboot if low on memory"-script again.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
to re-enable replication on cassia (sql-s5) I have to filter out wikikdata-
data. This requires a restart of the mysql-process. This restart will happen
TODAY, 20:00 UTC.
The downtime of s5 will be ~30 minutes.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
s5 (dewiki) is the next cluster for re-setup. I already got a fresh dump from
the WMF and imported it too on a server. The next step is to move the user-
databases over. For this I have to switch s5 into read-only. The read-only-
phase will start at
Tomorrow, Thursday after 13:00 UTC.
s5 carries a few very big user-databases, so I think the movement will take
more an 1 day. Below is a list of the biggest user-databases, maybe their
owners can take a look if some clean-up is possible?
Unfortunately s5 can not stay at the new place because the server belongs to
OSM. So a second read-only-phase will happen in near future (that one should
be a bit faster because I will just rsync files around instead of importing).
Sincerely,
DaB.
1.2G u_lvova_golem_s2_zh
1.3G u_hroest
1.3G u_rdf_bots
1.6G u_multichill_commons_categories_p
1.7G u_lvova_golem_s5_de
1.8G u_mauro742
2.7G u_dschwen
20G p_merlbot_dewiki_lists
51G p_globalusage_weekly_p
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
it looks like the WMF-techs are moving wikidata to cluster s5 at the moment
(without announcement of course).
I'm quite sure that this will break our wikidata-replication; so after my
sleep I will look how the situation will be and than probably re-import
wikidata everywhere (wikidata is still quite small at the moment so that's
still possible). So expect the wikidata replag to rise during the next hours.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hey all!
Sorry for crossposting - I hope to reach more people here than on
toolserver-l.
I am impressed! Wondering what tools are actually running on the
toolserver I started a list. It is long! You can admire it here:
http://www.mediawiki.org/wiki/Toolserver/List_of_Tools
For sure, it is incomplete as I used the toolserver wiki and jira to
find information.
In the light of building Tool Labs to become a platform the tools can
run on, we need more information about the tools. So here is what I ask
all tool developers for:
* Please check if your tools are on the list (correctly).
* Please fill in your software dependencies, data dependencies, use
patterns (are they running continously? or webservices? Batch runs?
etc.), the license.
* If you have not given your software an explicit license, please note
that only free software can migrate to Labs. Consider putting your stuff
under a free license.
* If you have already migrated your bot or tool to Labs and it is in the
list, please say so in the last column "status". The same if a mentioned
tool is abandoned and shall not move.
Thanks for your help!
Cheers, Silke
--
Silke Meyer
Systemadministratorin und Projektassistenz Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt
für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hi all!
I was thinking about the list of tools a bit more... In my opinion, this
collection of tools should be more visible to the world! There is so
much work and knowledge in there and partially you really have to dig to
find them...
There is this plan to create/improve Labs/Tool Labs so that tools can be
shared with others more easily. So one very important thing is to *know*
about existing tools.
How about dragging these tools into the spotlight? (The ones on the
toolserver as well as the ones already living in Labs.) The other day I
heard the proposal from a community member to have featured tools in a
visible place, e.g. a "tool of the month" or even of the week. I like
the idea! It could shortly present a tool, what it does, where to find
it and the person(s) behind.
What do you think of it? The first place that came to my mind where The
Signpost and/or German language Kurier where we could suggest this
topic. I'll be afk for the next few days and I'd be glad to read some
opinions when back. :)
Best, Silke
--
Silke Meyer
Systemadministratorin und Projektassistenz Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt
für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hello all,
to update a package with a security-problem, I have to restart z-dat-s2-b
today. This will cause sql-s2-user and sql-s2-rr to be down. The downtime wll
start at
TODAY, 19:20 UTC and should not more than a few minutes.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885