Message boards :
Number crunching :
BOINC 6.10.43 version released
Message board moderation
Author | Message |
---|---|
[AF>france>pas-de-calais]symaski62 Send message Joined: 12 Aug 05 Posts: 258 Credit: 100,548 RAC: 0 |
http://boinc.berkeley.edu/dev/forum_thread.php?id=2518&nowrap=true#31673 BOINC 6.10.43 released for testing for Windows and Windows x64, Linux and Linux x64 BOINC 6.10.43 released for testing for Macintosh Rom Walton wrote: Howdy Folks, Change Log: 6.10.37/38: - MGR: Save & restore size information of properties dialogs separately for project and task property dialogs, also save and restore dialog positions on Mac. - Mac: explicitly specify compiler as GCC 4.0 instead of system default in build settings to allow building with XCode 3.2 on OS 10.6 as well as XCode 3.1 on OS 10.5.8. - MGR: Instead of alternating gray and white backgrounds in lists, create CBOINCListCtrl with wxLC_HRULES flag. This avoids theme color conflicts with our backgrounds. It also eliminates the need to set item attributes, since the default attribute setting already uses theme colors. - MGR: Remove some hacks to deal with early wxGTK bugs which have since been fixed. - MGR: Restore wxGTK hacks, bug is still alive and well. - client: revisit the domino-effect preemption problem. Removed my changes of 19 Jan 2010, which didn't work. Added new mechanism: keep track of whether a job J has ever run in EDF. If so, and if another job of the same project and resource type as J is marked as deadline miss, then mark J as deadline miss, so that it won't get preempted. - client: if a GPU job is blocked on available mem, don't fetch more jobs for that resource type. - MGR: Improve performance when reducing number of rows in lists (as when selecting "Show active tasks") by calling ClearSelections() and SetItemCount() instead of repeatedly calling DeleteItem(). - MGR: Fix a bug which caused unnecessary demand RPCs on some platforms: set RPC time stamps to 1 rather than 0 in RefreshRPCs() so a not to trigger initialization code. - client: don't suspend non-CPU-intensive jobs because of CPU load. - MGR: Prevent flicker and lack of display by using the regular tooltip for the Project List control on Windows. - client: if suspending apps because of CPU benchmarks, leave them in memory. - MGR: Fix to my previous checkin: RefreshRPCs() shouldn't change time stamp if it was zero, as this is a special vslue to indicate the RPC has never been called. - Remove BOINC_RCSID tags from source files, we are doing branching and tagging properly. - client: add missing CPU scheduler code. - client: fix formatting in app_control.cpp - MGR: fix build break. - Mac Sandbox: Fix bug in my changes of 26 Jan 2010 to set projects directory and slots directory to group boinc_project, not boinc_master. - client: in computing non-BOINC CPU time, exclude any process whose executable includes "boinc", case-insensitive. Fix problem with BoincTasks.exe NOTE: this affects only Win and Linux; Mac already had case-insensitive comparison. 6.10.39: - fix bugs in strcasestr(), which apparently had never been tested. - Define HAVE_ALLOCA in boinc_win.h so that any component using strcasestr in str_util.cpp uses stack allocations instead of more expensive heap allocations. - Move remaining HAVE_* defines from project files to boinc_win.h 6.10.40: - MGR: Allow separate compile-time choice of rules and / or alternating gray and white background stripes in lists by defining BASEVIEW_RULES and BASEVIEW_STRIPES (in BOINCBaseView.h); set each to 1 to enable or 0 to disable; currently both are set to 1 for both stripes and rules. - MGR: Change previous commit to strips only for the next build. Things look wonky with both stripes and rules around the margins. - client (and anything else using MFILE): Win efficiency fix. Shockingly, realloc() wasn't doing exponential growth. So create realloc_aux() that does. 6.10.41: - unix compile fix - MGR: Derive messages tab colors from base class colors. 6.10.42: - MGR: Switch background color for the list view stripes back to the original color (247, 247, 247). 6.10.43: - MGR: Deconflict menu IDs ---------------------------------------------- Update 06/04/2010 13:36:46 A new version of BOINC (6.10.43) is available for your computer 06/04/2010 13:36:46 Visit http://boinc.berkeley.edu/download.php to get it. SETI@Home Informational message -9 result_overflow with a general handicap of 80% and it makes much d' efforts for the community and s' expimer, thank you d' to be understanding. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
|
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
A reminder to Linux users to drain your cache or you'll lose all your current work In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Not sure what warrants that warning, but that usually only happens when you install BOINC in a different place than you did last time (thus moving your data directory) or when you inadvertently go back from a 64bit version to a 32bit version (which use different applications on Linux). Check the version you run now against the name of the version you downloaded. The download site reads what OS you have (Windows, Linux, OS X) but unless you use Internet Explorer, it cannot easily determine the bit-rate of the OS. In the case of Linux, the name has _x86_64 in it for the 64bit version, _i868 for the 32bit version. In the case of Windows, the name has _x86_64 in it for the 64bit version, _intelx86 for the 32bit version. |
Urs Echternacht Send message Joined: 15 May 99 Posts: 692 Credit: 135,197,781 RAC: 211 |
... greened numbers were meant. _\|/_ U r s |
Dean Jones Send message Joined: 9 Sep 00 Posts: 6 Credit: 2,006,041 RAC: 0 |
MacBook Pro, 4 GB, OS X 10.6.3, NVIDIA GeForce 9600M GT with 512 MB, latest CUDA drivers from nVidia (per url in the readme file). I installed 6.10.43 today. A number of "problems" have cropped up: 1. It does not find any usable gpus. 2. It can't resolve the host name. 3. None of the gpu related management options appear in any of the menus. Suggestions please. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
2. It can't resolve the host name. Please install 6.10.44 (development version). Its main fix is: - Mac: Build with c-ares 1.6.0 instead of c-ares 1.7.0, because the newer c-ares has problems resolving host names on OS 10.6 with default settings when used with AT&T U-Verse 2Wire gateway routers and Airport. GPU not found problems is normally a drivers problem. Make sure you installed the correct CUDA 3.0 ones. You won't find any GPU related management options in the menus when the GPUs aren't detected. Also make sure you didn't set <no_gpus> in a cc_config.xml file in a gray past. ;-) @Urs, thanks. :-) |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
BOINC on mandriva fails to recognize the existing work every time I upgrade. I upgrade infrequently because its a hassle to wait out the cache In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Upgrade how? Through Synaptic Packet Manager or do you use the Berkeley Installer? Is your Mandriva 32bit or 64bit? Is your BOINC 32bit or 64bit? Have you asked other Mandriva users about their experience? when you last had this problem, which version did you upgrade from and to which one? But most of all, why then the warning for all Linux users? Do you know how many different *nix versions are out there? I don't. ;-) |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
manually through Konsole as instructed from the BOINC page. Mandriva 64 BOINC 64. Mandriva has their own auto install BOINC which the last I checked was 6.6.1 so there wasnt any point in installing a BOINC that is older than my current version. The last version I attempted was the 6.10.36, I think. Whichever version it was it got pulled back because there was something wrong with it. Needless to say it didn't install correctly. So I had to backoff to my current version. In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
gomeyer Send message Joined: 21 May 99 Posts: 488 Credit: 50,370,425 RAC: 0 |
Is anyone else having trouble managing a remote computer after upgrading it to 6.10.43? This host used to be visible/manageable from another computer using both the 6.10.18 Manager and using BoincView 1.4.2, but not after the upgrade. The remote_hosts.cfg and gui_rpc_auth.cfg files did not change, and I can see both BOINC folders in Windows Explorer from the other computer. (After sharing them) But BoincView says there is no Client responding to port 31416 and BoincManager just shows blank displays on all tabs except Disk and that shows zero bytes. (to be clear, that is trying to see remote 6.10.43 from local 6.10.18) Is this new version still using port 31416? Did something else change that would cause this? The remote host is running Win 7 64, I installed boinc_6.10.43_windows_x86_64.exe, and all attempts are on a home network. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Is anyone else having trouble managing a remote computer after upgrading it to 6.10.43? I just tested that with my remote computer, which is still on 6.10.36 and I see the same thing. I'll forward this to the developers. |
gomeyer Send message Joined: 21 May 99 Posts: 488 Credit: 50,370,425 RAC: 0 |
Is anyone else having trouble managing a remote computer after upgrading it to 6.10.43? Thanks Ageless. This could be a bit of a show stopper for some people. |
dnolan Send message Joined: 30 Aug 01 Posts: 1228 Credit: 47,779,411 RAC: 32 |
Is anyone else having trouble managing a remote computer after upgrading it to 6.10.43? It's working for me, but the system I run BV from is 6.10.43 (other systems are not). -Dave |
ML1 Send message Joined: 25 Nov 01 Posts: 20140 Credit: 7,508,002 RAC: 20 |
manually through Konsole as instructed from the BOINC page. OK, so you get a directory called "BOINC" created for wherever it is you run the downloaded shell extractor file? Mandriva 64 BOINC 64. Mandriva has their own auto install BOINC which the last I checked was 6.6.1 so there wasnt any point in installing a BOINC that is older than my current version. Which version of Mandriva? For example, the latest is called "2010.0". They're just trying the first beta version of 2010.1 over in Mandriva cooker. (I guess don't try that one yet ;-) ) As a check, what does: uname -a give? The last version I attempted was the 6.10.36, I think. Whichever version it was it got pulled back because there was something wrong with it. Needless to say it didn't install correctly. So I had to backoff to my current version. You can run 'manually' via the BOINC directory. Or you can do the Mandriva service install and then as root (if you know what you're doing) just update with the files the Berkeley download gives in BOINC. I have a script somewhere for doing that... I've done many an update and haven't lost any WUs recently. Hope that helps. Happy crunchin', Martin See new freedom: Mageia Linux Take a look for yourself: Linux Format The Future is what We all make IT (GPLv3) |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
It works the other way around. I can connect to the client 6.10.36 from my localhost with 6.10.45 (alpha). Just not from the 6.10.36 to the 6.10.45 Which would make it believe it's not a port problem. |
zoom3+1=4 Send message Joined: 30 Nov 03 Posts: 65709 Credit: 55,293,173 RAC: 49 |
It works the other way around. I can connect to the client 6.10.36 from my localhost with 6.10.45 (alpha). Just not from the 6.10.36 to the 6.10.45 Yeah I'm running 6.10.45 on XP x64 and BV sees what It did under 6.10.43, Which is everything, Sure It's only 1 PC, But still, BV sees the port. :D The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's |
Joseph Stateson Send message Joined: 27 May 99 Posts: 309 Credit: 70,759,933 RAC: 3 |
I believe this is a firewall problem. I can connect from linux 6.10.17 to any linux (6.10.43, 6.10.44) or windows xp (6.10.43) All of the above were launched using -allow_remote_gui_rpc I can connect to all of my vista 64 and win 7 systems (6.10.43) if I explicitly put the ip address of the 6.10.17 system into \ProgramData\Boinc\remote_hosts.cfg *AND* I either turn off the firewall or configure the exclusion properly. Excluding "boinc.exe" with no path to the executable will not work. Excluding "\Program Files (x86)\boinc\boinc.exe" will not work if you are running the 64 bit boinc. I have no idea how that 32 bit location got into my firewall. ======turn off the firewall and try the following==== From the cmd prompt of the windows system with the old boinc version, or from the terminal prompt of the older linux system (what.ever is the ip address of the newer system) telnet 192.168.what.ever 31416 if you see "unable to connect to the remote .." then you got a firewall problem if you see a bunch of strange characters and cant seem to exit then you connected but are not authorized |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
Is anyone else having trouble managing a remote computer after upgrading it to 6.10.43? I have BoincView running on an old machine witn BOINC v6.10.13 (no point having BV wasting cycles on a fast machine....) I have three CUDA machines downstairs which I regularly throw new test versions of BOINC onto. Currently, they've got v6.10.36, v6.10.43, and v6.10.45 loaded and running. I haven't had any problems with remote viewing or controlling any of the new BOINCs with this rig. I think it would be quite a good mine-canary if they do break anything - you can be sure I'd let them know :-) |
gomeyer Send message Joined: 21 May 99 Posts: 488 Credit: 50,370,425 RAC: 0 |
Well, I don't have telnet available as a DOS command with this Vista 32 machine, but I did double check the firewall on the Windows 7 remote host and for some reason the machine was conneted as a "Public" network instead of "Private" as I had it originally. The Windows firewall was indeed blocking it. Wierd: no idea why or how that happened. As soon as I changed the network connection back to "Home or work (Private) Networks" everything works normally even with Windows firewall enabled. Good catch BeemerBiker, thanks! Now I just have to try to figure out why the network connection changed. It was working OK before the upgrade and I swear I wasn't anywhere near those settings. I did pull the network cable while upgrading so I'll blame the switch on that for now and chalk it up to a learning experience on Windows 7. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.