In the past two weeks or so, I've had my linux machine crash on me. When it restarts I get error messages similar to this.

file info outside project in state file

It loses the computer ID and work for every project to which it was connected. It connects using a new computer ID and all new work.

I am running Debian Linux (etch) with kernel version 2.6-15 on an AMD Duron 1200. Boinc core client version 5.4.10.

Any other info needed that I forgot to post?

Thanks in advance.

Jim

---

My guess would be that it damaged the file client_state.xml on the crash.

You could add a little more security to BOINC and make the state file backup do what it is supposed to do (but currently fails to do) :

if [ -f client_state_prev.xml ]
then
 tail -3 client_state.xml 2>/dev/null | grep -q "</client_state>"
 if [ $? -ne 0 ]
 then
   echo "There is a problem with client_state.xml"
   exit 1
 fi
fi

./boinc

Instead of the message you could copy client_state_prev.xml to client_state.xml but sometimes it is better not to do everything automatic.


For windows, this start script would look like this :

@echo off

IF NOT EXIST client_state_prev.xml GOTO start

IF NOT EXIST client_state.xml GOTO error

findstr "</client_state>" client_state.xml

IF %ERRORLEVEL%==0 goto start


:error
echo "There is a problem with client_state.xml"
pause
exit 1


:start

start boinc

_____________________________

Actually this is a thing that the core client should handle in the program startup - but as long as it is not implemented there, it needs to be done like described above.

---

��u�

Ok. thank you for that suggestion.

I will give it a try to see if that helps. Hopefully, though, I'll never get the chance to see it catch an error. ;)

Jim

---

Another question, if I may. What are the proper permission settings for the boinc-client data directory and related files?

I don't know why this would all of a sudden become a problem, but I do want to at least eliminate it as a possibility.

AGain, thanks for the help.

---

(Unix/Linux) If you use the same user for the installation that you use to run BOINC, there should not be a problem as the installer tar archive knows the rights for the static files and the downloader / worker tasks know the required rights for their files too.

Except for the language directories, the user running BOINC should be allowed everything (rwx) on the directories. Write access to the language directories is not needed.

---

��u�

Again, thank you for that info.

A couple of months ago I made a back up of my boinc directory, reformated my hard-drives and reinstalled Linux. As a result, not everything was put back as pristine as it should have been. I also realized what I was inadvertently doing to make it work. I think I might have it working properly now. If not, I'm sure I'll be back for more info. :)

Jim

---