Hello,
we have an issue with Jira authentication since 25th August.
It seems the syncronisation with the crowd server is broken but I dont know why and filed a bug at Atlassian.
Cheers
Marlen
Hello all,
today I discovered (thanks to the mailing-list) that a few users have run
several bot-instances in parallel on willow. I'm sure that these people did it
by mistake, but it is annoying nevertheless and it is easy to fix: Use SGE.
The problem is that I wrote several of eMails about "use SGE!" already and
somehow it did not work as good as it should (if you converted you stuff
already: thank you and you can stop to read here ;-)). I understand that we
all are busy with our lives and Wikipedia and that we all love to "do it
right…later", but as you know that resources of the toolserver are limited. So
I hereby declare the following new rule:
All bots have to run by SGE. A bot is every program or script that makes
changes at a Wikimedia project. It does not matter if the bot runs
periodically or continuous. The only exclusions are a.) interactive bots, b.)
bots that can't run by SGE yet and c.) if you start a bot by hand for testing
(no screen, no cron, no while).
The rule will become active at Sunday, 10. February 2013. Exception b is
almost NEVER the case, if it runs on a shell it is VERY likely that it can run
by SGE.
Some time ago I wrote a simple SGE-how-to at [1]. Maybe you all can take a
look and correct things and make things more clear. In very most cases the
using of SGE IS easy.
Sincerely,
DaB.
[1] https://wiki.toolserver.org/view/SGE_for_beginners
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
We've been receiving messages from this domain at unblock(a)toolserver.org
and they appear to be related to this:
<http://www.reddit.com/r/WTF/comments/l44r1/i_just_got_this_email_at_work_i_…>.
Viral advertising for some film. In reality, it's a message with a
crapload of images attached serving no purpose for us.
Can we just block this whole domain from sending mail to toolserver
accounts? It's a nuisance, and the messages are quite large.
--
Chris Howie
http://www.chrishowie.comhttp://en.wikipedia.org/wiki/User:Crazycomputers
If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/
PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5
------------------------------------------------------------------------
IMPORTANT INFORMATION/DISCLAIMER
This document should be read only by those persons to whom it is
addressed. If you have received this message it was obviously addressed
to you and therefore you can read it.
Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.
This overrides any disclaimer or statement of confidentiality that may
be included on your message.
Hello all,
for historical reasons s2 and s5 are together on one host (cassia). Because
cassia is quite overloaded, the sharing will end soon and I will move s2 away.
For this I need your help because s2 and s5 share also the user-databases and
there is not hint which user-database is needed where.
So if you use user-databases for joining with s2 (two!) please add the name of
the user-database to [1] until
Friday, 8. February 18:00 UTC.
It will take only a few minutes to add your user-databases there, so please do
it. If you do not your user-databases there your tools will break after the
split, but of course that can be fixed later.
Sincerely,
DaB.
[1] https://wiki.toolserver.org/view/User:Dab/s2-userdatabaes
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hi,
for those of you not having seen TS-1553, mail forwarding
seems to have stopped working. So if you haven't received
the usual job reports that you were expecting, you might
want to login to all servers and check if there is mail for
you. You can query all servers by:
| for SERVER in clematis hawthorn nightshade ortelius willow wolfsbane yarrow; do
| ssh $USER(a)$SERVER.toolserver.org ls -l /var/mail/$USER
| done
replacing $USER with your username.
Tim
Hello all,
I successfully converted the commons-binary-dump from the WMF to the
traditional dump-format today. I will now re-import commons to everywhere we
have it already, and I will start with cassia (s2+s5)
Tomorrow, Friday, after 13:00 UTC.
During the re-import the commons-copy of cassia will be inaccessible. The
import will take some hours (depending on the load of the server) and to be
safe I say hereby that commons on cassia will be away for 24h.
Another thing: My personal eMail-Server will receive an hardware-update
starting Friday 17:00 UTC: So it could be hard to reach me by mail for a few
hours. In urgent cases, try to reach Nosy.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
The Wikimedia Foundation has an opening for a contractor to work on
Wikimedia Labs's "Tools Labs" environment. The initial contract is for
6 months at full time (40 hours per week), with optional renegotiation
of the contract at the end of that term.
Tools Lab Operations Engineer (Contractor)
http://hire.jobvite.com/Jobvite/Job.aspx?j=o7y3Wfwo&c=qSa9VfwQ
Wikimedia is looking for a contractor whose primary focus will be to
assist the community developers to migrate their tools to this new Labs
infrastructure, especially those residing in Toolserver today. In
addition, this person will:
Support enhancement and perform operational duties of the Labs
Virtualization Project using OpenStack and LAMP-stack technology. Duties
include developing, deploying and supporting tools to provision and
manage large networks of virtual machines, creating a redundant and
scalable cloud computing platform
Set up monitoring systems
Provide system and database administration duties for the Labs
environment
Candidates do not have to live in the USA; remote candidates are
welcome. You must be willing to travel occasionally for international
meetings, as well as to perform your duties. Two WMF people are already
working on the Wikimedia Labs infrastructure (Ryan Lane and Andrew
Bogott); this contractor will work closely with them, DaB. and Nosy,
Toolserver users, and the Engineering Community Team.
Please see the job description for more details on what the contractor
will do and what the required qualifications are. And please spread the
word about this opening (and about our other openings at
https://wikimediafoundation.org/wiki/Job_openings ) to people you know;
we'd love to fill this soon. Thank you!
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hi,
ssh'ing to yarrow gives:
| [tim@passepartout ~]$ ssh yarrow.toolserver.org
| @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
| @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
| @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
| The RSA host key for yarrow.toolserver.org has changed,
| and the key for the corresponding IP address 91.198.174.216
| is unknown. This could either mean that
| DNS SPOOFING is happening or the IP address for the host
| and its host key have changed at the same time.
| @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
| @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
| @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
| IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
| Someone could be eavesdropping on you right now (man-in-the-middle attack)!
| It is also possible that a host key has just been changed.
| The fingerprint for the RSA key sent by the remote host is
| 59:3d:de:62:07:44:f2:f3:b0:e1:6d:a8:d2:7e:7e:af.
| Please contact your system administrator.
| Add correct host key in /home/tim/.ssh/known_hosts2 to get rid of this message.
| Offending DSA key in /home/tim/.ssh/known_hosts2:1
| RSA host key for yarrow.toolserver.org has changed and you have requested strict checking.
| This is the Wikimedia Toolserver.
| [...]
Was this intentional?
Tim