Posts by ChertseyAl

1) Message boards : Number crunching : Cannot get new tasks on one of my AMD Rigs 4P (Message 1121) Posted 17 Sep 2014 by ChertseyAl Post: Al: When you get a chance, can you try again and see if it works for you? Thanks! Just tried: 17/09/14 06:52:50\|NumberFields@home\|Sending scheduler request: Requested by user. Requesting 95040 seconds of work, reporting 0 completed tasks 17/09/14 06:52:56\|NumberFields@home\|Scheduler request succeeded: got 2 new tasks 17/09/14 06:52:59\|NumberFields@home\|Started download of sf3_DS-13x267_Grp25113of25600.dat 17/09/14 06:52:59\|NumberFields@home\|Started download of sf3_DS-13x267_Grp25030of25600.dat 17/09/14 06:53:00\|NumberFields@home\|Finished download of sf3_DS-13x267_Grp25113of25600.dat 17/09/14 06:53:00\|NumberFields@home\|Finished download of sf3_DS-13x267_Grp25030of25600.dat 17/09/14 06:53:02\|NumberFields@home\|Starting wu_sf3_DS-13x267_Grp25113of25600_0 17/09/14 06:53:02\|NumberFields@home\|Starting task wu_sf3_DS-13x267_Grp25113of25600_0 using GetDecics version 102 Hurrah! I'll switch the rest of my hosts to this project later and see how it goes :) Cheers, Al.
2) Message boards : Number crunching : Cannot get new tasks on one of my AMD Rigs 4P (Message 1117) Posted 16 Sep 2014 by ChertseyAl Post: Tried that before, I'll try again ... 16/09/14 06:59:30\|NumberFields@home\|Sending scheduler request: Requested by user. Requesting 95040 seconds of work, reporting 0 completed tasks 16/09/14 06:59:35\|NumberFields@home\|Scheduler request succeeded: got 0 new tasks 16/09/14 06:59:35\|NumberFields@home\|Message from server: No tasks sent 16/09/14 06:59:35\|NumberFields@home\|Message from server: No tasks are available for Get Decic Fields Nope. It's not just one machine either, it's (I think) all but one of them.
3) Message boards : Number crunching : Cannot get new tasks on one of my AMD Rigs 4P (Message 1115) Posted 15 Sep 2014 by ChertseyAl Post: I haven't been able to get any work for weeks now, except for on just one machine. I always get something like this: 15/09/14 14:41:14\|NumberFields@home\|Sending scheduler request: To fetch work. Requesting 446 seconds of work, reporting 0 completed tasks 15/09/14 14:41:19\|NumberFields@home\|Scheduler request succeeded: got 0 new tasks 15/09/14 14:41:19\|NumberFields@home\|Message from server: No tasks sent 15/09/14 14:41:19\|NumberFields@home\|Message from server: No tasks are available for Get Decic Fields Actually, it's probably longer than that. I've tried detaching/reattaching but it makes no difference. Perhaps the server is refusing to send work to older client versions. Shame. I was planning on crunching my way up to the 1M credit level.
4) Message boards : Number crunching : Can't report completed work (Message 858) Posted 6 May 2013 by ChertseyAl Post: No, didn't reattach. I was going to wait until nearer the changeover, run dry, report and detach then. But I only check the forums once a day, didn't see the message, so missed the chance to report etc as it had all changed in less than a day :( Oh well. Cheers, Al.
5) Message boards : Number crunching : Can't report completed work (Message 856) Posted 6 May 2013 by ChertseyAl Post: Under the projects tab, click properties and look at the master URL. If it's "numberfields.asu.edu", then you should be good. But you will need to shut down the client and restart it. Note that if you shut down the manager, the client usually continues to run in the background (at least it does for me). I kill the client by right clicking the "show hidden icons" button on the task bar, right clicking the boinc client icon, and then selecting exit. Or you can kill it directly from task manager, or reboot the computer. Hope that helps. Only later versions of BOINC allow you to look at project properties. None that I run do sadly, so I have to edit the file by hand. I shut down BOINC Manager, which in my case does shut down the client (check in task manager also that nothing is still running). I edit client_state.xml, changing all occurences of stat.la.asu.edu to numberfields.asu.edu, save file, exit editor, check file has in fact been updated. It has. Start BOINC Manager which starts the client. Immediately I see ... 06/05/13 09:07:13\|NumberFields@home\|Fetching scheduler list ... in the messages tab, but nothing happens. If I check client_state.xml, it's gone back to the old URL. Must be some weird caching going on. Meanwhile I've lost typically 40-50 hours of crunching. Anyway, I've given up, too much like hard work to fix all of my machines :) Cheers, Al.
6) Message boards : Number crunching : Can't report completed work (Message 853) Posted 5 May 2013 by ChertseyAl Post: Oh, editing client_state.xml doesn't work - Just lost a whole bunch of work as a result. Oh well, I'm out. Cheers, Al.
7) Message boards : Number crunching : Can't report completed work (Message 852) Posted 5 May 2013 by ChertseyAl Post: Since the URL change, I'm not able to report 100s of hours of completed work. I've tried shutting down and restarting BOINC, but I just get: 05/05/2013 22:35:47\|NumberFields@home\|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 2 completed tasks 05/05/2013 22:35:52\|NumberFields@home\|Scheduler request failed: Couldn't connect to server If I reset the project or detach and reattach I'm going to lose a lot of crunching time. I thought the old and news URLs were going to run in parallel for a while? Cheers, Al.
8) Message boards : Number crunching : Long Wu´s and short wu´s, but why? (Message 812) Posted 26 Mar 2013 by ChertseyAl Post: I haven't heard from you in a while. Good to see you're still around. I'm always around on BOINC. Been clocking up milestones and badges all over the place, as was my way of BOINCing. Decided this year just to concentrate on a few projects that I like and totally drop the dull ones. So, I'll be around here for a while, got a 500k credit milestone and an upgraded badge to get at least :) Cheers, Al. p.s. Still feeding the dinosaurs a mixed diet of WU types. Think I'll go for the 'ordinary' ones only shortly as they are priority.
9) Message boards : Number crunching : Long Wu´s and short wu´s, but why? (Message 810) Posted 25 Mar 2013 by ChertseyAl Post: Sort of related question ... Which type of WU is most useful to the project if any? At the moment I run both bounded and 'ordinary', I assume unbounded, ones, but would happily run just one type if it was better for the project :) Oh, regarding length, for the OP, noticed the the bounded ones always run for some time, albeit short, but at least they run for a while. The unbounded ones either last less than a second of half a day on my dinosaur machines. Cheers, Al.
10) Message boards : Number crunching : 32 bit linux - process got signal 11 (Message 614) Posted 16 Apr 2012 by ChertseyAl Post: Yeah, I was aware that it was a segmentation error - I've seen numerous threads on other project fora about it ;) Not worth me trying to run the unbounded app on such a slow machine :( Hopefully someone else can try out the bounded app and have more success than me, or at least be able to debug it if it fails for them. Cheers, Al.
11) Message boards : News : To all Linux users: (Message 611) Posted 16 Apr 2012 by ChertseyAl Post: Not working for me ... Started a new thread for 32 bit linux problems in a more relevant forum: http://stat.la.asu.edu/NumberFields/forum_thread.php?id=68 Cheers, Al.
12) Message boards : Number crunching : 32 bit linux - process got signal 11 (Message 610) Posted 16 Apr 2012 by ChertseyAl Post: The 32 bit linux version isn't working for me, all tasks die with "process got signal 11". An example WU: http://stat.la.asu.edu/NumberFields/result.php?resultid=904465 <core_client_version>5.10.45</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> </stderr_txt> ]]> Not enough of a linux expert to offer much help. Maybe I got the 64-bit verion or something? Cheers, Al.
13) Message boards : Number crunching : Massive drop of credits per CPU hour (Message 599) Posted 9 Apr 2012 by ChertseyAl Post: Yes, the credit problem was fixed several months ago. I have had no complaints since then. No complaints here either - Predictable credit on every WU so far :) It's a pity that the estimated runtimes of the bounded WUs are way too high, and actual runtimes are so variable, makes it difficult to keep full caches. At least it's worth crunching them now though :) Cheers, Al.
14) Message boards : Number crunching : Massive drop of credits per CPU hour (Message 583) Posted 23 Mar 2012 by ChertseyAl Post: be careful not to take the real long WU's for the slow hosts! Yeah, I'll go for bounded ones initially :) Al.
15) Message boards : Number crunching : Massive drop of credits per CPU hour (Message 581) Posted 23 Mar 2012 by ChertseyAl Post: I went ahead and implemented the "--credit_from_runtime X" option in the validator. Now we wait to see if this fixes the problem with CreditNew... Does this mean that my 5.10.45 clients will now get sensible credit? If so, I'll start crunching this project again :) Al.
16) Message boards : Number crunching : 504 Hr work time!? (Message 405) Posted 26 Nov 2011 by ChertseyAl Post: The 2 that I have/had (on VERY slow hosts) jumped to 50% very quickly and started climbing steadily. One had got to 80-something percent and suddenly finished after around 39 hours - Got decent credit for it too, about time, I thought I was jinxed ;) The other is 71% after 45 hours, and I'm guessing it will finish at around 60 hours. Only using these old hosts for this project as they are my junk test machines with BOINC 6.10.30 and 6.12.32 which I don't want on any other machines, and I don't think this project works properly (regarding Run Time) with older versions. Al.
17) Message boards : Number crunching : Massive drop of credits per CPU hour (Message 387) Posted 22 Nov 2011 by ChertseyAl Post: Oh yeah, sample size was 232 WUs. Removed 2 from my set of 234 as they were <1 second and didn't really fit in with anything (rounding errors etc). Also, thumbs up to @Senilix for spotting the underlying problem :) Al.
18) Message boards : Number crunching : Massive drop of credits per CPU hour (Message 386) Posted 22 Nov 2011 by ChertseyAl Post: It's not quite as simple as it seems though. I've grabbed all of my results and put them in a spreadsheet so that I can sort/filter them. Observations: 1) Those with spectacularly poor credit have a zero run time, those are four V2.02 and one V2.03 (5 WUs) 2) Of those with a zero run time (21 WUs), 5 have low credit (see above), 1 has 'sensible' credit, 10 have BIG credit and 5 have OMFG credit. All of these are V2.02 but one. Seems that zero run time is responsible for random credit rather than CreditNew (can't believe I'm saying that!). 3) CreditNew seems to have actually settled down. Credits were higher when I started around 17th/18th and seem to level out a day of so later. Maybe CreditNew works? (stabs self in eye with fork). Later WUs with non-zero run times seem to give pretty constitent credit (pinches self). I can, as yet see no other patterns. Would love to able to predict if my current long-runners are going to be winners or losers in the lottery :) Al.
19) Message boards : Number crunching : Massive drop of credits per CPU hour (Message 384) Posted 22 Nov 2011 by ChertseyAl Post: older boinc-clients to not ptoperly report run time and cpu time. looks like creditnew has fallen into another pit dug out in boinc-central.. Yes, I got bitten on the a4se by another project like that. Hmmm. I'll screen-scrape all of my results into Excel and look for the pattern. One thing's for sure though, I'm not installing BOINC 6.x on anything else. I have to use it on a couple of machines and I hate it :( Al.
20) Message boards : Number crunching : Massive drop of credits per CPU hour (Message 382) Posted 22 Nov 2011 by ChertseyAl Post: All of your WUs with improper (too high/too low) credit have one thing in common: all show up with a run time of 0.00 sec. Ah, I hadn't made that connection. It's odd that some WUs show zero, others don't. I've used a dozen different hosts, but ATM I'm using 7 similar ones all running BOINC 5.10.45. I'll see if I can find out what's going on, though I suspect it is the WUs themsleves rather than the hosts. Thanks for the heads-up :) Al.

Next 20