River Tarnell | 1 Feb 18:28 2010
Picon

Unplanned downtime, 2009-02-01

Hi,

There was some unplanned downtime on the HA cluster today causing an outage
of the platform.  The downtime was caused by an upgrade of the software on
one node.  We will investigate the cause of the failure before upgrading the
other node.

Due to the nature of the NFS failure, you may need to restart any background
or screened programs you had running.

      - river.
Attachment (smime.p7s): application/pkcs7-signature, 5710 bytes
Hi,

There was some unplanned downtime on the HA cluster today causing an outage
of the platform.  The downtime was caused by an upgrade of the software on
one node.  We will investigate the cause of the failure before upgrading the
other node.

Due to the nature of the NFS failure, you may need to restart any background
or screened programs you had running.

      - river.
DaB. | 3 Feb 14:45 2010

Re: Interwiki-Bots

Hello again,

after this discussion seems to be finish for first, I created [1] to push and 
coordinate the process from now.

Sincerly,
DaB.

[1] https://jira.toolserver.org/browse/TS-494

-- 
wp-blog.de
Hello again,

after this discussion seems to be finish for first, I created [1] to push and 
coordinate the process from now.

Sincerly,
DaB.

[1] https://jira.toolserver.org/browse/TS-494

--

-- 
wp-blog.de
River Tarnell | 3 Feb 15:07 2010
Picon

DNS aliases for fast database servers

Hi,

There are now DNS aliases for the fast database servers, under
fastdb.toolserver.org.  For example, if you currently connect to
enwiki-p.db.toolserver.org, connect to enwiki-p.fastdb.toolserver.org
instead to use the fast server.

(For now only enwiki has a fast server, but we will be adding them for other 
clusters in the next few weeks.)

        - river.
Attachment (smime.p7s): application/pkcs7-signature, 5710 bytes
Hi,

There are now DNS aliases for the fast database servers, under
fastdb.toolserver.org.  For example, if you currently connect to
enwiki-p.db.toolserver.org, connect to enwiki-p.fastdb.toolserver.org
instead to use the fast server.

(For now only enwiki has a fast server, but we will be adding them for other 
clusters in the next few weeks.)

        - river.
River Tarnell | 4 Feb 13:46 2010
Picon

Changes to expired accounts web hosting

Hi,

In the past, when an account was expired, it was still possible to access 
its public_html.  This has now changed.  Any HTTP requests to an expired 
account will return an error page indicating that the account has expired.

The files in public_html are not deleted, and will become accessible again 
if the account is ever un-expired.

   - river.
Attachment (smime.p7s): application/pkcs7-signature, 5710 bytes
Hi,

In the past, when an account was expired, it was still possible to access 
its public_html.  This has now changed.  Any HTTP requests to an expired 
account will return an error page indicating that the account has expired.

The files in public_html are not deleted, and will become accessible again 
if the account is ever un-expired.

   - river.
Eusebius | 4 Feb 14:30 2010
Picon

Re: Changes to expired accounts web hosting

Hi,

River Tarnell a écrit :
> In the past, when an account was expired, it was still possible to access 
> its public_html.  This has now changed.  Any HTTP requests to an expired 
> account will return an error page indicating that the account has expired.

The "gallery" tool integrated into WM Commons is now unavailable, I
assume it is a direct consequence of this change.
<http://toolserver.org/~daniel/WikiSense/Gallery.php?wikifam=commons.wikimedia.org&img_user_text=Eusebius>

Is there a way to make it work again, by reactivating the host account
or moving the tool on someone else's account (and modifying the relevant
config on Commons)?
I don't see it as a vital tool, but I'm sure many users (and admins)
find it useful.

Regards,
Eusebius

Hi,

River Tarnell a écrit :
> In the past, when an account was expired, it was still possible to access 
> its public_html.  This has now changed.  Any HTTP requests to an expired 
> account will return an error page indicating that the account has expired.

The "gallery" tool integrated into WM Commons is now unavailable, I
(Continue reading)

River Tarnell | 4 Feb 14:35 2010
Picon

Re: Changes to expired accounts web hosting

Eusebius:
> The "gallery" tool integrated into WM Commons is now unavailable, I
> assume it is a direct consequence of this change.

Yes, but unintentional.  This should be fixed now.

     - river.
Attachment (smime.p7s): application/pkcs7-signature, 5710 bytes
Eusebius:
> The "gallery" tool integrated into WM Commons is now unavailable, I
> assume it is a direct consequence of this change.

Yes, but unintentional.  This should be fixed now.

     - river.
Nikola Smolenski | 4 Feb 14:45 2010

Re: Changes to expired accounts web hosting

River Tarnell wrote:
> Eusebius:
>> The "gallery" tool integrated into WM Commons is now unavailable, I
>> assume it is a direct consequence of this change.
> 
> Yes, but unintentional.  This should be fixed now.

CheckUsage, at least, doesn't work. 
http://toolserver.org/~daniel/WikiSense/CheckUsage.php

Mike.lifeguard | 4 Feb 17:19 2010
Picon

Re: Changes to expired accounts web hosting


On 10-02-04 08:46 AM, River Tarnell wrote:
> In the past, when an account was expired, it was still possible to access 
> its public_html.  This has now changed.  Any HTTP requests to an expired 
> account will return an error page indicating that the account has expired.
> 
> The files in public_html are not deleted, and will become accessible again 
> if the account is ever un-expired.

In the past, when people disappeared, their tools would (maybe) keep
working. Now that we *know* they will stop working once the account is
expired, do we know how requests for sourcecode for a tool will be
handled, in case someone wants to revive it?

And this is another reason multi-maintainer accounts are superior! Use them!

-Mike
River Tarnell | 4 Feb 17:24 2010
Picon

Re: Changes to expired accounts web hosting

Mike.lifeguard:
> In the past, when people disappeared, their tools would (maybe) keep
> working. Now that we *know* they will stop working once the account is
> expired, do we know how requests for sourcecode for a tool will be
> handled, in case someone wants to revive it?

Currently we don't have a good policy for this.  Many (most?) tools have no 
copyright header or license, which makes it difficult to distribute them.  
There have been some proposals in the past, like assuming tools without 
licenses will use a particular license, but I'm not too fond of that.

The solution I like best is to require that all tools be MMTs, but I imagine 
some users would object to that ;-)

This is probably something that WM-DE needs to create a policy for.

     - river.
Attachment (smime.p7s): application/pkcs7-signature, 5710 bytes
Mike.lifeguard:
> In the past, when people disappeared, their tools would (maybe) keep
> working. Now that we *know* they will stop working once the account is
> expired, do we know how requests for sourcecode for a tool will be
> handled, in case someone wants to revive it?

Currently we don't have a good policy for this.  Many (most?) tools have no 
copyright header or license, which makes it difficult to distribute them.  
There have been some proposals in the past, like assuming tools without 
licenses will use a particular license, but I'm not too fond of that.
(Continue reading)

Daniel Schwen | 4 Feb 18:14 2010
Picon

Re: Changes to expired accounts web hosting

One solution would be to make free licensing a prerequisite to
obtaining a toolserver account.
And then make it mandatory to make all source-code world readable
(minus config files containing passwords of course).

> Currently we don't have a good policy for this.  Many (most?) tools have no
> copyright header or license, which makes it difficult to distribute them.


Gmane