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
READ THE FOLLOWING INSTRUCTIONS BEFORE YOU SEND ANY MAIL:
the next Toolserver account renewal is on 1st June. if you want to keep using
your Toolserver account, you need to renew it before then, or it will expire
and you will not be able to log in.
to renew your account, do the following:
send mail to river(a)loreley.flyingparchment.org.uk
in the subject, you must write "toolserver expiration".
in the body, you must write your Toolserver username.
that is all.
do not send mail to this mailing list. do not send mail to ts-admins@. do not
do anything except follow the very clear and specific instructions presented
above. if you fail to perform this simple task correctly, you might find
yourself ignored, and your account will expire.
in one week, i will post a list of usernames who have successfully renewed
their accounts. you should check that your name is on this list; if not, your
mail may have been lost somewhere.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkoLlbsACgkQIXd7fCuc5vIZewCgl6tvId0hwiE5yFoB2wSh9oYJ
6KcAoMCnFCU3QdKMJHrKUqrmMYO0gRqU
=J1+I
-----END PGP SIGNATURE-----
Hi all
I'm happy to inform you that the new servers arrived in amsterdam. So we will
soon have: a new place for user home directories, a replacement for zedler (s2
database), a second login server, and an extra toolserver for OpenStreetMap stuff.
It will be a while until all is installed and set up. Full functionality is
expected to be available after the next regular maintenance window, july 6th.
Some parts may become available earlier, but we are out of room in our rack, so
we can't set up everything before the new rack is ready.
-- daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
there is currently a network issue between the Wikimedia switch and the
Toolserver switch at our colo, with the result that the Toolserver is
offline. the cause is unknown and there is no ETA.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkoeuoMACgkQIXd7fCuc5vLqpwCfQQqixUoVE5/TYYHNSC5VcYsZ
dWYAoLro3LVfub0Uh966iN7hIOLIHpjs
=4uuI
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
currently the stable server (willow) is running SJS Web Server. we will
shortly be converting it to Zeus Web Server. this will bring the functionality
in line with the normal Toolserver (allowing user-configurable rewrite rules
and better .htaccess support) as well as improving performance and reliability.
the new web server is running at http://stable.toolserver.org:81/. please test
that your project works correctly, and then let me know. once all projects
have been tested, we will switch the server over.
this applies to the following projects:
* geohack
* delinker
* admstats
* wmfgcbot
* acc
* poty
* nubio
if your project needs rewrite rules, which are currently configured in the web
server, you should create a rewrite script in $HOME instead. this is
documented in the ZWS manual at [1] and also on the wiki at [2].
- river.
[1] http://support.zeus.com/zws/media/docs/4.3/ZWSUserGuide.pdf
[2] https://wiki.toolserver.org/view/ZWS
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkoSlsEACgkQIXd7fCuc5vK7JQCgmpuSYtXDQf980MezAwubvxSs
uPMAoK07pJbrAkKFGi7xaszy01uCocqa
=sm6A
-----END PGP SIGNATURE-----
Hi all
Just a quick update on our latest hardware order: We are soon getting a new
database server, a new place for the /home dir and, in effect, a second login
server (willow; stable projects will be moved to a virtual box). And on top of
that, we get the playground box for the openstreetmap folks.
Anyway, the servers have been ordered, but won't arrive before May 25th. And
it's possible that there will be another week of delay, or even two. I will let
you know when I have more details.
Regards,
Daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
nightshade was rebooted at ~01:00 UTC due to an unidentified problem.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkoQC1IACgkQIXd7fCuc5vIbvACeOGUMAUXEb5r0kvPYk3bFXci6
QlMAmQHDLP4l+RKC535xIdcybNVK85/m
=krXI
-----END PGP SIGNATURE-----
I've locally installed the Perl module MediaWiki::API and successfully
made a Perl script which uses it. I've now converted the script to
Fasct CGI and placed it in my public_html with execute permission and
.fcgi extension but it fails because it can't find MediaWiki::API
I don't know if such scripts run as me and should have my path or how
to change the path, if they don't run as me does that mean I have to
get MediaWiki::API installed site-wide?
You can see the error output in this test script:
http://toolserver.org/~hippietrail/trycatch.fcgi
Andrew Dunbar (hippietrail)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
i am currently evaluating some possible changes to the Toolserver. to this
end, there is now a 'test Toolserver', vandale.toolserver.org, which is running
FreeBSD instead of Linux.
if you have a moment, please log in and test some of your tools there. if you
find something that doesn't work right, missing software, etc., file a bug in
the 'vandale' component of the Toolserver project on JIRA. i would be
particularly interested in tools that use Java or Mono (.NET).
as this is a test server, feel free to test things there; we don't mind if you
break something, since the point of the test is to identify problems. the flip
side of this is lower reliability; you might find the server is rebooted more
often, or your processes killed, etc.
this is not a permanent new server, and will be going away at some point after
testing is finished.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkoDv2cACgkQIXd7fCuc5vLOBwCgt7SX5Tj8N/aBCg4r2/+gfV+g
oqIAoKCoC5qQ7g8PMMyQf9zdCZy6eaZY
=arML
-----END PGP SIGNATURE-----