LHC@home

I just got the scheduler message :

[scheduler_reply]
[message priority="low"]Server can't open database[/message]
[request_delay]14400[/request_delay]
[project_is_down/]
[/scheduler_reply]
[scheduler_reply]
[project_name]LHC@home[/project_name]
[/scheduler_reply]

but a few seconds later the scheduler did reply. It seems that some overload condition is not recognized.

(the client didn't recognize the message, that's why it contacted the server again after a minute instead of 4 hours)

This is a server problem - its overloaded with work at the moment and can't respond to your request. This happens quite often on LHC, and that's when the server is UP (its often down). Don't worry about it, it'll recover eventually. I often find that the server, having been offline for a day or so, suddenly comes good about 9am Swiss time, when someone arrives at work, sees a problem, and reboots it.

PeterV.

I wasn't worried, just thought I'd post it, as this time it was not the usual one that says "too many connections". It sounded like a network problem rather than a database overload problem.

It sure can "confuse" a database client when the LAN between the application server and the database server gets lost. That's why it is a good idea to have this connection redundant, i.e. one primary p2p connection between the two machines and a backup one through the normal house-LAN.