1) Forums : Wish list : Switch on the mail-component (Message 5844)
Posted 6 Apr 2008 by Yeti
Post:
Meanwhile this seems to work, Great :-))

One small thing: The link in the mail is the old: http://cosmologyathome.org/forum_thread.php?id=21

The www is missing.

Yeti
2) Forums : Technical Support : 2.11 seems much better (Message 5191)
Posted 13 Mar 2008 by Yeti
Post:
@all with problems restarting 2.11er WUs:

Would be interesting to know, wheather you have set \"Leave applications in memory while suspended\" to no ?

If so, switch it to Yes and give it a try

Yeti

3) Forums : Technical Support : 2.11 seems much better (Message 5154)
Posted 10 Mar 2008 by Yeti
Post:
Did any of your hosts exhibit the behavior of running for the first several minutes with no change to the progress indicator? I\'m concerned about that as it could cause people to abort tasks thinking that nothing was happening...

If I remember right, the progress was shown immediatly, but sorry, I don\'t know exactly, because I don\'t bother about this detail.

I will have to watch it explicitly, this will take some time ...



Just gave it a try:

The percentage started after 5 Minutes of crunching time. I think, this shouldn\'t be a problem, a lot of projects behave like this
4) Forums : Technical Support : 2.11 seems much better (Message 5146)
Posted 10 Mar 2008 by Yeti
Post:
Did any of your hosts exhibit the behavior of running for the first several minutes with no change to the progress indicator? I\'m concerned about that as it could cause people to abort tasks thinking that nothing was happening...

If I remember right, the progress was shown immediatly, but sorry, I don\'t know exactly, because I don\'t bother about this detail.

I will have to watch it explicitly, this will take some time ...

5) Forums : Technical Support : 2.11 seems much better (Message 5138)
Posted 10 Mar 2008 by Yeti
Post:
Just checked a little bit with 2.11; it seems to be fine again :-))

On those machines, where I tested the last days, all seems to be fine with 2.11 and, until now, 2.11 seems to suspend correcty !

6) Forums : Technical Support : CAMB 2.10 (Message 5119)
Posted 9 Mar 2008 by Yeti
Post:
Meanwhile I got the same warnings from my remote server control, so I had to abort the 2.10 WUs.

Sorry :-(
7) Forums : Technical Support : CAMB 2.10 (Message 5117)
Posted 9 Mar 2008 by Yeti
Post:
Just checked 2.10 on my machines with following results:

  • Suspend is still not working
  • HD-Activity seems to be a little better, but not much
  • In Task-Manager I can watch CAMB bouncing up and down using the processor; on BOINCView I see a CPU-Efficiency from 0.4 to 0.6; it should be 0.9 up to 1.0
  • I logged on one of my servers running 2.10; it was very sluggish and not really responsible as it should.


Sorry, but 2.10 is still not good

8) Forums : Technical Support : CAMB 2.08/2.09 not suspending (Message 5094)
Posted 9 Mar 2008 by Yeti
Post:

As I said, I would have to say it is something specific to your configuration... ;-) I believe I saw some musings about L2 cache sizes. Might be that...as I have 1MB L2 and your MP2600 system has 512K total...


Sorry, but I don\'t think so. I had it on machines with double-XEONs, RAID-5 Controller, enough memory (8 GB), Win2003 Server x64, ...

You can take a look at one of this machines at: http://www.cosmologyathome.org/show_host_detail.php?hostid=1336

Yeti
9) Forums : Technical Support : CAMB 2.08/2.09 not suspending (Message 5081)
Posted 8 Mar 2008 by Yeti
Post:
Similar here; I received a lot of errors of my server-remote-watches.

I have to set 2.09 to \"No new work\" until hopefully 2.10 will fix the problem
10) Forums : Wish list : Switch on the mail-component (Message 5067)
Posted 8 Mar 2008 by Yeti
Post:
Please, switch on the mail-component of the server. It is a pain, always to have to come to the website to check wheather there is an answer in the forum, or a new version wich solves problems ...
11) Forums : Technical Support : CAMB 2.08/2.09 not suspending (Message 5065)
Posted 8 Mar 2008 by Yeti
Post:
Just saw that 2.09 is out, but, unfortenatly it doesn\'t solve the suspend-problem
12) Forums : Technical Support : 2.08 error: too many exits (Message 5054)
Posted 7 Mar 2008 by Yeti
Post:
<core_client_version>5.10.28</core_client_version>
<![CDATA[
<message>
too many exit(0)s
</message>
<stderr_txt>

</stderr_txt>
]]>

http://www.cosmologyathome.org/result.php?resultid=3572610

13) Forums : Technical Support : Missing Mail Notification (Message 5050)
Posted 6 Mar 2008 by Yeti
Post:
Just discovered, that I didn\'t receive mail-Notifications about new posts in threads.

For example I have activated mail notification for this thread: http://www.cosmologyathome.org/forum_thread.php?id=399

but I didn\'t receive a mail.

Oh, it can not be a Spam-Filter; I use my own e-mail-server and I am the master about spam and pishing filters, but there were no messages from cosmology@home.

Yeti
14) Forums : Technical Support : CAMB 2.08/2.09 not suspending (Message 5041)
Posted 6 Mar 2008 by Yeti
Post:
Don\'t know if it helps to know but CAMB 2.07 is stopping normal if I stop the boinc-client, even after ignoring the suspend command.

Yeti
15) Forums : Technical Support : CAMB 2.08/2.09 not suspending (Message 5040)
Posted 6 Mar 2008 by Yeti
Post:
It seems to be really the reason of CAMB 2.07. See this log:

06/03/2008 12:39:10||Suspending computation - user request
06/03/2008 12:39:10||[app_msg_send] sent <suspend/> to wu_030208_141149_1_1
06/03/2008 12:39:10|Cosmology@Home|[task_debug] task_state=SUSPENDED for wu_030208_141149_1_1 from suspend

06/03/2008 12:39:10||[app_msg_send] sent <suspend/> to 11oc06aa.18571.544210.14.10.52_2
06/03/2008 12:39:10|SETI@home Beta Test|[task_debug] task_state=SUSPENDED for 11oc06aa.18571.544210.14.10.52_2 from suspend
06/03/2008 12:39:10||[app_msg_receive] got msg from slot 1: <current_cpu_time>6.108843158700001e+003</current_cpu_time><checkpoint_cpu_time>5.593930658000000e+003</checkpoint_cpu_time><fraction_done>0.38206798</fraction_done>
06/03/2008 12:39:10||[app_msg_receive] got msg from slot 3: <current_cpu_time>6.664206e+002</current_cpu_time><checkpoint_cpu_time>5.978738e+002</checkpoint_cpu_time><fraction_done>2.349387e-001</fraction_done><fpops_cumulative>3.467713e+012</fpops_cumulative>
16) Forums : Technical Support : CAMB 2.08/2.09 not suspending (Message 5037)
Posted 6 Mar 2008 by Yeti
Post:
I was just testing the latest Alpha-Client 5.10.45 and watched, that camb 2.07 didn\'t suspend as it should.

At the moment it is not clear wheather this is related to BOINC 5.10.45 or CAMB 2.07, but we should keep an eye on it.

Yeti
17) Forums : Technical Support : CAMB 2.02 looses contact with BOINC-Core-Client (Message 3767)
Posted 1 Nov 2007 by Yeti
Post:
http://www.cosmologyathome.org/forum_thread.php?id=21&nowrap=true#3756


Great, I will test it :-))

18) Forums : Technical Support : CAMB 2.02 looses contact with BOINC-Core-Client (Message 3753)
Posted 31 Oct 2007 by Yeti
Post:
Scott,

should I test wheather 2.03 has the same behavior ?

Yeti
19) Forums : Technical Support : CAMB 2.02 looses contact with BOINC-Core-Client (Message 3709)
Posted 30 Oct 2007 by Yeti
Post:

At least it only finishes tasks and doesn't start new ones...

HM, but if the CoreClient only switches between tasks, you have more activ running processes than processors / cores, this results in fighting for resources between the different tasks and this makes the machine sluggish and un-useable

Sorry, but this is not really funny

Yeti
20) Forums : Technical Support : CAMB 2.02 looses contact with BOINC-Core-Client (Message 3699)
Posted 30 Oct 2007 by Yeti
Post:
I see on several of my boxes that CAMB 2.02 doesn't follow the "commands" from the Core-Client (5.10.20)

So, if I set BOINC to suspend, it says suspended; all applications stop crunching, except CAMB 2.02

Or, I stopped the whole BOINC-service, all applications stop crunching and are removed from memory, again except CAMB 2.02. It is still in memory and crunching on.

This doesn't happen immediatly, but after some (longer) time of activity it happens.

Until this is solved, I will have to set NoNewWork :-(

Yeti


Next 20