System is Linux with a NVIDIA 650ti GPU

I am seeing the following in job outputs:
<core_client_version>7.0.29</core_client_version>
<![CDATA[
<stderr_txt>
parse_init_data_file: no end tag
22:14:16 (24029): Can't parse init data file - running in standalone mode
parse_init_data_file: no end tag
22:14:16 (24029): Can't parse init data file - running in standalone mode
setiathome_v7 7.00 Revision: 1782 g++ (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2)
libboinc: BOINC 7.1.0

Any idea what is causing this?

I saw the reply to your post over at EAH. I'm going to say that the problem is with the version of BOINC you are running, since 7.0.29 isn't even the suggested older version for any platform.

I saw the reply to your post over at EAH. I'm going to say that the problem is with the version of BOINC you are running, since 7.0.29 isn't even the suggested older version for any platform.

As posted on the EAH website the binary downloaded from the boinc site was generated under an UBUNTU distro. The libraries used are not part of FC17 and my attempts at locating them have failed.

Even with this error jobs run to completion, and credits are granted. This is a bit confusing. I would think that all jobs would fail.

Earlier I killed the 24 hour seti WU in the hopes of installing a new BOINC but now I am back to the original. I will look further into locating the missing libs but until then ....

---

http://www.usefulramblings.org

That's only because there are some problems with validation as the new MBv7 app gets settled in.

Normally, if a task dies for any reason you get the big goose egg for credit.

I'm going to say that the problem is with the version of BOINC you are running, since 7.0.29 isn't even the suggested older version for any platform.

It is on all the RPM sites for Fedora 17.
e.g. site 1, site 2.

Berkeley BOINC is built with Ubuntu 12.04 LTS

---

You could try looking into what exactly is it that the apps don't like in the init data file.

The file is called init_data.xml. Each slot directory has its own file. Since the apps that show the error are from Seti and Einstein try to pick a slot that either one is using.

If you think it's best to copy-paste the file here do note that the file contains your authenticator which is something you'll want to blank first.

You may also want to make sure file and/or directory permissions are ok.

I'm going to say that the problem is with the version of BOINC you are running, since 7.0.29 isn't even the suggested older version for any platform.

It is on all the RPM sites for Fedora 17.
e.g. site 1, site 2.

Berkeley BOINC is built with Ubuntu 12.04 LTS

All I meant was IIRC, after 7.0.28 was placed as the recommended version back in the day the alpha builds progressed pretty rapidly at first while they worked towards the last recommended which was 7.0.44.

Although, as I have said before, Linux isn't my strong suit and I don't follow it's BOINC releases all that close and was just going off what's on the BOINC site's all downloads page.

In any event, you would think robl can find one which works off the two sites you posted links to! ;-)

All I meant was IIRC, after 7.0.28 was placed as the recommended version back in the day the alpha builds progressed pretty rapidly at first while they worked towards the last recommended which was 7.0.44.

The Linux recommended through RPM sites has long time been 7.0.27, which had trouble on its own.

the whole problem with the older distros is that the libraries aren't updated towards their version. So in this case, even though for instance the BOINC wiki states that you have to have certain library files, it doesn't mean that the library files in fedora 17 are all up to date. Even while their name may be the same. Like libc.so.6, you can't see on the outside which version that is, but it is a requirement that BOINC has.

Building BOINC yourself is going to be problematic, although not impossible. Not something I've ever done on Linux, I must say. I did build for Windows. A long time ago. When Visual Studio 2005 was still the thing to use. ;-)

Biggest problem with Fedora 17 and present BOINC is the lack of compatible or up-to-date GlibC libraries. The only way around it that I see, is to update to fedora 18 or 19.

The APP_INIT_DATA.xml file keeps track of the elapsed time that a task took. Seeing the BOINC Wiki, it looks to be a problem with the science application, or at least with the BOINC API. Not saying it still can't be a problem with BOINC, but problems with it were fixed in 6.13/7.0.3.

---

Building BOINC yourself is going to be problematic

Not really.

The APP_INIT_DATA.xml file keeps track of the elapsed time that a task took. Seeing the BOINC Wiki, it looks to be a problem with the science application, or at least with the BOINC API. Not saying it still can't be a problem with BOINC, but problems with it were fixed in 6.13/7.0.3.

The init_data.xml file contains other stuff too, like your name and team, project preferences and a lot more, which you surely knew.

I'd guess in this case either BOINC can't write it properly or it has something in it that gets BOINC's not-really-xml-parser confused.

All I meant was IIRC, after 7.0.28 was placed as the recommended version back in the day the alpha builds progressed pretty rapidly at first while they worked towards the last recommended which was 7.0.44.

The Linux recommended through RPM sites has long time been 7.0.27, which had trouble on its own.

the whole problem with the older distros is that the libraries aren't updated towards their version. So in this case, even though for instance the BOINC wiki states that you have to have certain library files, it doesn't mean that the library files in fedora 17 are all up to date. Even while their name may be the same. Like libc.so.6, you can't see on the outside which version that is, but it is a requirement that BOINC has.

Building BOINC yourself is going to be problematic, although not impossible. Not something I've ever done on Linux, I must say. I did build for Windows. A long time ago. When Visual Studio 2005 was still the thing to use. ;-)

Biggest problem with Fedora 17 and present BOINC is the lack of compatible or up-to-date GlibC libraries. The only way around it that I see, is to update to fedora 18 or 19.

The APP_INIT_DATA.xml file keeps track of the elapsed time that a task took. Seeing the BOINC Wiki, it looks to be a problem with the science application, or at least with the BOINC API. Not saying it still can't be a problem with BOINC, but problems with it were fixed in 6.13/7.0.3.

Ageless, I am not questioning your skillset but before I migrate to fedora 18/19 can you explain why those releases of fedora would eliminate the problem I am currently having, i.e., what makes them more BOINC friendly. I believe that FC 17 is coming to an end but I would like to be reasonably sure that such an effort would produce better results than what I am having with FC 17. I have never successfully upgraded a Fedora release. It has always been a virgin install so there is time involved and time seems to always be an elusive bird.

---

http://www.usefulramblings.org

Ageless, I am not questioning your skillset but before I migrate to fedora 18/19 can you explain why those releases of fedora would eliminate the problem I am currently having, i.e., what makes them more BOINC friendly.

To be honest, I cannot. I'm not even sure if your problem is a BOINC problem or an application error. But seeing how you have it at two different projects, makes me swing towards BOINC first. You can test that by going back one or more versions.

e.g. if the 6.12.43 from here does it as well, it's a science app problem. Do know that before you swing back to 6.12 you best set NNT, run your cache empty, report all. If things do manage to run correctly, that is. ;-)

---

You could try looking into what exactly is it that the apps don't like in the init data file.

The file is called init_data.xml. Each slot directory has its own file. Since the apps that show the error are from Seti and Einstein try to pick a slot that either one is using.

If you think it's best to copy-paste the file here do note that the file contains your authenticator which is something you'll want to blank first.

You may also want to make sure file and/or directory permissions are ok.

I checked the directory and file permissions and ownership. They seem to be fine.

I checked a currently running E&H wu's init_data.xml file and looking through it I did not see anything which indicated an error condition, but then again I am not sure what I would see. This job was estimated at 6 hours but is now running at the 8:52 hour mark. boinc manager's "remaining estimated time" is showing as "---".

I will let it continue and see if it ever completes.

---

http://www.usefulramblings.org

Looks like folks at Einstein found the problem.

What they didn't tell you that the bug was introduced in 7.0.30 and fixed in 7.0.31. (I don't know how Fedora managed to get it into 7.0.29.) Going back to an earlier release might be the solution for you.

This job was estimated at 6 hours but is now running at the 8:52 hour mark. boinc manager's "remaining estimated time" is showing as "---".

Since the app thinks it's running standalone it doesn't send any progress info to BOINC so BOINC can't compute any meaningful remaining estimated time.

Looks like folks at Einstein found the problem.

What they didn't tell you that the bug was introduced in 7.0.30 and fixed in 7.0.31. (I don't know how Fedora managed to get it into 7.0.29.) Going back to an earlier release might be the solution for you.

This job was estimated at 6 hours but is now running at the 8:52 hour mark. boinc manager's "remaining estimated time" is showing as "---".

Since the app thinks it's running standalone it doesn't send any progress info to BOINC so BOINC can't compute any meaningful remaining estimated time.

Juha,

Thanks for your input, especially the part about "can't compute any meaningful estimated time".

---

http://www.usefulramblings.org

I had to migrate from FC17 to Ubuntu 12.04 LTS to get back into the game.

Thanks to everyone who responded.

---

http://www.usefulramblings.org