LHC@home

Well ... that's the message I'm receiving :

LHC@home - 2004-10-09 19:13:39 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain

I'm using Windows XP SP2 on a 2,4 Pentium IV

Boinc Ver. 4.09
sixtrack 4.46

Anyway one minute later it has retried and succeed ... I'm posting just in case anyone else finds the same error

Best regards,
Offler
http://www.astroseti.org

I also had this message come up but I suspect that it was due to LHC's server being down around that time.

Just my opinion of course, could be wrong

This message seems to pop up when the LHC server is particularly busy. It indicates that the limit on the number of DB connections has been exceeded. It will generally clear at the next attempt since some DB connections will probably have been released.

The number of DB connections allowed is parameter that the admins can use for tuning the DB performance. Sometimes its effect is counter intuitive. From notes in the forum from the admins it seems that setting the connection limit to 400 resulted in fewer transactions being processed than when it was set to 50!

See Markku's full comments here


Giskard - the first telepathic robot.

> This message seems to pop up when the LHC server is particularly busy. It
> indicates that the limit on the number of DB connections has been exceeded. It
> will generally clear at the next attempt since some DB connections will
> probably have been released.


That's not really the reason for this error message.

The server _does_ issue a correct error message about the database overload but preceeds it with the mime type. This confuses the BOINC function SCHEDULER_REPLY::parse(), which requires the first line to contain "[scheduler_reply]"

Although this is caused by the sender side, I think, the parser on client side should just ignore the mime type entry "Content-type:" or even everything outside of the scheduler_reply tags.

I think, CPDN had the same problem earlier - would really be good to parse less picky in this case. It would be a 5 minute task to fix the function.

> I also had this message come up but I suspect that it was due to LHC's server
> being down around that time.
>
> Just my opinion of course, could be wrong


Will be fixed with the next BOINC client. If the database is too busy, BOINC will give the correct error message.