Message boards :
Number crunching :
Re: error -108
Message board moderation
Author | Message |
---|---|
The Pirate Send message Joined: 14 Apr 00 Posts: 191 Credit: 4,929,008 RAC: 0 |
|
Pascal, K G Send message Joined: 3 Apr 99 Posts: 2343 Credit: 150,491 RAC: 0 |
Links to Documents by Project or How I found out all the Stuff I Needed to Know About BOINC BOINC GUI Diagnostic Error 108. Failed to cleanup the Windows Sockets Interface" Semper Eadem So long Paul, it has been a hell of a ride. Park your ego's, fire up the computers, Science YES, Credits No. |
The Pirate Send message Joined: 14 Apr 00 Posts: 191 Credit: 4,929,008 RAC: 0 |
This happens on a Linux box not windows and it happens after it has been running a couple of days. S@H keeps running until there are no more WU's to process. Now that I look, I see that just before I get the line scheduler init_op_project to http://setiboincdata.ssl.berkeley.edu/sah_cgi failed, error -108 there are two lines that say: make_scheduler_request: -108 make_scheduler_request: -108 |
Walt Gribben Send message Joined: 16 May 99 Posts: 353 Credit: 304,016 RAC: 0 |
> This happens on a Linux box not windows and it happens after it has been > running a couple of days. S@H keeps running until there are no more WU's to > process. > > Now that I look, I see that just before I get the line > > scheduler init_op_project to http://setiboincdata.ssl.berkeley.edu/sah_cgi > failed, error -108 > > there are two lines that say: > > make_scheduler_request: -108 > make_scheduler_request: -108 -108 means a file open failed. It looks like 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? 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. |
Paul D. Buck Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0 |
> It looks like 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. > ... Walt, I liked your explanation, so I added it along with the message to the FAQ database ... Now the hard question ... can I get you to read the other 120 I have and point out where I screwed up? |
Bob Chr. Laryea Send message Joined: 1 May 02 Posts: 122 Credit: 83,877 RAC: 0 |
Hi there Regards |
Bob Chr. Laryea Send message Joined: 1 May 02 Posts: 122 Credit: 83,877 RAC: 0 |
Hi there I had the same error message E@H error -108 did not get much reply in this thread (e@h) so hope it is ok that i reply here. Thanx & regards Regards |
Paul D. Buck Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0 |
> Hi there Hi! > I had the same error message E@H <a> href="http://einstein.phys.uwm.edu/forum_thread.php?id=382">error -108[/url] > did not get much reply in this thread (e@h) so hope it is ok that i reply > here. If you read the earlier part below, there is a good explanation down there towards the begining ... I will quote the best of it: -108 means a file open failed. It looks like 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? 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. > Thanx & regards You are welcome ... Also, though not complete by any means, click on my signature or the link and find more than you can stand ... All of the messages I have seen, or others have given to me (all 120+) are in the FAQ database. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.