-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Toolserver users
Due to a few recent events, it seemed like we need an explicit policy for
dealing with private data. So I have added a privacy policy to the general
toolserver us. Please read:
https://wiki.toolserver.org/view/Rules
If you continue to use your toolserver account, it is assumed that you agree to
these rules.
- -- daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkpKL1sACgkQG0czJgig8U8UlACgj/erHZ2JamkM+bJzr9pcKop9
VBEAnjm8cnXylul8DNb9jQj6Yv1LNinW
=QF9k
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
the new s2 server (daphne) is online, and should have caught up with
replication later today. however, it is using a new MySQL build (version
5.1.35), which contains a critical InnoDB bug causing server crashes when
innodb_locks_unsafe_for_binlog is enabled. since we need this option to
support long queries, we won't switch servers until a patch is available.
(this is a new bug, unrelated to the previous one.) i hope this will happen
later this week.
when we switch, user databases currently on the s2 server will _not_ be moved,
and the 'sql' alias will continue to point at the old server (zedler).
therefore, if you have created tables on the old server which you need to join
to s2 databases, you will need to move these to the new server yourself. do
not move normal user databases, they should remain on 'sql' as before.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAko+R7MACgkQIXd7fCuc5vIV9gCdGvqGabLQCienTQOB3Lk5ClyP
l3EAoIZebLgBV8X6zeUIspNZNn1C8mlE
=uYxB
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
given the current low uptake of stable server usage, we have decided we cannot
afford to dedicate an entire server to it, which ends up being mostly idle.
therefore we will be migrating the stable server to a zone (virtual machine) on
hyacinth, which is also the new /home server. there should be no change in
either reliability or performance as a result.
unlike the previous move, no user intervention will be required this time. we
are currently copying the existing /users and /projects directories to the new
server. at switchover time, an incremental rsync will be done to copy any
changes since then. you can log into the new server now, using the hostname
"newstable.toolserver.org"; however, i recommend not changing any files, as
they will be overwritten when the next copy is done. if you would prefer to
edit files on the new server, let me know and i will exclude your project from
the automatic copy.
(it may take a while until you can log in, since not all .ssh directories have
been copied yet.)
i *do* recommend doing a quick sanity check of your software on the new server;
for example, that any software or libraries it needs are available and work
correctly.
downtime for the final migration will be on Monday, 6th June, in line with the
maintenance schedule for stable. we might begin the downtime slightly earlier
than usual (5AM UTC) to allow time for the file copies.
i would like to change to ZWS at the same time as the migration; if your
project has no yet confirmed that it works with ZWS, *please* consider trying
to do so before the migration, as it will make things much easier for us. this
applies to:
* wma
* wmfgcbot
if you are unable to complete the web server migration yourself, please ask for
help, either on IRC or the mailing list.
the move is accompanied by a more recent version of the TS package repository
(/opt/ts), which includes newer versions of Perl, Python and other software.
this is documented in more detail at:
<https://wiki.toolserver.org/view/Solaris_software>
for projects using third-party Python modules currently installed in
/opt/ts/lib/python2.4/lib/site-packages, these will still be available after
the move. however, we recommend changing to the Toolserver Python.
after the move is complete, the existing stable server (willow) will be
repurposed into a general login server. more details on this will follow
later.
lastly, we are still interested in more stable projects. stable server
projects can have multiple maintainers, which reduces the workload on one
maintainer, and means tools don't die when their maintainers leave.
we are currently considering disabling the unmaintained web tools of expired
user accounts, meaning these tools will stop working. stable tools will only
be disabled if *all* maintainers leave, and no new maintainer can be found.
additionally, the stable Toolserver has a well-defined maintenance schedule to
avoid downtime during peak times, and has much less unplanned downtime than the
normal Toolserver.
if you would like to move a project to stable, open a request in the TS project
in JIRA, describing the project and listing the initial maintainer(s).
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAko8YXMACgkQIXd7fCuc5vKkogCgkUtkExNsFNbczDCq9d4IbT6v
S0sAmgLHns9mqnkzDwMjkICWpVnNJsI1
=11m+
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
the two new Toolservers, hyacinth (/home server) and daphne (s2 database) have
been installed. on Monday, June 15, between 5-7AM UTC, i will move /home from
hemlock to hyacinth; this will involve some downtime as the entire filesystem
has to be copied. the total downtime should be less than 2 hours.
more information will be forthcoming later regarding the new s2 database,
and the OpenStreetMap Toolserver, which was also installed today.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAko0FGwACgkQIXd7fCuc5vIQ8QCdGjAp23Ug0Aa/X+0633PsnUYG
hT4AmQHOnuLToyrUBFTHtPCMLUnH+daQ
=Ch82
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
as usual, the following list contains users whose home directories are using
more than 1GB of disk space. please consider checking your home directory and
deleting any files you no longer need.
space is listed in kilobytes.
1044294 mzmcbride
1077935 leon
1138620 vvv
1231049 tawker
1257963 autocracy
1461143 erenrich
1520995 danny_b
1714427 purodha
1898741 fmaunier
2388170 misza13
2498892 darkdadaah
2620823 flacus
2929883 skyluke
3352872 stwalkerster
4541646 henna
5029182 drh08
5070470 tparscal
5637043 gmaxwell
6229967 kolossos
7113430 werdna
9724094 dschwen
10780027 cbm
15499050 bryan
15866279 emijrp
21621695 voj
33116919 sk
56239790 daniel
117855613 soxred93
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAko2joUACgkQIXd7fCuc5vLVRACfWRMPy/fW4sUApfCS84V0yEgW
Og4AoLJNcVkPjCy8F1RE9KWNVMG8i2G3
=2gev
-----END PGP SIGNATURE-----
Hello all,
yesterday at highnoon the master-db-servers were switched because of an huge
schema-update. Because we have only one cluster of db-servers at the moment we
couldn't do the schema-update the same way like the foundation (the foundation
stops one of their slaves, does the schema-update, waits, start it again,
stops another slave, does the schema-update and so on until all slaves are
updated, and declare one slave as new master, runs the schema-update on the
old master = no downtime) and so it took several hours until the schema-update
was done and we could switch to the new master-servers.
I deleted the view on the logging-table during the update to speed the update
up and killed several long-running queries too tonight.
The update was finish before I wake-uped, and I just finished the
masterswitch, restarted replication and recreated the logging-tables (see
maintaince-log for details). So in a few hours everything should be normal
again.
Happy Corpus Christi (it's an holiday here :)).
Sincerly,
DaB.
--
wp-blog.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
please remember that 'nice' is not a magical fix for programs that use too much
CPU. if a program uses a lot of CPU, it should be reniced; but that doesn't
mean that you can use as much CPU as you like as long as you renice it.
if you write a tool that uses 50% CPU constantly, you are using 6.25% of the
total available CPU on the Toolserver for yourself. if everyone did this, we
could only support 16 users before running out of CPU. we have a lot more than
16 users, so please be considerate, and monitor your CPU use.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkow9O0ACgkQIXd7fCuc5vIgFQCgjrrJVnKGFEwOV+aPNXkXPzJI
KUEAoI7GF7FixCyGq8cQhXOnTZFldeBO
=tJcy
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
during today new Toolserver hardware will be installed. there is a possibility
that this will cause some downtime.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkoqM8oACgkQIXd7fCuc5vLVvgCeMghf+fjTTWTVQJ9Sb+9/S3N8
NtQAnAvp/KkK0ud5hMW//HTVPGzUqaZU
=jdf4
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
a new Python, version 2.6.2, is now available on stable. this is *not* the
default Python; it is installed in /opt/ts/python/2.6, and to use it, you
should write something like this at the top of your script:
#! /opt/ts/python/2.6/bin/python
all previously-installed modules are also available with the new Python. the
problem with $PYTHONPATH is also fixed, so there is no longer any need to set
that to use any modules.
i recommend all projects which use Python change to 2.6, as any new module
requests will only be built for this version.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkon8BAACgkQIXd7fCuc5vLO8wCfcYznII2Wouz77b9VNxjRm+Wr
JJEAnRHnnQxaE9iHKKhcHSB/upVlXjwh
=OpZb
-----END PGP SIGNATURE-----