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
Hello all,
today I discovered (thanks to the mailing-list) that a few users have run
several bot-instances in parallel on willow. I'm sure that these people did it
by mistake, but it is annoying nevertheless and it is easy to fix: Use SGE.
The problem is that I wrote several of eMails about "use SGE!" already and
somehow it did not work as good as it should (if you converted you stuff
already: thank you and you can stop to read here ;-)). I understand that we
all are busy with our lives and Wikipedia and that we all love to "do it
right…later", but as you know that resources of the toolserver are limited. So
I hereby declare the following new rule:
All bots have to run by SGE. A bot is every program or script that makes
changes at a Wikimedia project. It does not matter if the bot runs
periodically or continuous. The only exclusions are a.) interactive bots, b.)
bots that can't run by SGE yet and c.) if you start a bot by hand for testing
(no screen, no cron, no while).
The rule will become active at Sunday, 10. February 2013. Exception b is
almost NEVER the case, if it runs on a shell it is VERY likely that it can run
by SGE.
Some time ago I wrote a simple SGE-how-to at [1]. Maybe you all can take a
look and correct things and make things more clear. In very most cases the
using of SGE IS easy.
Sincerely,
DaB.
[1] https://wiki.toolserver.org/view/SGE_for_beginners
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello all,
great parts of the toolserver-cluster were down or very slow in the last few
hours. AFAIS it was a problem with the user-store or rosemary (where the user-
store is physically connected). I rebooted rosemary, but the reboot showed
problems with its IPv6-address. I tried to fix that what caused several other
reboots. Rosemary is now up and running but the user-store is not available
(looks like Nosy just mounted it without updating the fstab-file). So I was
forced to remove the user-store everywhere (beside on willow because it need a
reboot to do that and a reboot is scheduled already later for today).
I will try if I can find the partition for user-store and mount it but I have
not much hope (there are way to many devices to try) – just to be clear: There
is no data lost. Also away will be munin, because its data is also mounted on
that host. I fear that we have to wait for Nosy to recover before we get the
user-store back.
tl;dr: TS had problems, user-store is away.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
while I was killing some bot-processes on willow to reduce the high load I
accidentally pressed return too early and killed a random number of processes
with that. I restarted the system-processes, but I am not sure if everything
is completely right. Just to be sure I hereby announce a reboot for tomorrow,
Monday, 19:05 UTC.
Willow will be away for some minutes. Please notice that the history shows
that cron on solaris does not start all processes during the reboot, so you
should check after the reboot if everything works. Please notice that in a few
minutes the new "no bots without SGE"-rule ([1]) becomes active, so please
make sure that your bot uses SGE or I might disable it.
I have no idea how many user-processes were killed, but I'm sorry that it did
happen nevertheless.
Sincerely,
DaB.
[1] http://lists.wikimedia.org/pipermail/toolserver-announce/2013-
January/000557.html
--
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885
Hello all,
for historical reasons s2 and s5 are together on one host (cassia). Because
cassia is quite overloaded, the sharing will end soon and I will move s2 away.
For this I need your help because s2 and s5 share also the user-databases and
there is not hint which user-database is needed where.
So if you use user-databases for joining with s2 (two!) please add the name of
the user-database to [1] until
Friday, 8. February 18:00 UTC.
It will take only a few minutes to add your user-databases there, so please do
it. If you do not your user-databases there your tools will break after the
split, but of course that can be fixed later.
Sincerely,
DaB.
[1] https://wiki.toolserver.org/view/User:Dab/s2-userdatabaes
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885