This WU bombed out with the following error...

stderr out

<core_client_version>5.2.7</core_client_version>
<message> - exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2

File: \\home\\korpela\\seti_boinc\\client\\worker.cpp
Line: 134


</stderr_txt>


I was having connectivity issues with my DSL and I was rebooting multiple times to try to fix it. After being shut down all day while I was at work, I restarted the computer and BOINC crashed on opening (something that rarely happens). And, this WU bombed. All other in progress or stuck in uploading WUs are ok.

Never seen this error before...

Oh well. 26 hours down the tubes :( Such is life on a Beta project. Time to start the next one.

Kathryn

---

Kathryn :o)
The BOINC FAQ Service
The Unofficial BOINC Wiki
The Trac System
More BOINC information than you can shake a stick of RAM at.

Kathryn

I posted a thread about a similar happening... One of the things that is known is that at times BOINC does not always close files properly (or read "client_state.xml.bak)... There are fixes that are beyond the BOINC Core 5.2.7 that you are using or the 5.2.13 that also had the same problem on my part.

This WU bombed out with the following error...

stderr out

<core_client_version>5.2.7</core_client_version>
<message> - exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2

File: \\home\\korpela\\seti_boinc\\client\\worker.cpp
Line: 134

</stderr_txt>

I was having connectivity issues with my DSL and I was rebooting multiple times to try to fix it. After being shut down all day while I was at work, I restarted the computer and BOINC crashed on opening (something that rarely happens). And, this WU bombed. All other in progress or stuck in uploading WUs are ok.

Never seen this error before...

Oh well. 26 hours down the tubes :( Such is life on a Beta project. Time to start the next one.

Kathryn

I would hope that besides becoming and Alpha Tester for the Update BOINC Core that we could get feedback for updated Core Clients (@Eric, many here would be will to help).

Regards

Al

---

Thanks to Paul and Friends
Please consider a Donation to the Seti Project

I posted a thread about a similar happening... One of the things that is known is that at times BOINC does not always close files properly (or read "client_state.xml.bak)... There are fixes that are beyond the BOINC Core 5.2.7 that you are using or the 5.2.13 that also had the same problem on my part.

This should be fixed in 5.3.22 now. I'll test it later on today, but am clearing most of my cache beforehand. Just to be sure.

I'll backup client_state.xml, then delete the last parts in it, save the file and start Boinc. It should check the CS file and pick up Client_state_prev.xml automatically.

---

Kathryn

I posted a thread about a similar happening... One of the things that is known is that at times BOINC does not always close files properly (or read "client_state.xml.bak)... There are fixes that are beyond the BOINC Core 5.2.7 that you are using or the 5.2.13 that also had the same problem on my part.

This WU bombed out with the following error...

stderr out

<core_client_version>5.2.7</core_client_version>
<message> - exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2

File: \\home\\korpela\\seti_boinc\\client\\worker.cpp
Line: 134

</stderr_txt>

I was having connectivity issues with my DSL and I was rebooting multiple times to try to fix it. After being shut down all day while I was at work, I restarted the computer and BOINC crashed on opening (something that rarely happens). And, this WU bombed. All other in progress or stuck in uploading WUs are ok.

Never seen this error before...

Oh well. 26 hours down the tubes :( Such is life on a Beta project. Time to start the next one.

Kathryn

I would hope that besides becoming and Alpha Tester for the Update BOINC Core that we could get feedback for updated Core Clients (@Eric, many here would be will to help).

Regards

Al

Thanks. I did update to 5.2.13 today. This is the first time I've had problems in a very long time. After the upgrade everything picked up from where it left off.

Now I'm just waiting for Seti Beta to work off it's LTD so I can get some new work....

Kathryn

---

Kathryn :o)
The BOINC FAQ Service
The Unofficial BOINC Wiki
The Trac System
More BOINC information than you can shake a stick of RAM at.

This should be fixed in 5.3.22 now. I'll test it later on today, but am clearing most of my cache beforehand. Just to be sure.

I'll backup client_state.xml, then delete the last parts in it, save the file and start Boinc. It should check the CS file and pick up Client_state_prev.xml automatically.

Excellent. I shall keep my fingers crossed. I have had problems during power outages in the past having the CS file corrupted and basically resets the project. Thanks much for the info on this long awaited fix!

Regards, Daniel.

---

It worked. I deleted the last 20 lines in Client_state.xml, saved the file, restarted Boinc.

It picked up on the client_state_prev.xml file immediately, saved the normal client_state.xml file and wrote a new client_state_prev.xml file. :)

---

It worked. I deleted the last 20 lines in Client_state.xml, saved the file, restarted Boinc.

It picked up on the client_state_prev.xml file immediately, saved the normal client_state.xml file and wrote a new client_state_prev.xml file. :)

OUTSTANDING! Thanks, Jord! I appreciate the update.

Regards, Daniel.

---