I've a Toolserver account - I remember registration procedure just like a
terrible nightmare and I survived only thanks to lots of luck.
Now, server refuses connection. I use Pageant, usually login is very simple
- I load my key, then I open Putty, I post my username and all runs. But
now it doesn't run any more. How can I get some help?
Alex brollo
My cronie task list looks like this:
PATH=/opt/ts/gnu/bin:/sge/GE/bin/sol-amd64:/usr/bin:/bin
5 1 * * * qcronsub -N 'wymowa.py' -b y -l h_rt=4:00:00 -l virtual_free=50M
/usr/bin/env PYTHONPATH=$HOME/wikt/pywikipedia /usr/bin/python2
$HOME/wikt/moje/wymowa.py >/dev/null
6 2 * * * qcronsub -N 'frequency.py' -b y -l h_rt=0:30:00 -l
virtual_free=20M /usr/bin/env PYTHONPATH=$HOME/wikt/pywikipedia
/usr/bin/python2 $HOME/wikt/moje/frequency.py >/dev/null
...and so on
It stopped working around 2-3 weeks ago. Now I get an error message:
/usr/bin/env: No such file or directory
What should I change in these lines in order for the scripts to work again?
alkamid
(In case the message with the pretty picture doesn't get through in time)
Due to the power line reaching my home office having been ripped out, I'm without power for an indeterminate time. Accordingly, the maintenance window planned for 18:00 UTC tonight is cancelled, and will be rescheduled once I have a status update from the power company telling me when they'll have replaced the poles and cabling.
-- Marc
Sent from my iPad
Just wondering what the status of exposing all wikidata tables on the
toolserver is.
Currently, there are a few wb_* tables with item labels, descriptions,
aliases, and language links.
But the tables (whatever they are called) containing item-to-item
connections appear to be missing. Maybe because they were added later?
Magnus
<optimism>What's the worst that could happen?</optimism>
The big news this week is the replacement of Gluster as the provider of
shared storage by NFS for the tools project.
In doing so, we're going to gain a great deal of extra stability, and
quite a bit of performance. In addition, there is now an automatic
timetravel snapshot feature allowing users to look at the filesystem as
it was during snapshots spanning: once an hour for the past three hours,
once a day for the past three days, and two weekly snapshots (on Sundays).
That said, NFS is robust but does not scale as much as we would like in
the longer term; we will keep investigating clustered storage solutions
for the future, with an eye to returning to it once we find a solution
that is (a) no less robust than NFS, (b) no less reliable than the
current storage and (c) at least as good from a performance standpoint.
Technically, this storage is already available to all projects but the
configuration necessary to /replace/ gluster with it would generally
require a per-project outage. (Involving copying the contents of the
previous store to the new one, and substituting one mount point for
another -- a process which running processes can generally not cope with).
In practice, the tools project will be the first transition "victim",
with an outage tomorrow to make the switchover. Sadly, the process is
necessarily disruptive and currently running processes will be affected
(see below for details).
As secondary news, thanks to the unwavering efforts of Asher, the
database replication is now at a point where we are actually selecting
what, exactly, is going to be replicated. Things are progressing there
at a fair clip and we're still sticking pretty close to schedule. More
news on that topic next week.
=== Planned outage ===
When: Tuesday April 23 at 18:00 UTC
Duration: 1 hour
Impact:
* Jobs running on the grid engine will be stopped, and execution nodes
will be temporarily disabled;
* The login server will be restarted during the window, ending active
sessions;
* The web service will be unavailable during the maintenance window; and
* Running processes not scheduled through the grid engine will be killed.
Recovery plan:
In case of unplanned failure during the maintenance window,
configuration will be rolled back to the current version (that is, the
gluster-based project storage will remain in place) and a new
window will be planned after postmortem.
-- Marc
Hi all!
Let me shortly summarize the comments on the roadmap's discussion pages:
There were no comments about the actual roadmap but feedback
concerning these two topics:
1) What's going to migrate and what isn't?
* Until now, it's not clear which tools will not be able to move. Or
which maintainers might decide not to move and why. People are curious
about this but tool maintainers would have to talk about it for us to
find out.
2) Bad Tool Labs experience:
* How fast is the account creation process right now? A tool
maintainer reported that he spontaneously had some time to think about
migrating. He requested an account but then waited for two weeks to
get it. For people working on tools in their spare time this is too
long.
* Documentation has to be improved! Good overviews are needed as well
as a detailed documentation of everything relevant to working in Tool
Labs.
* An example: You get strange messages and can't find any information
on them, e.g. this one: "Your user rights were changed by Andrew
Bogott. You are now a member of this group: shell. Learn more". By
clicking onto it, you get a list of permissions: "loginviashell".
There is a red link pointing to "Wikitech:Shell". The user is
confused.
* Who is responsible for documentation? (I'm not sure I answered this
correctly: It's not clear to me how much the Tool Labs docs overlap
with general Labs docs and who is responsible for that part. Or is the
Tool Labs documentation isolated from the rest???)
Cheers, Silke
2013/4/19 Silke Meyer <silke.meyer(a)wikimedia.de>:
> Hi all!
>
> As you know Wikimedia Deutschland has the mandate to create a roadmap
> for the availability of features on Wikimedia Labs / Tool Labs that are
> currently available on the Toolserver until the next membership assembly
> (May 25th). I have worked on this for the last weeks and now published a
> draft. I would like to get your feedback on this draft to make sure it
> is sound and nothing vital is missing. The current version is not final
> but hopefully very close to what will be presented at the membership
> assembly next month.
>
> The plan has been drafted in close cooperation with the responsible
> people at the Wikimedia Foundation. It still needs a final ok from them
> though.
>
> You can find the drafts at:
>
> English version: http://www.mediawiki.org/wiki/Tool_Labs/Roadmap_en
>
> German version: http://www.mediawiki.org/wiki/Tool_Labs/Roadmap_de
>
> To not spread out discussions too far please use the discussion pages of
> the above two pages for comments, suggestions and corrections.
>
> Cheers, Silke
>
> --
> Silke Meyer
> Internes IT-Management und Projektmanagement Toolserver
>
> Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
> Tel. (030) 219 158 260
>
> http://wikimedia.de
>
> 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.
--
Silke Meyer
Internes IT-Management und Projektmanagement Toolserver
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
http://wikimedia.de
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 have the following in my crontab:
00 06 * * * qcronsub -l h_rt=10:00:00 -l virtual_free=100M
"/home/theo/tools/bsr_notifier.py"
H
owever, upon running qstat about 20 minutes after the cronjob is set to
run, I see...absolutely nothing. And the same an hour later. Help?
--
*Theo (User:Theopolisme on Wikipedia)
http://enwp.org/wiki/User:Theopolisme<http://en.wikipedia.org/wiki/User:Theopolisme>
*
https://www.mediawiki.org/wiki/Amsterdam_Hackathon_2013
Today is the last day to register for the Amsterdam hackathon (May
24-26) and request a scholarship.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hello all. I use this
way<https://wiki.toolserver.org/view/Submit.toolserver.org#resource_definition@…>for
running crons. I make a file named
*something.sh *for example, encluding the following:
*#!/bin/sh
#$ -j y
#$ -o /dev/null
cd pywikipedia
python anyscript.py*
Then, I put a cron like:
*00 21 * * * cronsub -s something % sh $HOME/something.sh*
The problem is that I want my crons to stop producing output files at
"home" folder inside my account, I don't want it to produce outputs at all.
How can I do that?
--
*User:Avocato--*