Using Seti on Ubunty Jaunty 9.04

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. :)
____________

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.
____________

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. :)
____________

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

...
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.
...

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.

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?

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.

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.

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)

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