Posts by Karsten Vinding

21) Message boards : Number crunching : Boinc 7.0.24/Ubuntu computation errors (Message 1226264)
Posted 387 days ago by

I actually got it to run now.

Reporting 7.0.26 in Boinc Manager.

Its crunching away on two AP WU's and DL'ing more.

And I have merged the computer with the old install, so its downloading the rest of the old WU's.

Now on to intalling optimized apps, and making it start on bootup. Hope I dont mess it up...

22) Message boards : Number crunching : Boinc 7.0.24/Ubuntu computation errors (Message 1226249)
Posted 387 days ago by

Karsten Vinding

John:

I did.

Do "sudo apt-get remove boinc-manager"
and "sudo apt-get remove boinc-client"

And the original repository install was uninstalled via the repository.

But I see your point about it being 7.0.24, but it should not be.

I will try one last time to install 7.0.26 on top of all this. If this fails I'm going to stop for now.

23) Message boards : Number crunching : Boinc 7.0.24/Ubuntu computation errors (Message 1226238)
Posted 387 days ago by

Karsten Vinding

Oh well, I give up.

Even though I followed the instructions and installed Boincs own 7.0.26 and not 7.0.24 from repository, I still get this:

http://setiathome.berkeley.edu/result.php?resultid=2418178646

http://setiathome.berkeley.edu/result.php?resultid=2417963293

Both AP and MB

Computer is this one, many many failed tasks...

http://setiathome.berkeley.edu/results.php?hostid=6637638

Luckily I got it stopped before it ruined all my allocated WU's.

I'll wait for this to get fixed properly!

But thanks for trying to help xclusive :)

24) Message boards : Number crunching : Boinc 7.0.24/Ubuntu computation errors (Message 1226220)
Posted 387 days ago by

Karsten Vinding

Seems to be running now...

At least Manager started, and is DL'ing files.

Will see if I get errors again.

How do I get it to autostart when Ubuntu boots?

25) Message boards : Number crunching : Boinc 7.0.24/Ubuntu computation errors (Message 1226217)
Posted 387 days ago by

Karsten Vinding

Trying to install BOINC after your instructions (followed to the letter) I get the following when trying to launch boinc:

root@Ubuntu-server:~# sh /home/karsten/BOINC/run_manager
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory

So even manual install won't work. This is getting frustrating/tiresome...

26) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1225450)
Posted 389 days ago by

Karsten Vinding

That's because the minimum buffer of 10 days is also used as an indicator that the host may not connect to the internet for the next 10 days. So BOINC tries to get all tasks finished, uploaded, and reported that early.

Joe

OK. That makes sense (sort of).

What I dont understand is why it behaves this way now, when it didn't when I had the cache set to 10/10 in a desperate attempt to get work.
Back then nothing worked, no work was being requested, no work was being reported, no tasks was in high priority.
The high priority tasks was allready in the cache for the GPU back then.

I have gone down to 6/0.5 on my ATI host because I was hitting a 400 WU limit, and that wasn't enough for 10 days cache for the GPU.
So I was afraid the servers would still try to fill the GPU cache (because the client would still ask for work), but would not send much work because of that limit. And since they honored for the GPU first, the CPU would not get much work.

I havent tried if it works that way in reality, (a 6 days cache should be fine) but I wouldnt be surprised.

27) Message boards : Number crunching : Catalyst 12.4 and Lunatics 6.10 (ati13ati) (Message 1225382)
Posted 389 days ago by

Karsten Vinding

I will add that I am running 12.4 on one of my systems, and its working fine.

I even believe I'm seeing a little bit faster crunching times than with 12.3.

28) Message boards : Number crunching : Boinc 7.0.24/Ubuntu computation errors (Message 1225372)
Posted 389 days ago by

Karsten Vinding

xclusive:

I have subscribed to the launchpad bug and told that "this bug also affects me".

I don't have anything to contribute with, but will keep an eye on the development, so I can react as soon as there is a fix.

29) Message boards : Number crunching : Boinc/seti wont run on my new Ubuntu setup. (Message 1225368)
Posted 389 days ago by

Karsten Vinding

Thanks.

Allready read and commented in that thread, and it wasn't much help anyway, since nobody seems to know whats wrong.

Hope work is going on behind the curtains to get it working.

30) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1225367)
Posted 389 days ago by

Karsten Vinding

Well setting 0.5/10 didn't really work out well.

But setting 10/0.5 in BM settings, seems to have helped.

All my computers are now requesting work like mad (except the Ubuntu one where seti won't work :( ).

A lot of my WU's have gone high priority (?), and every single WU thats finished seems to be uploaded and returned emidiatly. I don't see the large numbers of waiting to report that I had.

Off course the servers are not giving me any work, but at least the client asks for it now.

Why it behaves so differently now, I can't explain.

31) Message boards : Number crunching : Boinc 7.0.24/Ubuntu computation errors (Message 1225321)
Posted 389 days ago by

Karsten Vinding

How annoying.

I updated to Ubuntu 12.04.

The computer basically serves as a server for my Logitech Squeezebox, and crunches on the side.

And of course one of two things for which I actually use the computer, doesn't work :(

Hope they fix it fast.

32) Message boards : Number crunching : Boinc/seti wont run on my new Ubuntu setup. (Message 1225311)
Posted 389 days ago by

Karsten Vinding

I'm having big problems getting Boinc to work on updated Ubuntu 12.04.

I had it running fine on 11.10.

Boinc installs fine and I attach to Seti.

But all WU's end up erroring out with the following:

Stderr output

<core_client_version>7.0.24</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
Stack trace (11 frames):
/usr/bin/boinc(boinc_catch_signal+0x65)[0x48f675]
/lib/x86_64-linux-gnu/libc.so.6(+0x364c0)[0x7f235bf734c0]
/lib/x86_64-linux-gnu/libc.so.6(__strcat_chk+0x39)[0x7f235c043db9]
/usr/bin/boinc[0x412a34]
/usr/bin/boinc[0x412b00]
/usr/bin/boinc[0x43163d]
/usr/bin/boinc[0x431adb]
/usr/bin/boinc[0x41a728]
/usr/bin/boinc[0x4712a4]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f235bf5e76d]
/usr/bin/boinc[0x406a65]

</stderr_txt>

What is wrong, and how do I fix it?

33) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1224972)
Posted 390 days ago by

Karsten Vinding

Correct.

But then that isnt a 10 day cache, which I have told it to maintain... :)

So it should still be requesting work, and its not.

34) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1224960)
Posted 390 days ago by

Karsten Vinding

Well setting cache to 0,5/10 seems to have helped. I now have a large enough cache to last me for about 1 day and some hours.

Boinc reports that I have a 13 day cache, but thats not correct ( I have 119 Wu's + 2 AP, and I crunch ~4-5 WU's an hour (AP's takes ~ half a day)).

But anyway, if it fetches again before running out of work, I'll be more than happy.

35) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1224902)
Posted 390 days ago by

Karsten Vinding

It's a new policy called "hysteresis work fetch" - the plan being to request work less often, but in larger amounts.

OK, that sort of explains it.

So setting boinc to ask for work often, will work better because the downloads are normally having a hard time getting through.

I still don't understand why the decission was made to give the GPU preference in getting work, when the CPU is asking for a LOT more work than the GPU.

My computer is getting work now, but only for GPU. Meanwhile only 4 cores are crunching. If boinc had requested for CPU only, because it needs work the most, this problem wouldn't exist.

While I was writing this, the CPU finally got work, and I can see boinc has started 6 new tasks on the CPU, meaning it was down to crunching on 2 cores.

I still think something is wrong with the way this works.

Its not easy to setup when the system does the opposite of what you would expect.

36) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1224891)
Posted 390 days ago by

Karsten Vinding

Probably you need to readjust your preferences.
Your first setting is to high so boinc ask to late.
If you have 10 / 0.5 change to 0.5 / 10

I'll try that.

Why should it work? Shouldnt boinc try to keep work for 10 days anyway? Or does it somehow control how often it will ask for work?

37) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1224889)
Posted 390 days ago by

Karsten Vinding

Now something is happening:

My CPU finished one of its Wu's, and boinc reacted on this.

29-04-2012 15:20:38 | SETI@home | Reporting 1 completed tasks, requesting new tasks for CPU and ATI
29-04-2012 15:20:38 | SETI@home | [sched_op] CPU work request: 2744569.84 seconds; 0.00 devices
29-04-2012 15:20:38 | SETI@home | [sched_op] ATI work request: 82425.41 seconds; 0.00 devices
29-04-2012 15:20:42 | SETI@home | Scheduler request completed: got 7 new tasks

These 7 new tasks are all for the GPU, which has plenty of work. They are all stalled in download, meanwhile the CPU has finished one more WU, now only running on 6 cores. Boinc won't fetch as long as other WU's are downloading, and it could take some time to just get these 7 WU's downloaded.

This should not happen, with a cache thats supposed to be 10 days, or whatever max limit is set on number of WU's.....

Why hasn't boinc requested CPU work a long time ago?

38) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1224878)
Posted 390 days ago by

Karsten Vinding

I have enabled that setting.

The issue is the client not asking for work.

Its not the "project has no work available" response I'm seeing, the client simply doesn't ask for any work.

I just asked boinc to report finished work. It's down to the last 8 wu's running, nothing in the CPU cache, lots in the GPU cache.

29-04-2012 15:05:48 | SETI@home | Reporting 4 completed tasks, not requesting new tasks
29-04-2012 15:05:48 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
29-04-2012 15:05:48 | SETI@home | [sched_op] ATI work request: 0.00 seconds; 0.00 devices
29-04-2012 15:06:02 | SETI@home | Scheduler request completed

In 15 minutes, two more Wu's will be finished, and the CPU will only be running on 6 out of eight cores. In 1h30m no Wu's will be crunching, except on GPU...

39) Message boards : Number crunching : How does work fetch in 7.0.25 work? (Message 1224868)
Posted 390 days ago by

Karsten Vinding

I have been using 7.0.25 since it was released, and in general I have been pleased with it. Its more tidy in what work is running, and is better at finishing up jobs, instead of having a lot of tasks hanging in unfinished state (when running multiple projects).

For the last weeks I have been running Seti exclusively.
And on my non GPU computers it works perfectly, lots of Wu's cached, and the machines are allways crunching.

But on my two GPU machines not so well. Boinc normally keeps lots of Wu for the GPU's, but the CPU's often run dry.

Especially my fastest computer is having problems. Cache is set at 10/10 days, but still it often runs dry.

Right now I have 8 WU's crunching, and 2 in the cache. Enough for 2 hrs max. Reporting WU's back should make boinc fetch work (and lots of it, if it should last 10 days).
But boinc responds: Reporting 3 completed tasks, not requesting new tasks.

WHY?

I have been keeping an eye on it, and boinc will run the cache completely dry, leaving the CPU with nothing to do, or only work on a few of the CPU's, before it starts asking for work.

Sometimes its without CPU work for many hours.

It's not Wu's that are waiting to be downloaded that prevents fetching, my DL queue is empty.

If I enable another project with CPU crunching, it will start fetching immediatly for that project, and after this, start fetching for Seti, if I disable work fetch for the other project. But it only lasts for a short time, then nothing is fetched again.

This is very annoying behaviour, and it has been doing it for weeks. Letting things settle down, doesn't seem to help.

I think this is a serious bug in work fetch in 7.0.25. It should try to honour the cache settings for both GPU and CPU, when the systems crunches on both.

40) Message boards : Number crunching : checking for an AMD AstroPulse (Message 1218218)
Posted 405 days ago by

Karsten Vinding

No I havent.

I had enough problems getting my current optimized clients running on Linux, so I have just been happy with it.

Placements of the different files, making apps executionable, learning about different user classes (and what they can do), was more than enough to challenge my abilities.

But if there is potentially 5-10% more speed to gain, I would probably try it again.

Should be easier the second time :)

Previous 20 · Next 20