Re: [Toolserver-l] Cron on submit

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 >

[Toolserver-l] Cron on submit

-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

Re: [Toolserver-l] SGE errors

Ok, now I've just gotten an email: error: unable to send message to qmaster using port 536 on host "damiana": got send error error: commlib error: can't connect to service (Connection refused) error: commlib error: can't connect to service (Connection refused) Unable to run job: unable to send m

Re: [Toolserver-l] SGE errors

I'm on willow, and I'm not getting any email errors, but it looks like my cron jobs are being very seriously delayed. My one bot is supposed to run every two hours on the hour, but the interval between runs is increasing steadily. User:Hersfold hersfoldw...@gmail.com On 2/3/2013 2:32 PM,

Re: [Toolserver-l] SGE errors

I'm having the same problem, for two days, and by what i can see, it's happening only on hawthorn. Alchimista 2013/2/3 Bryan Tong Minh > Hello, > > > SGE is spewing out various JSV errors, included below. Anybody an idea > what is going on? > > > Bryan > > Cron qcronsub -l h_rt=00:10:00 -l ar

[Toolserver-l] SGE errors

Hello, SGE is spewing out various JSV errors, included below. Anybody an idea what is going on? Bryan Cron qcronsub -l h_rt=00:10:00 -l arch=* -l virtual_free=200M -e $HOME/replag-plot.err -N replag-plot /home/bryan/public_html/stats/replag/make-plot.sh error: JSV stderr: Traceback (most rece

[Toolserver-l] Contacting me

Hello all, few days ago my mom got a telephone-call by an English speaking person babbling something about "servers" (she was not able to understand more and terminated the line). I'm not saying that it was one of you, but the incident inspired me for the following declaration: *NEVER* call me