-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
the Toolserver is currently offline due to an issue with the NFS server.
we are working on the issue and have a ticket open with Sun, but at this
point there is no ETA.
if it looks like the issue will take some time to resolve, we will
restore the last /home backup onto another server and use that.
however, that means losing about 12 hours worth of changes, so we will
try to avoid it if possible.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkqSsmMACgkQIXd7fCuc5vKobACfcRyaQMlECY0tIXfTvXTH7IeH
NPQAn2UcW83zd3hTnk8wRU08cvWgD9Ni
=8yRk
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
i have shut down MySQL on s1 (rosemary) for hardware maintenance later
today. this will also affect stable once the maintenance starts.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkqO6UIACgkQIXd7fCuc5vK9XwCdEvzrIQE/oxAt/ankGGUlJImC
TFwAn1zbuwQTYeqx7F23UeusEcUH0BFG
=e4IP
-----END PGP SIGNATURE-----
Hello all,
hyacinth (NFS-server and stable) was rebooted because of problems with the
network. The missing nfs forced nearly tools to stop/halt. The outtage was
nearly 1 hour.
Sincerly,
DaB.
--
wp-blog.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
after the web server change on Wednesday, we noticed the following
behaviour of regexp matching in rewrite scripts: when using a construct
like "(a|b|)", the regexp will *not* match the empty string. as a
workaround, you can write "(a|b)?". if you do not use this construct
in your rewrite.script, this does not affect you.
we have raised this issue with Zeus and are waiting for a resolution.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkqMZtEACgkQIXd7fCuc5vJSBwCfUqPM5UnwGu2bkaE7QkMejUzq
ljQAnR2Z9uPjlvi54LJd6D5Fp9qsim6J
=ug1G
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
following the implementation of the Solaris login server (willow), we are
planning to move the web server, wolfsbane, to this platform. compared to the
previous change on the web server (from Apache to ZWS), we don't expect this to
require as much effort from users. for example, there is no need to change
your htaccess or rewrite rules, because we will be using the same web server
software.
for most tools (e.g. simple CGI or PHP scripts), there will be no need to
change anything. in order of likelihood, the most common problems will be:
* missing modules (for PHP/Perl/Python)
* missing libraries (for C/C++)
* different versions (e.g. PHP 5.3 vs 5.2, Python 2.6 vs 2.5)
* OS differences
if you find missing modules or libraries, please file a request on JIRA to have
these installed. for version differences, normally no changes will be
required; if any are required, they will be documented in the release notes for
the language in question, and should be easy to do. in extreme cases (where
converting to the new version would be very difficult), we may be able to
install old versions of the affected software.
there are unlikely to be many people affected by OS differences; this would
only happen if your tool calls external programs, which is uncommon. if you
encounter a problem of this sort and can't solve it yourself, you can ask for
help on IRC or the mailing list. there are some notes about Linux->Solaris
migration on the TS wiki at <https://wiki.toolserver.org/view/Using_Solaris>.
there will be a one month test / migration period, during which you can test
the web server on willow. to do this, replace "toolserver.org" in your tool's
URL with "willow.toolserver.org", for example:
http://willow.toolserver.org/~jsmith/mytool.php
this will last until Wednesday, 19 August, at which point wolfsbane will be
converted.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkpolUwACgkQIXd7fCuc5vL2EgCgmG45stK/gAuTQS48mSAumkPL
svkAnRV66vax/6j+Mrq5E/1/YsF4ESoq
=lwH6
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
due to some confusion during Wikimedia's move of commons to a new
cluster, the database was dropped on the Toolserver and is not
available. we will do a reimport at some point to bring it back.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkqIgcYACgkQIXd7fCuc5vJN8wCfUPsDKqr+yDOxCjDskaJPsYFL
eacAoKbKdoELJ/95jsXUtMpTNT7QBnZ/
=ZOlD
-----END PGP SIGNATURE-----
Hello all,
at the moment it is difficult to inform our toolusers (people that use our
tools) about planed maintainces, downtimes and other important things.
So I had the idea today that a kind of global sitenotice (like the one in the
wikimedia-projects) would be nice and a easy solution for that. The easiest
way to implement it is IMHO a simple textfile, that toolauthors
may/can/should/whatever insert in their tools. I created such a file, it can
be found at /var/www/sitenotice on wolfsbane and via
http://toolserver.org/sitenotice. For normal the file would be empty or
contains only a empty div-container. If the roots know about a planed downtime
or an important change, they would insert a short text in the file and our
toolusers would be informed.
The setup is differend to status.toolserver.org, because status lists only the
current status, not a futuraly status.
Please comment at the toolserver-mailinglist and tell me/us if you would
implement the sitenotice in your tools.
Sincerly,
DaB.
--
wp-blog.de
Hello all,
to make sure that CVE-2009-2692 is fixed after the kernel-update, I rebooted
all linux-servers (that's nightshade, wolfsbane and cassini) tonight.
The downtime was fewer then 5 minutes.
Sincerly,
DaB.
--
wp-blog.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
people running cron jobs or otherwise receiving system mail on willow
will not have received that mail in the last few days, as it was being
queued instead of sent. this has now been fixed, so you may see some
old mail arriving.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkp+gW8ACgkQIXd7fCuc5vKdRwCgqPpJ2VPsihkQfqoDuvuEYnT2
NoEAn23buSxsRd1cqeXoswqGsmHrhJV9
=etIX
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
the s1 server (rosemary) has a faulty motherboard which is causing
system crashes. we will replace the part next week; until then, access
to s1 will be intermittently offline.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkp+CUkACgkQIXd7fCuc5vJPoACbB3A2wdatbZvrdwSUQ1bcm3wH
eT4AnA0mKf1cghr/a6FPRoIvGmOIqYmb
=oi+H
-----END PGP SIGNATURE-----