Just a little reminder:
Your toolserver accounts will expire on January 6th, 2014. You can renew
it with acctrenew as usual.
If you had an expired account and you want to come back and collect your
data: Your account has been reactivated until that date. You can login
to nightshade and use the script "byebye" to collect your stuff. It will
create a new directory inside your home directory called FarewellBundle.
This directory contains tarballs of almost everything you had on the
toolserver. The only thing you have to take care of separately is your
stuff in /mnt/user-store. Please download the data you don't need on the
toolserver any longer!
If you don't need your account any longer you can delete it using the
script "burnbridges". It will delete everything but your
~/public_html/.htaccess files in case you have a redirect to Tool Labs.
For us, it would be very helpful if you deleted you data yourselves.
If you find some time before January 6th, please consider migrating your
tools to Tool Labs , as the toolserver will be discontinued in mid
2014. If you hit barriers that prevent you from migrating, please create
bugs in Bugzilla ! We can meet in an IRC office hour in January to
discuss them. The office hour will be announced separately at the
beginning of January.
 Tool Labs Help:
Internes IT-Management und Projektmanagement Toolserver
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt
für Körperschaften I Berlin, Steuernummer 27/681/51985.
I'm not sure if this has been discussed anywhere but, what will happen with
the Toolserver domain?
I'm not sure if ALL servers are going to be removed or a basic Apache is
going to run in the domain the next years.
Perhaps we can mantain a basic site, with the wiki, and a little museum?
most of dbreps's jobs have been waiting for more than a
| scheduling info: queue instance "medium-lx(a)mayapple.toolserver.org" dropped because it is temporarily not available
| queue instance "longrun2-sol(a)hawthorn.toolserver.org" dropped because it is disabled
| queue instance "longrun2-sol(a)clematis.toolserver.org" dropped because it is disabled
| queue instance "longrun3-sol(a)willow.toolserver.org" dropped because it is disabled
| queue instance "short-sol(a)willow.toolserver.org" dropped because it is full
| (-l arch=linux-x64,h_rt=12300,mem_free=2070M,sql-s1-rr=1,sqlprocs-s1=1,virtual_free=2070M) cannot run globally because it offers only gc:sql-s1-rr=0.000000
Does that mean that the resource sql-s1-rr is depleted? Are
the database servers really that congested?
I see that /sge/scripts/sensor/sqlslots2.pl was changed on
October 17th. Could the calculation of the DB slots be
wrong, or would changes in that file not affect the resource
Today, I hacked together a JIRA migration tool. If you want your bugs
migrated please do the following two things:
1) Under Administration, <your project>, People, add 'Bugzilla Bug Exporter
(valhallasw)' to 'Administrators' and click 'Update'. Otherwise, the bot
cannot close the bug.
2) File a bug in bugzilla using the following link:
3) Your bugs will be migrated for you! See
https://bugzilla.wikimedia.org/58820 for an example of what the converted
bug looks like.
I like to wish you a Merry Christmas. I hope you get all presents you
wrote Santa for, eat a nice Christmash-dish and can celebrate with your
family and friends :-). Take a few days off and relax a bit.
If you celebrate Xmas at the 25th instead of the 24th: Repack this eMail
and open it tomorrow again ;-)
I am finishing up the move and want to redirect all incoming links (which
use the exact same structure) from the toolserver to labs. Ive tried
several things from IRC, but am getting nowhere. does anyone have an
existing .htaccess that does this?
I am in the process of migrating to labs and the command sql performs
differently between the two platforms, Can I get the source for the
toolserver version of it so that we can make the labs version work the same.
In order to check my scripts activity I generate my log files in my
public_html folder. Unfortunatly I can't read these files (I delete them
frequently, so they are recreated).
Is there any option to make all the new files in public_html viewable ?
Currently I have a "Forbidden" error but I can see the folder content :
considering your feedback regarding the shutdown procedure, nosy and I
improved upon the process a bit. The 'burnbridges' script will not
that has any redirect to Labs in it. And even though your account will
be expired by calling burnbridges, those redirects will still continue