Welcome to MilkyWay@home

Can't write init file: -108 Error

Message boards : Number crunching : Can't write init file: -108 Error
Message board moderation

To post messages, you must log in.

AuthorMessage
STE\/E

Send message
Joined: 29 Aug 07
Posts: 486
Credit: 576,548,171
RAC: 2,284
Message 29118 - Posted: 10 Aug 2009, 0:06:24 UTC

I'm getting a "Can't write init file: -108" Error Message on 1 Box repeatedly not every Wu but often enough to be of some concern. Since I don't see the error on any of my other Box's I assume it's something to do with that specific Box but don't know what it could be ...

Task ID 71965752
Name gs_82test_2Stream_1_1503047_1249861628_0
Workunit 70809486
Created 9 Aug 2009 23:47:10 UTC
Sent 9 Aug 2009 23:47:13 UTC
Received 9 Aug 2009 23:48:35 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -185 (0xffffffffffffff47)
Computer ID 36377
Report deadline 12 Aug 2009 23:47:13 UTC
CPU time 0
stderr out <core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
Can't write init file: -108
</message>
]]>

Validate state Invalid
Claimed credit 0
Granted credit 0
application version 0.19
ID: 29118 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile banditwolf
Avatar

Send message
Joined: 12 Nov 07
Posts: 2425
Credit: 524,164
RAC: 0
Message 29125 - Posted: 10 Aug 2009, 0:48:59 UTC - in response to Message 29118.  
Last modified: 10 Aug 2009, 0:49:37 UTC

*edit*May not be the same error.

See if this helps any: http://boincfaq.mundayweb.com/index.php?language=1&viewCat=3

ERR_FOPEN -108

1. BOINC has a problem opening or writing one or more files. One of the ways to get this error is by hiding the BOINC directory and its sub directories. Then BOINC can't find where it is running from.

Solution: Do not hide your BOINC directory.

2. BOINC finds that the file is open and in use by another process, or BOINC cannot write to the file.

Solution: Exit BOINC completely and restart it.

3. It may happen, that when an application hangs while opening/writing to a file and then terminates abnormally (e.g. via Task Manager or even BOINC), this (formerly opened) file may stay locked even if the application is terminated (due to file locks are handled by the OS - e.g. file locks on network shares are handled by the OS for the network PC/Server - the OS needs a definite "remove this lock!" from the calling application to remove it).

Solution: Restart your computer.

4. You installed BOINC as an administrator but run it as another user and didn't give that user rights to write to the BOINC directory/subdirectories. The directories their read-only attributes are set.

Solution: Either run BOINC as administrator, or give the user you want to run under rights to write to the BOINC directory and subdirectories.

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.
ID: 29125 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
STE\/E

Send message
Joined: 29 Aug 07
Posts: 486
Credit: 576,548,171
RAC: 2,284
Message 29137 - Posted: 10 Aug 2009, 8:16:19 UTC

I got rid of the "Can't write init file: -108" Error Message on that Box BW after reading your Post, Thanks

I'm not sure what got rid of it but I think it might have had something to do with a slot file that I couldn't delete. I had to copy all the rest of the files on that BOINC only Partition & then Format the Partition to get rid of the slot file.

I copied all the files back after Partitioning it and let it run over night and I don't see any new "Can't write init file: -108" Error Message's so I'm assuming it's gone for now anyway ... :)
ID: 29137 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Can't write init file: -108 Error

©2024 Astroinformatics Group