-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
According to our maintenance schedule, February 7th would usually be a
general maintenance. However, due to the problems with s3/s7 we have
not had enough time to plan it; there will therefore be no maintenance
this time.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (NetBSD)
iEYEARECAAYFAk1Enq8ACgkQIXd7fCuc5vLrUQCfT7bJEpisyeVpZnNiEfhkM8nu
NcsAn0a7RiZd4ef+KgVem5WbbAiAlRtZ
=92od
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We have moved phpMyAdmin to a new host. This should not affect users,
but please open a request in JIRA if you find any odd problems with it.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk0/GKEACgkQIXd7fCuc5vIgxACgmil7NmPpx2myeBdwQqWNwTOg
kjgAnjKzphlrKKVU8/8VLkfNPNrdMnbS
=RxHX
-----END PGP SIGNATURE-----
Hello all,
with the beginning of the next year (2011) I will not longer accept new
interwiki-bot-accounts, if:
-The homewiki of the bot has at least one active interwiki-bot, which runs on
the toolserver, OR
-The homewiki has less then 1000 articles.
(There can be exceptions if there is a good reason of course)
The homewiki is that wiki where the bot starts and where the account-requester
got his/her bot approved (see [1]).
If the account-requester requested the account only for the interwiki-bot, the
request will be rejected; if he/she requested the account also for other
things, only the interwiki-bot will be denied of course and the rest of the
request will be handled the normal way.
For interwiki-bots which runs already on the toolserver, there is no change at
the moment. When you find a free minute: Please add your bot to [2] and check
if there are inactive bots listed for your wiki.
The goal of this change is to limit the number of interwiki-bots on the
toolserver (and improve our documentary a bit).
Sincerly,
DaB.
[1] https://wiki.toolserver.org/view/Account_approval_process, Request
process, Point 4.
[2] https://wiki.toolserver.org/view/Wikimedia_bots
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
After the s3/s7 split at Wikimedia, which moved several databases from
s3 to the new s7 cluster, we retained both databases on the same (s3)
server, which is our usual policy in such cases.
Unfortunately, over the last couple of days Wikimedia executed several
DROP DATABASE statements on their s7 server, for the old s3 databases.
These statements were replicated to our s3/s7 server and dropped the
live databases on our server. As a result:
* Several s3 databases (all of which start with 'a') are no longer
available
* s3 replication is halted due to the missing databases
* s7 replication is halted to prevent further destruction of data.
The only way to resolve this issue is to re-import the data from
Wikimedia's databases, which will take a few days at least.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk01800ACgkQIXd7fCuc5vKLMACeIN62eR9PXNDy475V9GLP3Edx
vggAmwUieFLO2hbF6S9NpJh/K3JsFx9G
=nI96
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Shortly we will move user databases on the s3/s4/s6/s7 server from the
current primary (cassia) to the secondary server (hyacinth). hyacinth
will become the new primary server. This will involve a couple of hours
read-only time for user databases during the move.
Due to the current problems with s3/s7 this maintenance is being done
outside the normal schedule.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk028soACgkQIXd7fCuc5vJH2gCggv1qjvygWzAM+sUVljUqtZ12
iG0An2fMIRacYeffR9o+hfJ13y8juocm
=vj5q
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We have set up a pair of redundant hosts to act as SGE job submission servers.
These work by sharing each user's cronietab between both hosts, and executing
jobs on whichever server is working. This avoids that problem where jobs run
from cronie on one login server (such as willow) will fail to run if that host
is down, even when other login servers are available.
To use the new hosts, log into submit.toolserver.org and set up a cronietab
(*not* a crontab) as normal.
Note that these hosts are *only* for submitting SGE jobs, not for running tools
on.
For now this service could be considered experimental, but I don't foresee any
problems with it.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk0tewgACgkQIXd7fCuc5vJKpQCeOwDC6Y2/0rBkzGFj6A2WT1DS
aaQAn0yhdkmZikrbXPdPL26EsQ5A+r+1
=PDMJ
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I've made a couple of changes to cronsub in response to some issues reported by
users. Specifically:
* cronsub now requires that the script file be executable, and will raise an
error if it's not. The previous behaviour was that non-executable scripts
would be executed by /bin/sh. If this affects you, the fix is to make the
script executable (chmod +x).
* Previously, SGE would copy the job script to a shared directory and execute
it there. For example, if you submitted $HOME/test.py, it would be copied
to a file such as /sge62/default/spool/wolfsbane/job_scripts/117333 before
starting. This was unfortunate for Python users who depended on Python's
behaviour of treating the script's directory as part of the "import" search
path.
This behaviour has been changed, so that the script file will be executed in
its original location.
I appreciate that the first item may be a breaking change for some users.
However, on balance this seems like the lesser evil.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk0ny8sACgkQIXd7fCuc5vK1UwCfaIt9gOSWym8sDOKR8bekuUaK
Qy4AoLLJIB1xaUjeKdpUHLZ6npg/0FiS
=VV97
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
It's now possible to set environment variables in your $HOME/.environment file,
as a series of NAME=value pairs, for example:
PYTHONPATH=$HOME/pylib
This will affect interactive logins, cron jobs and SGE jobs, but currently not
web server CGI scripts.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk0mH1EACgkQIXd7fCuc5vJrWwCgt+nTHauHPBIJ2+jhw3J2tkPt
COcAnAurVJt1Wncm6WDM8eX/h0RkTz7+
=KJ0E
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Since the switch to Solaris a few people have complained about the Sun 'cron'
not being very good. As an alternative to cron, we have now installed
'cronie', which is the RedHat Linux version of cron. This is based on Vixie
cron and offers an almost identical feature set to the old cron on
nightshade.
To avoid a conflict with the system cron, the cronie crontab command is called
'cronie'. To convert your current crontab to a cronietab[0], you can use a
command like this:
% crontab -l >crontab # list existing crontab to file
% cronie crontab # install same as a cronietab
% crontab -r # remove old crontab
You should probably use either crontab or cronie, but not both, since that
could be confusing.
- river.
[0] Yes, "cronietab" is a fairly stupid name. Sorry.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk0lXhoACgkQIXd7fCuc5vKuEACdHkfvuZeTdT8MmMmNpgY1O/t6
7PwAn1tk+uJ9czNa+MBWQWP4vndzN+Et
=FIKF
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Effectively immediately we are discontinuing support for the jobserver (that
is, the "job" command) on willow. The replacement for the jobserver is SGE:
<https://wiki.toolserver.org/view/Job_scheduling>
If you current use the job server, please migrate your jobs to SGE and then
delete them. We will not shut down the job server until all users have
migrated.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk0lIyIACgkQIXd7fCuc5vLYxQCgkpBdrvdYiCBDe/4QR2Xx4tDU
K/AAn1LeTo77idvq4jYB72HbNeqrSwor
=je9C
-----END PGP SIGNATURE-----