-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Perl on the Solaris systems will shortly be upgraded from 5.12.1 to 5.12.2.
This should have no impact on users.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkySPGEACgkQIXd7fCuc5vLuPQCfawQtGLeDnCqTHC/3kdU/gPCF
1+MAmwdVvKK4tpYdimOeye8iivjvDEVM
=5Hr4
-----END PGP SIGNATURE-----
okay, so installing MediaWiki::API is supposed to be done locally. I'm
following the instructions:
https://wiki.toolserver.org/view/Perl
The problem is that there's no local Config.pm at the given location. In
other words, /etc/perl/CPAN/Config.pm in step 3 does not exist. That
makes it hard to follow step 4 and beyond.
I'm on willow.
And about "no perl experts": I've only spent 10 years writing OO perl,
I've just always used root access or a CM config that handles packages.
I recently bought Randal Schwartz a drink- OTOH, Ward Cunningham then
bought me a drink, so I can't complain.
-ted
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Some time ago we changed the default Perl on Solaris login servers to 5.12.
Since then, no one has reported any problems with 5.12; we will therefore be
removing Perl 5.10 later this week (that is, /usr/bin/perl5.10 and
/opt/ts/perl/5.10/bin/perl).
Applications that use /usr/bin/perl will not require any changes because of
this.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkyONE8ACgkQIXd7fCuc5vKT0wCfab2WDZbRcGTSE5RidytNxbxJ
IEsAni3jzrsn9kdCJ+kWukv49zXAlbvB
=iEv0
-----END PGP SIGNATURE-----
Hello all,
I was noticed by a user today that a few web-tools on the toolserver (at least
3) uses google analytics and violates our rules with that. No user is allowed
to "publish connection data, especially IP addresses, of other people " [1];
"publish" means also "give data away to (other) companies or webpages".
I will message these users separately, so that they can remove the problem
themself soon. If you (because of nescience or ignorance) include a service
like google analytics in your tools too, please remove it too very soon.
Sincerly and good night,
DaB.
[1] https://wiki.toolserver.org/view/Rules#Privacy_Policy - point 2
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
After some internal discussion and previous consultation with users, we have
decided to standardise on Solaris for the login and web servers. We will
therefore be converting nightshade from Linux to Solaris at some point in the
future.
There is no fixed time frame for this at moment, but it won't happen sooner
than a month from now, and we won't do anything until we are satisfied that all
tools (and users) are ready for the migration.
To start with, we want to identify and fix any issues which prevent users
from moving their tools to Solaris. This will mainly include:
* Software which needs to be installed or updated
* Behaviour differences between Linux and Solaris where the Linux behaviour is
more correct or preferable.
Please take a moment to test your tools on willow, the existing Solaris login
server. If you find any issues, please open a ticket in JIRA, and include
[solaris] in the subject line so we can easily identify them.
Software on Solaris is often newer than the software on the Linux login
server. This isn't a problem that can be fixed (since the software will
eventually be updated anyway), but during the migration period, we can install
more recent versions on Linux as well to allow interoperability.
The easiest way for users to migrate is probably to ensure your tools work on
both systems; you can then continue to run them on Linux for now (if you want),
and there will be no work required once the conversion is done.
Some differences between the two operating systems are documented on the wiki
at <https://wiki.toolserver.org/view/Solaris>.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkyOOnsACgkQIXd7fCuc5vLvAwCgj5P6LFyP0aAxod1NrUfYncsT
P1IAoIjzptaK7pQbDncna5rlIshVGSDE
=r4o1
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
(I have the impression that our maintenance notices are not always very clear,
since people are sometimes surprised when we carry out previously-announced
maintenance. So, here's a new and hopefully improved notification format.)
This is a maintenance notification for tonight (Saturday 11th) UTC. The
following services will be affected:
Service | Expected impact
- --------------------------------+-----------------------------------
s1 cluster | User databases unavailable for < 10 minutes
s2 cluster | Entire cluster unavailable for < 10 minutes
s3 cluster | User databases unavailable for < 10 minutes
s4 cluster | User databases unavailable for < 10 minutes
s5 cluster | Entire cluster unavailable for < 10 minutes
s6 cluster | User databases unavailable for < 10 minutes
user databases (sql) | Unavailable for < 10 minutes
user-store filesystem | Unavailable for < 20 minutes
NFS, LDAP, misc services: | None expected, but at risk during maintenance.
SVN, phpMyAdmin, SGE, tsbot, |
mail forwarding, DNS, |
sql-toolserver database |
All other services | No impact
Start time: Sunday, 12th September, 12AM UTC
End time: Sunday, 12th September, 3AM UTC
Details:
Tonight we will complete the upgrade to Solaris 10 Update 9 on the remaining
servers. This requires under 10 minutes downtime while each system reboots.
Since we will be upgrading the primary server in each cluster, which holds user
databases, these will be unavailable during the reboot. Access to replicated
databases will not be interrupted, since queries will be directed to the
alternative server while one is rebooted.
The exception is s2/s5 and sql (user databases), which currently have only one
server. They will therefore be unavailable during the reboot.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkyLn7IACgkQIXd7fCuc5vLGIQCeOzuSSxfnVcwKaPz4JU4I15WL
864Ani/mUI0ed+8nfnocP3rVep+P64X6
=GEkv
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We have replaced sendmail on the Solaris login servers with the Postfix MTA.
This should not make any difference to users, except that it should fix the
problem with cron mails not being delivered.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkyLxVsACgkQIXd7fCuc5vKBewCeLfsdZ7frvaC/SI4LM03XWCsC
qaUAoITvPv6ULwCViT1jfDrYTDYEElMs
=KyjE
-----END PGP SIGNATURE-----
I am not getting cron emails, and think that my cron tasks are not
working. They are run on willow, and I think that this is related to the
upgrade done.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Later tonight we will upgrade the OS on hyacinth (s3/s4/s6 server). This will
involve ~30 minutes downtime, but should have no impact on users.
We will also upgrade the OS on willow at the same time, which should require
<10 minutes downtime. If there are no problems with that upgrade, we will also
upgrade the web servers (wolfsbane & ortelius); but the cluster software makes
this upgrade more intricate, so it may not be completed tonight. That will
have no impact on users, since web requests will be served by the other server
while one is being upgraded.
This maintenance will take place around 12AM UTC on Saturday (11th).
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkyKUDkACgkQIXd7fCuc5vIJ3QCfWbdwQ+I/pzof66ffUZwklkwa
SUYAoLyp7quTM0LCLlTw9vqIQLyhwTnI
=/o9r
-----END PGP SIGNATURE-----