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
>> hi all
>>
>> many of our tools uses messages from betawiki because they are
>> translated in many languages.
>> But this messages must be synchronized and I think it's not very
>> economically if every user/tool do that self. Because of that I
>> propose
>> to create one database for all users which will be sync periodically.
>
>A database with one table per user? Sounds good.
>
>> What do you think? Are any other users interested for such a db?
>
>I would be interested.
>
>> Greetings,
>> Luxo
>
>Pietrodn
>powerpdn(a)gmail.com
I thought not one table per user, but rather one table for all messages.
On betawiki are a lot messages e.g.
http://translatewiki.net/wiki/MediaWiki:Abusefilter-revert-title/en.
So I would make a table something like
+
----------+------------------------+-----------------------------------------------------+
| LANG | MESSAGE |
TEXT |
+
----------+------------------------+-----------------------------------------------------+
| en | Abusefilter-revert-title | Revert all changes by
filter $1 |
+
----------+------------------------+-----------------------------------------------------+
| de | Abusefilter-revert-title | Alle Änderungen durch
Filter $1 rückgängig machen |
+
----------+------------------------+-----------------------------------------------------+
| fr | Abusefilter-revert-title | Révoquer toutes les
modifications par le filtre $1 |
+
----------+------------------------+-----------------------------------------------------+
the messages which will be synced should be one a list which every
ts-user can edit, so that it's easy for every user to add the messages
he requires.
--Luxo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
on Monday, 6 April between 5-7AM UTC, scheduled quarterly maintenance will take
place on the following servers:
zedler (s2), rosemary (s1), yarrow (s3), hemlock, amaranth, willow (stable)
expected downtime for each server is less than 15 minutes.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAknQ3OMACgkQIXd7fCuc5vIDhgCfWY1P+D+/wGdyv6BfLEfpVn0n
8XQAnRYKQkYETmEvn4D5UvCabNGjfY1n
=Cfx1
-----END PGP SIGNATURE-----
Hello all,
I think that when such a number of people come together it would be nice to
have a key-signing in Berlin. If you have no idea, what a key-signing is, look
at the wikipedia-article [[en:Key_signing_party]].
If you don't own a pgp-key yet and are an linux-user there are several how-tos
on the net to get one fast (there are how-tos for windows-users too, but it's
more complex, but that doesn't need to stop you).
Because there is no time (and place) for a hash-methode-keysigning (you know,
all standing in a line for hours ;)), I would organise a
list-methode-keysigning. That means that you send me
*Your nick (if you have one)
*Your realname (optional, but some people don't sign non-realname-keys)
*Your keynumber
*Your key-hash
*Your key (if it is not on normal key-servers)
to pgp(a)daniel.baur4.info.
I will make a list of that data. Then I (respectively the verein) will print
out several copies of that list and place them at central places (like the
reception or the c-base) for hand-out. You can also place sticker on your
nameplate (to let people easier find you) if you like (I have colorful
sticker-dots here ;)).
You will take such an list and start looking for other people, that stand on
the list, check your hash on his/her list and his/her hash on your list and
mark your name as checked on his/her list and his/her name on your list if
all is right. Then continue until all entries on your list are checked (or
the meeting is over).
It would be very nice if many people would participate to increase the level
of trust (at least the key-trust) between us.
Follow up to foundation-list.
Sincerly,
DaB.
P.S: Even if you come just to the party on saturday, you can take part!
2.P.S: I organize a key-signing for the first time, so please be patient if I
did anything wrong.
--
Diese eMail sollte mit dem PGP-Schlüssel 0x2D3EE2D42B255885 digital signiert
sein. Bitte beachten Sie, das unsignierte eMails beliebig gefälscht sein
können. Achten Sie daher auf Signaturen.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
at ~07:00, the web server (wolfsbane) became unresponsive and was rebooted.
during this time http://toolserver.org was unavailable. the problem was
resolved about 10 minutes later.
the login server and the stable server were unaffected.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAknPEl8ACgkQIXd7fCuc5vI1NACfXrnwaEF0+9yCQkA6KInmWF2v
aE0AoLukCBsxuDRgRQldkXL0SfxnzBDn
=xCMm
-----END PGP SIGNATURE-----
I added some information about nice/renice to the toolserver wiki
yesterday. When sysadmins mail the list about something like this
(or about phoenix a while back) it would probably be worthwhile
for them to add documentation to the wiki. All the stuff I've
documented there has come after such announcements/reminders.
-Mike
----
Mike.lifeguard
mikelifeguard(a)fastmail.fm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
at ~15:00, an unplanned outage on the NFS server caused downtime for several
minutes, and a slightly longer outage of the s2 cluster while the database
recovered. the server was rebooted and now seems to be working fine. the
stable server was unaffected.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAknOQtQACgkQIXd7fCuc5vJ9BwCeLGjGbk4R/bzTusBMszY+Ig4u
E90An3G62ko0Mgvsoy8bdytgAyF/Fpab
=jme/
-----END PGP SIGNATURE-----
Hello all,
the load on the login-server (nightshade) is quite high at the moment. One of
the problems, that cause this, is that people don't use nice. The nice-level
tells an operation system how important a program is and how much cpu-power
it should get (to simplify it).
Normal user can set a nice-level between 0 and 19. 0 is the highest, 19 the
lowest value. The default is 0. Longrunning tasks like bots should use a low
nice-level like 10.
The usage is quite easy. Just put a "nice -n 10" before your command. An
example would be
nice -n 10 python redirect.py broken
which runs the program python (that executes the redirect-script) at
nice-level 10.
More details tell the man-page of nice (man nice).
Because I know that a few of you (of corse only new users ;)) will forget
that, I wrote a little program today. The program searchs for long-running,
high-cpu-time-using programs with nice-level 0 and set nice-level 19 by force
(then it sends an eMail to inform the user). At the moment, the programm runs
in test-mode; that means it sets only a nice-level of 1 and sends an email.
If you receive such an email and think that it is wrong, please message me.
Thanks for your attention :).
Sincerly,
DaB.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
i've deployed a new version of MySQL on rosemary (s1) and yarrow (s3) which
contains a fix for the bug where long SELECT queries on wiki databases break
replication. for people who were affected by this problem, you can re-enable
tools which were disabled because of this *after* you test that your queries no
longer cause replag.
(if you re-enable your tools without testing first, i will be annoyed.)
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAknKbpQACgkQIXd7fCuc5vInaQCghOCkrnvaV4oDnvM209bM68hM
7JYAn1JUTDaaP2Dp5TMRLWGHHFo3JK3M
=LDHZ
-----END PGP SIGNATURE-----