LHC@home

First WU crunched in less then 9 minutes, get probably out of the accelerator. It seems it uploaded without problem, but then came following:

LHC@home - 2005-02-21 21:08:24 - Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi
LHC@home - 2005-02-21 21:08:38 - Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
LHC@home - 2005-02-21 21:08:38 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain
LHC@home - 2005-02-21 21:08:38 - Can't parse scheduler reply
LHC@home - 2005-02-21 21:08:38 - Deferring communication with project for 1 minutes and 0 seconds
LHC@home - 2005-02-21 21:09:38 - Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi
LHC@home - 2005-02-21 21:09:41 - Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
LHC@home - 2005-02-21 21:09:41 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain
LHC@home - 2005-02-21 21:09:41 - Can't parse scheduler reply

---

Best greetings from Belgium
Thierry

LHC@home - 2005-02-21 21:08:38 - SCHEDULER_REPLY::parse(): bad first tag
> Content-type: text/plain
> LHC@home - 2005-02-21 21:08:38 - Can't parse scheduler reply

This is an old one. It happens when the server has too many DB connections.

We are currently submitting more jobs, which is very CPU-and-DB-time consuming task, so the new server is having quite a nice stress test right now.

---

Markku Degerholm
LHC@home admin