Hi all
I'm happy to let you know that new hardware has been ordered by Wikimedia
Deutschland and will arrive probably in about two weeks. We will get two new
systems:
* A more powerful web server, to replace hemlock: Sun Fire X4150, 2x Quad-Core
Xeon, 8GB RAM, 2x73GB SAS HDD. The current web server only has two cores.
* Another database server, to be used for S1 (english wikipedia), so S1 and S3
no longer have to share a server: Sun Fire X4250, 2x Quad-Core Xeon, 32GB RAM,
16x146GB SAS RAID.
This should improve performance and give us some head space for growth. Once the
new servers arrive, S3 will be re-imported too, so we will have live data again.
Any ideas for names? To stay with the nightshade theme, how about Jurubeba and
Erubia? Or perhaps we go the "witches' weed" way, with Datura and Mandrake?
Henbane is taken, i think. Amanita sounds nice, too :)
A third server has been ordered, which will also be installed in Amsterdam, but
will not be part of the toolserver cluster. It's a storage server (X4540, 24TB
RAID) that will keep a live backup of all media files.
Cheers,
Daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
During the next maintenance window (March 7th), we will make some
changes to how mail forwarding works. This will not affect most users,
but you should read this mail anyway, especially if you make use of
.forward files. A summary of the changes you might need to make are at
the end of this mail.
At present, all mail to user(a)toolserver.org is sent to your LDAP alias;
if you don't have an address set in LDAP, mail is sent to nightshade and
processed locally (which might include using .forward files). Locally
generated mail, e.g. cron, is handled by .forward; users with email
addresses set in LDAP have "username(a)toolserver.org" in $HOME/.forward
so it's forwarded properly.
After this change, mail to user(a)toolserver.org and mail to
user(a)ANYMACHINE.toolserver.org will be handled as follows:
* If $HOME/.forward exists, mail will be delivered to the address in
that file;
* If not, mail will be delivered to the user's LDAP email address, if
any if set;
* If none is set, mail will be delivered locally on either clematis or
hawthorn (*not* nightshade).
In addition, mail to user+foo(a)toolserver.org and
user+foo(a)ANYMACHINE.toolserver.org will be accepted, where "foo" can be
any string. This will be handled in the same way, except that
$HOME/.forward+foo will be checked instead of $HOME/.forward. This
allows you to process mail differently depending on the address (see
below for an example).
In summary, you should make these changes after the maintenance:
* If you do not do anything "special" with your mail, and you have an
LDAP mail address set, and your .forward file contains
"username(a)toolserver.org", then you do not need to do anything. We
will delete your .forward file during the maintenance, since it's no
longer necessary. This applies to the vast majority of users.
* If you have an LDAP email address set, and your .forward file contains
a different address, you should delete your .forward file after the
maintenance. We will not do this for you.
* If you do not have an LDAP email address set, and you have a .forward
file containing an email address, you do not have to do anything.
However, you *should* run 'setmail' to set an LDAP email address, then
delete your .forward file.
* If you do not have an LDAP email address set, and you do not have a
.forward file, then currently your mail will be delivered locally on
nightshade. After the maintenance, your mail will be delivered
locally on either hawthorn or clematis. We do not support this
configuration, and you should set an email address in LDAP so your mail
is forwarded. However, if you insist on having mail delivered locally,
you can continue to do so.
* If you currently rely on accepting mail to
user+foo(a)machine.toolserver.org and use .forward+foo to funnel this
mail to a program, then you do not have to do anything. However, you
*should* instead send mail to user+foo(a)toolserver.org, which does not
rely on a particular machine being up. Note that if you do this, the
incoming mail will be processed on either clematis or hawthorn.
The explanation of these changes is more complicated than the actual
changes. The result should be that mail processing is much simpler and
more obvious to users.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (NetBSD)
iEYEARECAAYFAk1pIIQACgkQIXd7fCuc5vKOkACfYd3na6TlCLOpuOiXWDEVBB1y
sdkAnilzSrqxYCgL0WalfYlwSt68yf4U
=2El7
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On the morning (UTC) of March 1 we will install some new hardware at the
Toolserver. Services will be affected as follows:
Service | Expected impact
----------------------------+--------------------------------
Databases: s3, s4, s6, s7 | User databases unavailable for
| < 10 minutes.
user-store filesystem | Unavailable for < 10 minutes.
Start time: Tuesday, 1st March, 1PM UTC (estimated)
http://time.tcx.org.uk/utc/2011/3/1/13/0
End time: Tuesday, 1st March, 4PM UTC (estimated)
http://time.tcx.org.uk/utc/2011/3/1/16/0
Details:
We will install new storage for databases and the user-store filesystem.
This requires installing HBAs in three servers: hemlock, cassia, and
hyacinth, which requires downtime. We will try to stagger the
installation of the two database servers so that those clusters
remaining accessible during the maintenance, but user databases will be
unavailable while hyacinth is down.
Before the maintenance on hemlock, we will forcibly unmount the
user-store filesystem. Any program accessing it at the time will
receive an I/O error.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (NetBSD)
iEYEARECAAYFAk1ro3AACgkQIXd7fCuc5vLhsQCfbKKphnxKxXCM3VNCJC+YOsz+
E5sAn3EBKJjF1PeU4WZCT5W9KFNuqGqM
=TGse
-----END PGP SIGNATURE-----
Hi,
I have a wrapper script that starts a handful of jobs on the
toolserver (via qsub). But, when I put that wrapper script as a
"normal" cronjob, I get some error messages about qsub not found.
Starting the wrapper via cronsub doesn't work either.
Anyone: What do I have to put in my .environment file (or whatever) so
that my "normal" cronjob can start qsub/cronsub jobs?
Thanks,
Magnus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm about to do some maintenance on ortelius, one of the web servers.
This should not have any impact of users.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (NetBSD)
iEYEARECAAYFAk1jx2kACgkQIXd7fCuc5vI7jQCgp23SaKkR/GLDRkt6U0xW1RqN
O3oAoI75koGwU1kVPcdkqe5SXmbjdEQV
=yQK1
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Python 3.2 is now available on the login servers. Anyone using Python
3.1 should switch to 3.2, since 3.1 is likely to be removed at some
point. People using 2.7 (the default) are not affected.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (NetBSD)
iEYEARECAAYFAk1h9UMACgkQIXd7fCuc5vKhgQCgp2w9cADOZjxf+G0kvGbg3a3o
RN0AoKsiOHJRNe1BaGFd6zw3e47baUS7
=YhIE
-----END PGP SIGNATURE-----
Hi all!
Wikimedia Germany is again organizing a hackathon in Berlin. It will be in May,
but we have not decided on the weekend yet. So, if you are interrested in
attending the event, please let us know on which dates you *can't* come. We are
especially interrested to know when people around the globe are tied up by exams
and such.
So, if you want to come, but might not be able to at some specific dates, drop a
note:
<http://www.mediawiki.org/wiki/Berlin_Hackathon_2011#Straw_Poll>
Thanks,
and see you there!
-- daniel
Today I can see an unknown file named 'core' with modification date
13/02/2011 at one of directory under public_html.
It is around 233 MB in size. It has been more a week from my last login.
Anything wrong??
--
Junaid P V
http://junaidpv.in
Hello all
Just a short question in [1] is mentioned how to trigger a mail in case
* the job starts
* the job finishes
what about
* the job print something to stdout like for CRON jobs (in the early
days... ;))
Thanks a lot for answering
Greetings
Dr. Trigon
[1]
https://wiki.toolserver.org/view/Job_scheduling#Receiving_mail_when_the_job…