On 02/13/2013 02:31 PM, Michael Andersen wrote:
Perhaps someone could create a tool to
extend the number of hours per day? :-D
I think this tool would be needed very urgently. Is there any space API
or hardware interface specification? :=D
Cheers
Marco
_
ad. Perhaps someone could create a tool to extend the number of
hours per day? :-D
MGA73
-Oprindelig meddelelse-
Fra: toolserver-l-boun...@lists.wikimedia.org
[mailto:toolserver-l-boun...@lists.wikimedia.org] På vegne af Carl (CBM)
Sendt: 12. februar 2013 19:35
Til: Wikimedia Toolserver
Emne
On Sun, Feb 10, 2013 at 5:48 PM, Wolfgang ten Weges wrote:
> a "top" shows that the culprits are likely the same as last time :
> All the CPU, and a lot of process slots (and cron slots most probably) are
> currently (ab)used by /home/javadyou/pywikipedia/radeh7.py and
> /home/reza/pywikipedia/ra
a "top" shows that the culprits are likely the same as last time :
All the CPU, and a lot of process slots (and cron slots most probably)
are currently (ab)used by /home/javadyou/pywikipedia/radeh7.py and
/home/reza/pywikipedia/radeh.py
Wolfgang ten Weges/Wolfgang
Le 04/02/2013 20:21, Dr.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks DaB whatever you (or someone else? ;) did!
Now it works again as you can see from looking at [1] there was clearly
a drop in executed jobs now it is on a constant level again! Cool!
[1] http://munin.toolserver.org/Login/hawthorn/cron_jobs_sh.h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.02.2013 01:30, DaB. wrote:
>> I am now noticing issues with my cronjobs too.
>
> What exactly is the problem?
Cronjobs not getting executed (as usual... ;) - at the moment I do
also have jobs in SGE queue that do not get runned at all (at least
Hello,
At Monday 04 February 2013 01:23:08 DaB. wrote:
> Hello!
>
> There were 2 messages here during Janury reporting problems with cron.
Both where on willow AFAIS, which is overloaded.
> I am now noticing issues with my cronjobs too.
What exactly is the problem?
> > By looking at [1] you
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
There were 2 messages here during Janury reporting problems with cron.
I am now noticing issues with my cronjobs too. By looking at [1] you
are able to see that the strange behaviour started somewhen week 2 and
3 (mid January). Do we have again