Posts by -ShEm-

1) Message boards : Number crunching : MW@H vs BOINC (Message 30010) Posted 31 Aug 2009 by -ShEm- Post: 8/30/2009 10:47:09 PM Contacting account manager at http://bam.boincstats.com/ 8/30/2009 10:47:10 PM Account manager: BAM! User-ID: 3911 8/30/2009 10:47:10 PM Account manager: BAM! Host-ID: 161313 8/30/2009 10:47:10 PM Account manager: This host connected 275 times to BAM! 8/30/2009 10:47:10 PM Account manager contact succeeded 8/30/2009 10:47:10 PM Milkyway@home Resetting project 8/30/2009 10:47:11 PM Milkyway@home Detaching from project Regards Art From where are you attaching to MW@h? From BOINC Manager on the computer or from BAM!? If you don't attach it to MW@h from BAM!, BAM! will detach MW@h at any contact your BOINC make to BAM!. That will also be the case for any other projects you attach to from BOINC instead of BAM! Newer versions of BOINC no longer allows you to attach to a project from BOINC Manager if that host is using an account manager like BAM!.
2) Message boards : Number crunching : server crash (July 29) (Message 28595) Posted 30 Jul 2009 by -ShEm- Post: um ... not everything OK, I hope it's just the BOINC cache or an index : A bunch of tasks from earlier today have been marked "no longer usable" and exactly those are affected and my PC's task list was empty. My user task list was _not_ empty, but if I opened the older tasks, the PC they are attached to is not mine, e.g. : http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=63855306 from my task list is attached to http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=73028 belonging to DrMASH Tasks that I downloaded just now have the correct host entry. Similar for me (tasks listed for another host belonging to another user)...
3) Message boards : Number crunching : Laptop rebooting by itshelf (Message 18963) Posted 16 Apr 2009 by -ShEm- Post: Yeah, I'd say it's Windows updates, since my wife's Vista laptop did the same last night after updating Windows yesterday afternoon. And it's not running MilkyWay. Also it has happened on previous updates some months ago...
4) Message boards : Number crunching : Vote for the MilkyWay favicon! (Message 8207) Posted 6 Jan 2009 by -ShEm- Post: I'm not a number! I'm a... oops, sorry wrong forum :) Number 3!
5) Message boards : Number crunching : Wu errors! (Message 7570) Posted 9 Dec 2008 by -ShEm- Post: Had an error code -131 on Win XP Px64, which according to The Boinc FAQ Service is the output file is bigger than set by project, so file isn't uploaded... see this WU-result
6) Message boards : Number crunching : Could We Get a Paper On This? (Message 3577) Posted 29 May 2008 by -ShEm- Post: Seems you missed it somehow: The project is still an alpha-project, so problems should be expected rather than being a surprise.
7) Message boards : Number crunching : Weak Account Key (Message 3517) Posted 25 May 2008 by -ShEm- Post: hmmm...it seems our scheduler isn't set up to handle it. i guess it didn't get updated with the server upgrade. i'll look into it for you Any news on this? Still getting Message from server: Invalid or missing account key. Visit this project's web site to get an account key. when trying to use weak account key... Would like to be able to use it, though it's not that important ;)
8) Message boards : Number crunching : Weak Account Key (Message 3019) Posted 4 Apr 2008 by -ShEm- Post: Did you follow this guide? http://boinc.berkeley.edu/trac/wiki/WeakAuth Also, this change requires a scheduler update which i'm not sure actually happened. So if anyone else wants to give this a try and tell me what happens for them i would be greatly obliged. Yeah, followed that guide though I didn't know about it, but I knew where to put the key ;) As Kathryn said, simply replacing back to normal account key makes it work again. As I saw W.A.K. available on my account page, I wanted to use it on a remote pc for security reasons :)
9) Message boards : Number crunching : Weak Account Key (Message 2980) Posted 3 Apr 2008 by -ShEm- Post: The new server software here supports 'Weak Account Key', but when I use it and try to connect I get "No or invalid account key" (or similar), so have to go back to using the normal account key... and yes, I did make sure I didn't make any typing mistakes (copy'n'pasted) and checked after that ;) Any way we could get this to work here? It works on SETI@home...
10) Message boards : Number crunching : application v1.21/v1.22 errors/memory leaks/crashes here (Message 2189) Posted 12 Mar 2008 by -ShEm- Post: astronomy_1.21_amd64-unknown-freebsd astronomy_1.21_i386-unknown-freebsd HTH ;) Yup, thanks :D
11) Message boards : Number crunching : application v1.21/v1.22 errors/memory leaks/crashes here (Message 2186) Posted 12 Mar 2008 by -ShEm- Post: ... I should mention this particular host runs with FreeBSD 7.0-Release, with boinc compiled with platform i686-pc-linux-gnu (seems projects don't agree upon which platform-response to support on FreeBSD). Also running S@H and Cosmology with no problems. Why don't you run the native freebsd binaries instead ? Should be easy to set it up using an app_info.xml file. If you need help with that, let me know. Yeah, wanted to do that, but dunno where to download the binaries from... :( app_info.xml I can do myself ;)
12) Message boards : Number crunching : application v1.21/v1.22 errors/memory leaks/crashes here (Message 2165) Posted 11 Mar 2008 by -ShEm- Post: Just reporting I had 4 workunits "freeze" on 1 host with Linux 32bit v1.22. A restart of boinc in all cases solved the freezes. Other WUs (and projects) were crunched in between the freezes. One of them was (forgot to take note of the other 3): http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=4988091 One thing I noticed at all 4 WUs was that running time was app. 5 seconds longer in boinc than other WUs (8m40s vs 8m35s), but looking at the above WU shows reported CPU-time at app 7m57s (and I see 3 other WUs with same short CPU-time, so it's likely those were the other frozen ones). I should mention this particular host runs with FreeBSD 7.0-Release, with boinc compiled with platform i686-pc-linux-gnu (seems projects don't agree upon which platform-response to support on FreeBSD). Also running S@H and Cosmology with no problems. Have 2 hosts with WinXP Pro running v1.22 but have had no freezing on those.