Database gone -> Scheduler confused

Message boards : Server programs : Database gone -> Scheduler confused
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Ananas

Send message
Joined: 27 Jun 06
Posts: 305
Germany
Message 20617 - Posted: 1 Oct 2008, 21:21:58 UTC

The SETI database seems to have crashed. This problem is not correctly handled by the scheduler, it returns funny messages to the clients :

<scheduler_reply>
<scheduler_version>603</scheduler_version>
<master_url>http://setiathome.berkeley.edu/</master_url>
<request_delay>3600.000000</request_delay>
<message priority="low">Can't find host record Invalid or missing account key.  Detach and reattach to this project to fix this. </message>
<project_name>SETI@home</project_name>
</scheduler_reply>


This advice is plain nonsense of course, detach/reattach will trash work but not fix the database
ID: 20617 · Report as offensive
Profile David Anderson
Volunteer moderator
Project administrator
Project developer
Avatar

Send message
Joined: 10 Sep 05
Posts: 717
Message 20621 - Posted: 1 Oct 2008, 22:14:06 UTC

Try doing what it says; the S@h DB is fine.
ID: 20621 · Report as offensive
Profile Ananas

Send message
Joined: 27 Jun 06
Posts: 305
Germany
Message 20623 - Posted: 1 Oct 2008, 22:34:39 UTC - in response to Message 20621.  
Last modified: 1 Oct 2008, 22:34:54 UTC

Try doing what it says; the S@h DB is fine.


Now it is fine, yes, and my client has already reported the tasks.

But when that scheduler message returned, the status page said "Disabled" for the database on jocelyn - so there was probably not even a crash but just a short planned maintenance outage.
ID: 20623 · Report as offensive
mo.v
Avatar

Send message
Joined: 13 Aug 06
Posts: 778
United Kingdom
Message 20624 - Posted: 1 Oct 2008, 22:58:33 UTC
Last modified: 1 Oct 2008, 23:03:45 UTC

If the computer has other tasks from the project still in progress or ready to upload or ready to report and you follow the advice to detach from the project then reattach, how would it be possible not to lose the credit and progress from these tasks?

Or is there a special situation where detaching & reattaching wouldn't have their usual consequences?

Under what circumstances does BOINC advise crunchers (not just from SETI) to detach from a project?
ID: 20624 · Report as offensive
Profile Ananas

Send message
Joined: 27 Jun 06
Posts: 305
Germany
Message 20625 - Posted: 1 Oct 2008, 23:05:27 UTC - in response to Message 20624.  

...Or is there a special situation where detaching & reattaching wouldn't have their usual consequences? ...


I highly doubt that - especially as a reattach would not have succeeded with a scheduler that is unable to query the database.
ID: 20625 · Report as offensive
Profile Ananas

Send message
Joined: 27 Jun 06
Posts: 305
Germany
Message 20626 - Posted: 1 Oct 2008, 23:23:13 UTC - in response to Message 20624.  
Last modified: 1 Oct 2008, 23:23:58 UTC

...
Under what circumstances does BOINC advise crunchers (not just from SETI) to detach from a project?


In this situation, it does that when a host is attached using the original ("strong") authenticator and a user lookup by authenticator fails.

There should be a log entry (severity=critical) about that incident, if logging is enabled.

Maybe it would be a good idea, to treat at least CR_SERVER_LOST and CR_SERVER_GONE_ERROR from mysql_query() different than a normal "not found" error.
ID: 20626 · Report as offensive

Message boards : Server programs : Database gone -> Scheduler confused

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.