I am using BOINC under a Linux system, which I am not yet used to, but it was working ine until a few days ago.

Now, this is all I see when I return from the end of my work day, bummer.

Something I did ? Didn't do and should have perhaps ?

Also note please, at the same time I am still using SETI Classic, and it is working better now, much fast process time, than when I was using it in any flavor of Windows operating system, hmmmm.

I am using the standard callup in a shell for BOINC along with my user I/D, but this is all I am receiving of late.

Any resolves for this please ? Perhaps I need a complete re-install, oh boy.... ..



2005-02-25 16:58:59 [SETI@home] Deferring communication with project for 46 minutes and 38 seconds
2005-02-25 16:58:59 [SETI@home] Deferring communication with project for 46 minutes and 38 seconds
2005-02-25 17:45:37 [SETI@home] make_scheduler_request: -108
2005-02-25 17:45:37 [SETI@home] make_scheduler_request: -108
2005-02-25 17:45:37 [SETI@home] scheduler init_op_project to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -108
2005-02-25 17:45:37 [SETI@home] scheduler init_op_project to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -108

---

"Find solutions, not fault."

> Any resolves for this please ? Perhaps I need a complete re-install, oh
> boy.... ..

I'd wait a couple of days at a minimum before you get too worried: the project has had some stunningly bad luck and now that they're up it's going to take a day or two for all the machines out there report in.

---

>
> > Any resolves for this please ? Perhaps I need a complete re-install, oh
> > boy.... ..
>
> I'd wait a couple of days at a minimum before you get too worried: the project
> has had some stunningly bad luck and now that they're up it's going to take a
> day or two for all the machines out there report in.
>
I am very patient. I just leave it running and hoping it will soon connect and make exchange.

Thanks so much for the reply also.

Cheers.... ..

---

"Find solutions, not fault."

The error comes from when BOINC is setting up a request to send to the scheduler. Before the communications starts even.

-108 means a file open failed.

"Make scheduler request -108" means BOINC was setting up a message to send to the scheduler, but couldn't open the file to store the message. Thats where the error comes from, it was trying to open the file "scheduler_request_setiathome.berkeley.edu.xml" and that failed.

The same file gets reused each time - gets created if it doesn't exist, and overwritten it it does.

So check the BOINC directory for that file and see whats stopping BOINC from opening it. Could be a permissions problem. And the date might give you a clue as to when it was last written, did you change BOINC around then? Compare it to the client_state.xml file, that gets rewritten every minute. Do they show the same permissions, owner and group?

And since you're running Linux, you might see something logged in the system messages or security log.

You could try removing the two scheduler files and just let BOINC recreate them when they're needed. They're scheduler_request_setiathome.berkeley.edu.xml and scheduler_reply_setiathome.edu.xml.

I had the same error -- mine was permissions. The install set the correct permissions on the base directory, but not the ones underneath it.