Hello all,
yesterday Merlissimo and I successfully tested the installation of the SGE-
version for the toolserver. The last step is now to install the new version on
the live-system. For that, the SGE-service needs to stop completely on the
cluster, the old version has to be removed and the new one has to be
installed. We plan to to this on
Thursday 5. July between 17:30 and 22:30 UTC.
During this time no SGE will work. There will be no restarting (and no
migration) of stopped things after the update.
After the update is done, we will start to use the 2 Linux-boxes for tools too
(I will send details than).
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello all,
I was asked by various Wikimedia-projects about details of the new no-
interwiki-bots rule; I will try to clarify some parts of it in this mail.
For first: The default interpretation of the rule is: no interwiki-bots. The
rule forbids the running of any interwiki-bot on the toolserver, if there is
no exception that permits the running.
The most important exception is the MMP interwikibot, which is lead by
Toto Azéro at the moment. The MMP is allowed to run several instances of
interwiki-bots and should cover every wikimedia-project in a fair manner.
Until rules are work out there will be no addings of other users to the MMP
(it would be great if the TS-users would work out the rules).
Another exception is the creation of a better interwiki-bot and the test-
running of it; an example is the new bot by Merlissimo. The test has to happen
in a MMP. Of course running the newest pythonwikibot for "testing" is NOT
subject of this exception (as long as it not the pywikipedia-MMP).
The last exception is the non-continuous-mode: That's NOT "Only 1 time per
week/day/hour".
Let's give a example what is covered by this exception: You are working in the
Italian Wikipedia and notice that an interwiki-link in an article points to
the wrong article in the English Wikipedia. You correct the interwiki-link,
but there a dozen of articles in other languages where the link is still wrong
– much boring work for a human. Here is it ok to run a interwiki-bot on the
toolserver to fix this fast.
Another example would be the correcting of hundreds of articles because a
Wikipedia-subproject re-organized the name-structure of a article-group.
What I had in mind as I declared this exception is, that the number of
articles the bot will correct is finite and the run-time of the bot is somehow
short.
What is not an exception:
*Running a bot in screen instead by cron or SGE
*Running a bot only "some time when my home-computer sleeps"
*Running a bot because "my Wikipedia is special"
There may be other valid exception or reasons to run a interwiki-bot; if you
plan to do this: open a JIRA-ticket and the roots will look at it (every TS-
user can leave a comment for course).
If there a further questions please ask on the ML or in the IRC.
Sincerely,
DaB.
P.S: You an substitute "interwiki" with "interlanguage" in this mail.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello all,
at Thursday, 26th June, between 11:30 and 16:30 UTC we will have a general
maintenance-window.
The main-reason for the maintenance-window is to install Solaris-updates. We
will reboot the Solaris-boxes after the updates are done – this INCLUDES
willow so please ensure that you have no open files anywhere on the cluster.
The reboots will be announced on the server 15mins before they happen, so you
will have a warning. In the past some reboot-cron-scripts were not executed
after a reboot so you should check that when the maintenance-window is over.
Another topic will be the update of JIRA and fisheye, so these services will be
away for some time during the maintenance-window.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello all,
willow was rebooted around 15:30 UTC because Mark was in the datacenter today
and he added some memory to our servers. We couldn't announce the reboot,
because we didn't know that Mark would be in the datacenter today. I'm sorry
if any data was lost, but on the plus-side the memory-extension should make
the usage of willow more easy for all of you.
Another topic: A default quota for each user without a quota was set tonight.
For some users the default will be too small: If you need more disc-space,
open a jira-bug or try to reach a root in the IRC and we will set a bigger
quota for you.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello,
today we have run a little bit short of disc-space on the /home-partition. I
searched for files with more than 500MB, hoping to find some old log-files that I
could delete before I tell you to clean-up. What I found was upsetting: The
biggest log-file I found was 74GB(!) big and several others were also dozen of
GB big. I deleted them all (a list can be found at [1]).
Guys, what is so hard to check from time to time a big a logfile is and
truncate it? Do I really have to speed-up the re-installation of the quota-
system so that you all have 256MB per default and angry mails are send if you
use more?
So please: Use the weekend to log into your toolserver-account, check how much
disc-space your use (use "du -hs your(sub)directoryhere" for that) and look if
you can do some clean-up. If everything is ok and you still use 5GB of disc-
space: no problem, if you need it, take it.
I will contact the top10-disc-users on Monday by email.
Sincerely,
DaB.
* [1] https://jira.toolserver.org/browse/MNT-1252
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885