Since a week or so I am using Ubunty Jaunty 9.04 as operating system. Installation went fine, no problems there.
I copied my Boinc folder from a back-up disk to my user folder, started the manager and it just continued as if nothing had changed.
Except: I now get computation errors using Seti. I don't get them with Einstein and Rosetta. Many WU's are crunched well, but now and then there is one with an error. With the previous OS, Hardy Heron, I never had them.

Does anybody else also use Jaunty? If so what are your experiences so far? I must add I do use the Ext4 file system.

---

______
DeMus

I've had the same issue- two of my machines are running Ubuntu 9.04, and they both started having intermittent output file errors after some updates a few days back. I fiddled around with some permissions in the folders and got them working, but the next day the problem returned. The two computers are:

Computer 1
Computer 2

I'm still digging around on it trying to see if I can figure it out, but I'm no Linux expert. Tried all the obvious stuff (revert to stock, redownload optimized, reinstall BOINC, reset, detach and manually attach... etc) to no avail. If I come up with anything, I'll post back in.

Those two machines dominantly crunch on Milkyway (when they can get work, which is infrequent these days) so I'm actively working on getting their seti work sorted out so they can keep plugging away. :)

---

So, I'm not the only one.
Do you also use the EXT4 filesystem?
You wrote you got it using the stock version as well as the optimized version?
I must say I do like Jaunty but these errors are a pain in the ....

---

______
DeMus

Now you're making me think, I haven't had enough coffee yet this morning!

Both computers are running ext3 filesystems; I set them up to be "tried and true" and they worked like champs since I fired them up, until I upgraded from 8.10 to 9.04. Oddly, they ran 9.04 beta and RC perfectly.

I've had the issue with stock applications as well as optimized applications.

I'm pondering switching to a different BOINC version; perhaps something in 6.6.20 isn't playing nice (or something in 9.04 isn't playing nice with 6.6.20.) Might do that today and see what happens.

Edit: Agreed with you on Jaunty- I love the changes they've been making and it's really coming along, but the errors are definitely frustrating. I'm glad it still works as well as it does on my older machines, and my experience is that they've improved a lot of the modern hardware compatability issues that plagued them; my laptops and day desktops all took installs of it without complaint, and some of them have more usnusual setups.

---

Now you're making me think, I haven't had enough coffee yet this morning!

Both computers are running ext3 filesystems; I set them up to be "tried and true" and they worked like champs since I fired them up, until I upgraded from 8.10 to 9.04. Oddly, they ran 9.04 beta and RC perfectly.

I've had the issue with stock applications as well as optimized applications.

I'm pondering switching to a different BOINC version; perhaps something in 6.6.20 isn't playing nice (or something in 9.04 isn't playing nice with 6.6.20.) Might do that today and see what happens.

Well, I still use 6.4.5 (the stable one) and I have these problems as well.
It seems the only common factor we have is Jaunty itself.

---

______
DeMus

Hmm, yeah that would tend to eliminate the idea of it being BOINC at fault. Perhaps I'll downgrade one of the machines back to 8.10 today and see if that clears anything up, which I suspect it would. If Jaunty's to blame, I admit to being rather at a loss to figure out what would be causing it. I don't remember noticing anything about file permission changes or anything being in the release notes, but I'm no expert and tend to miss a lot anyway.

Other thing I noticed- not enough to make this a pattern, but I saw it happen twice... a reboot of the affected machine solved the issue for one set of workunits. The next downloaded batch started producing errors. That happend one time on each machine, and I haven't gotten it to happen again, but that's likely because the two computers had reached daily task limits.

I might have to spend some time today browsing through the Ubuntu forums looking for suspects. :)

---

A few days ago I started a thread about Boinc and Jaunty also. I noticed that even though I set the preferred browser to Firefox, Epiphany is started when I click on a web related button in the Boinc manager (like message boards, your account, etc) Do you also have this?

---

______
DeMus

DeMus, could you reduce as a first test, if the errors disapear if you reduce/ disable your overclock ? This is not the only problem with Jaunty and opt. applications so far.

---

_\|/_
U r s

DeMus, could you reduce as a first test, if the errors disapear if you reduce/ disable your overclock ? This is not the only problem with Jaunty and opt. applications so far.

If you read Brian D. Landis' post you see he also has problems with stock versions of the crunching software.
Yes, I do have my computer overclocked from 2.4 to 3GHz. How did you find out?

But I can try this for a day or so to see if the errors stay away.

---

______
DeMus

...
I'm pondering switching to a different BOINC version; perhaps something in 6.6.20 isn't playing nice (or something in 9.04 isn't playing nice with 6.6.20.) Might do that today and see what happens.
...

The Linux versions of 6.6.20 are not released but still in development state and are only for testing. Check the BOINC download page.

---

_\|/_
U r s

If you read Brian D. Landis' post you see he also has problems with stock versions of the crunching software.
Yes, I do have my computer overclocked from 2.4 to 3GHz. How did you find out?

But I can try this for a day or so to see if the errors stay away.

Brian D. Landis is using 32bit and has different errors than you showing up. He possibly should check especially that "Computer 2" he had listed for permission problems.

---

_\|/_
U r s

A few days ago I started a thread about Boinc and Jaunty also. I noticed that even though I set the preferred browser to Firefox, Epiphany is started when I click on a web related button in the Boinc manager (like message boards, your account, etc) Do you also have this?

I haven't had this problem; everything opens properly in Firefox, which is the preferred browser.

The Linux versions of 6.6.20 are not released but still in development state and are only for testing. Check the BOINC download page.

Yes, and ordinarily I'd just revert to 6.4.5 and be happy, but the trick is I didn't have any issues until some time after upgrading to Ubuntu 9.04 (rather, after some updates to 9.04); I don't think BOINC is to blame. More than likely a bone-headed mistake on my part is- I've played around with Linux on and off for a couple of years but I'm still pretty wet behind the ears. :)

Brian D. Landis is using 32bit and has different errors than you showing up. He possibly should check especially that "Computer 2" he had listed for permission problems.

In the process of doing so right now. Not sure why the permissions would reset themselves as I have them set at the folder level as well as file level- but like I said, I'm not above making a bonehead mistake! :)

---

Computer 1 is successfully crunching after detach/re-attach manually using stock application. The trick becomes if it will persist through a reboot, and then, if it will persist after setting up optimized apps. It's done this before, and will start erroring out after a reboot or a restart of the BOINC manager.

Computer 2 now attempting to download it's task for the day, it's also reverted to stock across the board- we'll see what it does.

Also double checked permissions on both machines and everything looks good (to my inexperienced eye.)

Edit: Computer 2 is now crunching on its appointed task sucessfully. Need to check the same thing- restart manager, computer, etc and make sure that the permissions stick.

Edit 2: The error is very clearly on my part- everything is holding fine on stock apps, but when I switched to optimized apps, all hell's broken loose. I've got something wrong in my app_info I suspect; time to go back to basics and do some reading again. :)

---

Maybe you want to have an other pair of eyes a look at that app_info.xml of yours to help you.

(oops the thread moved. Irritating if there is no email sent upon moderator action)

---

_\|/_
U r s

@ DeMus
I'll tryout myself with Kubuntu9.04amd64 liveCD to see if i also can produce that error.

---

_\|/_
U r s

Maybe you want to have an other pair of eyes a look at that app_info.xml of yours to help you.

(oops the thread moved. Irritating if there is no email sent upon moderator action)

Took me a minute to find it again as well. I think, maybe? I have found my mistake.

I downloaded the optimized app onto another machine and unarchived it in a shared directory (this machine is my file server at home.) I then got on the machine doing the crunching, and copied over the app and app_info with BOINC shut down, restarted BOINC and got errors.

On a whim, I re-downloaded the app on the machine to use it and unarchived it on the desktop, then copied over the app and app_info (this is the same app from the same site), and it works perfectly. This to me begs the question- does unarchiving it on the local machine somehow set a flag or permission that lets it do its magic, whereas copying an already unarchived app from a different machine cause an issue? That's way beyond my skills to determine. Anyway it seems to work- call it a permission issue or a corrupted download; it's working fine on one machine. The other I won't know until tomorrow when it can get a new task, since it's errored down to 1 per day.

Edit: Now that I think about it, I had the same problem with 3 of my linux machines running Milkyway- I suspect that my problem was solved then as well when I unarchived the app on the machine in question rather than copying the uncompressed app from my local file server.

Time to find a copy of Linux for Dummies! :)

---

Maybe you want to have an other pair of eyes a look at that app_info.xml of yours to help you.

(oops the thread moved. Irritating if there is no email sent upon moderator action)

Well, about the app_info_xml you are talking about: I have 2 of them. I switched from one optimized version to another and in both I get the errors.
First I had the 64 bits AK V8 SSSE3 version for MB WU's, now I use the SSSE3 version for MB's and AP500 for the AP WU's.
As I said both of them have the errors.

I did lower the CPU frequency to around 2.75GHz, let's see if the errors still happen. To be honest I do hope they still keep coming because I do want to go back to 3GHz to have maximum functionality in my computer.

---

______
DeMus

...I did lower the CPU frequency to around 2.75GHz, let's see if the errors still happen. To be honest I do hope they still keep coming because I do want to go back to 3GHz to have maximum functionality in my computer.

I'm no expert to this, but what else than OC or overheating should throw a bad_alloc?

terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc

Moreover if it's only occasionally.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

These reports about compute errors suddenly started last week when the first people out here had updated to Ubuntu 9.04 (and its kinds). If that is not a coincidence that there is now something not correct with Jaunty ... guess the rest for yourself.
Maybe the corrected a long hidden bug in a lib and now all older programs have to be recompiled. We'll see.

---

_\|/_
U r s

...I did lower the CPU frequency to around 2.75GHz, let's see if the errors still happen. To be honest I do hope they still keep coming because I do want to go back to 3GHz to have maximum functionality in my computer.

I'm no expert to this, but what else than OC or overheating should throw a bad_alloc?

terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc

Moreover if it's only occasionally.

Gruß,
Gundolf

After I had lowered the CPU frequency to 2.75GHz I also had 2 computation errors. CPU temp. was around 58C, the hottest core was 67C. This is lower than before when I was using 3GHz as top speed.
I now switched back to this 3GHz and am still without any error, temps now are 60C for the CPU and 72C for the hottest core. One is always a few degrees hotter than the other 3.

I don't think it is caused by the temperature. I have been crunching for over one year now, always running this speed and having these temperatures and never had problems. Now with the new OS it started.
As Urs also said, it must be because of the new OS. Something does not quite fit with the Seti software, or vice versa.

---

______
DeMus