-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
This mail affects you if you have user databases on s3, s4, s6 or s7.
Other users can ignore it.
Currently, these clusters are all on the same server. During the
re-import, I will do an internal server split, i.e. each cluster will be
on a different MySQL server afterwards. We will then move user
databases to the new servers, and do the same thing on the other server.
This presents a problem when restoring user databases, because it's not
clear which cluster(s) the user intended each database to exist on.
That problem will be resolved as follows: User databases which contain a
wiki name or a cluster name in the database name will be restored to
that cluster. All other databases will be restored to s3.
If you don't agree with this algorithm, you should list your database
name under the appropriate cluster at [0] and it will be restored to the
server you request. You can list one database under multiple servers,
if you want (but please consider disk space requirements before doing
that).
- river.
[0] <https://wiki.toolserver.org/view/User:River/hyacinth_db_split>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (SunOS)
iEYEARECAAYFAk4B3HEACgkQIXd7fCuc5vJrlQCeN3lbb/GRgzihawzBWobeIttn
NAEAoLcyAN7eHNetAcpBjfH5gFEfi2BQ
=B63B
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm about to re-import several database clusters from WMF: s3, s4, s6
and s7. This will be done on the secondary server first, so users won't
be affected, except that queries on these clusters might be a bit slower
for a while.
This will resolve the following TS issues:
TS-948 creating of rue.wiki
TS-926 Cassia and hyacinth are missing the ruewiki-database
TS-1013 metawiki Database seems to be corrupt
And might resolve the following issues, although they don't provide
enough information to be sure of the cause:
TS-1024 cswikisource_p needs reimport
TS-1048 cswiktionary_p needs reimport
This reimport might take longer than usual because I will be testing a
new way of configuring database servers (which hopefully reduce database
corruption in the future).
Once this is done, I'll switch user databases to the secondary server
(during which they will be offline for a couple of hours), and then
reimport the other server.
s1, s2 and s5 will be done later.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (SunOS)
iEYEARECAAYFAk4AxugACgkQIXd7fCuc5vIELACdF8k2zkgsakxSo6x+jyrySy2o
KEwAnigGCyqS8td/t7gcQT97wjAwAOvV
=citf
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I've set up an Apache instance on wolfsbane for testing. Please have a
look at <https://wiki.toolserver.org/view/Apache_testing> and then test
your tools (note the caveat about PHP, in particular).
We're not in any rush to move off ZWS, so this is mostly just
preliminary testing. Nonetheless, it would be useful to know about any
problems now rather than later.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (SunOS)
iEYEARECAAYFAk3/ahAACgkQIXd7fCuc5vI6+gCfe58t1WD4D1NYnQlACu5miPjV
WUsAnR0jWJDB2bkXFQFl2qhnPUt3iDfX
=EFB1
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
There was an outage this morning (mostly of the web server) caused by a
fault on the fibre between hemlock and its storage array, which hosts
user-store. I have unmounted user-store until the problem is resolved,
so www is now working again.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (SunOS)
iEYEARECAAYFAk38jgYACgkQIXd7fCuc5vJyGgCgj0fRjG/YA9QHkLdBY4EVDqwu
PvYAn1Pen5ayAadqbsL9Awlbc8+sSgzk
=VtdB
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Either today or tomorrow I will be reinstalling the two web servers
(wolfsbane and ortelius). This should not have any effect on users,
and crontabs will be backed up and restored afterwards.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (SunOS)
iEYEARECAAYFAk37lngACgkQIXd7fCuc5vLK+ACgp1nGvciXLPNgbn5M3R9Zl4As
b4gAn1tJaeFegx7JDO8MGFC1WuuwmYTL
=Azzf
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On the morning (UTC) of June 6th we will performance general maintenance[0]
on all servers. Services will be affected as follows:
Service | Expected impact
--------------------------+--------------------------------------------------
Entire platform | As described in maintenance schedule[0]
FishEye | Unavailable for < 10 minutes
[0] https://wiki.toolserver.org/view/Maintenance_schedule
Start time: Monday, 6th June, 0800h UTC (or possibly earlier)
http://time.tcx.org.uk/utc/2011-06-06/00:00
End time: Monday, 6th June, 1200h UTC (estimated)
http://time.tcx.org.uk/utc/2011-06-06/12:00
Details:
We will install current operating system patches on all servers, which will
require a reboot of each system.
--
We will enable IPv6 on the NFS server, which might make /home
unavailable for a short period even if hosts are up.
--
FishEye will be upgraded to 2.5.5.
--
We will perform general software upgrades for ts-specs (/opt/ts). A list of
software to be upgraded can be found at:
<https://wiki.toolserver.org/view/Admin:Pending_maintenance_tasks>
Some software may be unavailable or function incorrectly during the upgrade
process, which we estimate will take under 30 minutes.
Note: Mono will not be upgraded due to a build failure which was not
fixed in time for the maintenance.
ts-specs (/opt/ts software) changes
- -----------------------------------
We now build software with GCC stack-smashing protection (-fstack-protector) by
default, and several packages have been rebuilt to benefit from this. This
should not cause any user-noticable changes.
Some notable changes are detailed below:
webp
- ----
The "webpconv" binary is no longer provided; instead, use cwebp and dwebp.
OpenSSL
- -------
We will install a set of root CA certificates for OpenSSL, which will enable
SSL connections (e.g. from cURL or wget) to work by default, as long as the
certificate is valid, rather than requiring the user to provide a certificate
or disable checking.
The set of installed certificates will be the current Mozilla root certificate
set (from Firefox) and the Toolserver CA certificate from
https://fingerprints.toolserver.org.
Python 3
- --------
The default version of Python 3 (/usr/bin/python3) will change to 3.2. Python
3.1 will be removed during the following maintenance.
MySQL
- -----
The MySQL client will be upgraded to 5.5.12, and will move from
/opt/ts/mysql/5.1/bin to /opt/ts/bin. If you currently call "mysql" without a
path, you do not need to change anything. If you use
"/opt/ts/mysql/5.1/bin/mysql", you should change to "/opt/ts/bin/mysql" (or
preferably remove the path and rely on $PATH). The old (5.1) client will still
be available for now.
The MySQL client library will also move to /opt/ts/lib. The old client library
will still be available, but if you have any compiled software which links
against MySQL, you should re-compile it with the client library in /opt/ts/lib.
libpng
- ------
libpng has been upgraded from 1.4 to 1.5. A 1.4 runtime library is provided
for compatibility, but if you have any software that links against libpng, you
should recompile it with 1.5. The following warning (from the libpng
documentation) applies to this upgrade:
The libpng 1.5.x series continues the evolution of the libpng API,
finally hiding the contents of the venerable and hoary png_struct and
png_info data structures inside private (i.e., non-installed) header
files. Instead of direct struct-access, applications should be using
the various png_get_xxx() and png_set_xxx() accessor functions, which
have existed for almost as long as libpng itself. (Apps that compiled
against libpng 1.4 without warnings about deprecated features should
happily compile against 1.5, too.)
GCC
- ---
GCC has been upgraded to 4.6.0. This should be backwards compatible, so there
is no need to recompile software. There are two relevant changes for C++ users:
* If you define _XOPEN_SOURCE, you need to use -D_XOPEN_SOURCE=600.
-D_XOPEN_SOURCE=500 will not work.
* GCC 4.6 will no longer accept a const object without a ctor, i.e.:
struct S { };
const S o;
The fix is to either add an empty constructor, or explicitly default-initialise
the object:
const S o = S();
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (SunOS)
iEYEARECAAYFAk3lYHIACgkQIXd7fCuc5vKCpgCfTKXkByYIjD8f7sFhSRk+kMSl
BksAoI86/sVpyhFt6YoFpYjI+OUS+OQj
=+Pc2
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Shubinator:
> On Tue, May 31, 2011 at 2:41 PM, River Tarnell
> <river.tarnell(a)wikimedia.de>wrote:
> > Start time: Monday, 6th June, 0800h UTC (or possibly earlier)
> > http://time.tcx.org.uk/utc/2011-06-06/00:00
> Your text says the maintenance will start at 08:00 UTC, but the link implies
> 00:00 UTC. Which is it?
0800h is the correct time. <http://time.tcx.org.uk/utc/2011-06-06/08:00>
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (SunOS)
iEYEARECAAYFAk3l6GQACgkQIXd7fCuc5vKkdACgj3m7NEJ7hQzq2Kj2WwVg5PTv
9KEAoJKUEZub4RqAbcYzH4CCy1fkqXWG
=jQtP
-----END PGP SIGNATURE-----