Message boards :
News :
SETI@home Version 7 has been released
Message board moderation
Previous · 1 . . . 10 · 11 · 12 · 13 · 14 · 15 · 16 . . . 19 · Next
Author | Message |
---|---|
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
I have two machines that have remained on stock applications. Neither of these have exhibited the issues of constantly requesting more work but not getting any that you describe. Please head over to NC and start a dedicated thread. The is a very high overlap between the Lunatics team (especially the installer crew) and the people commited to chasing boinc bugs and generally manning the help desk. While we are busy trying to get an installer out we can't chase boinc bugs. Please open a dedicated NC thread for any boinc based problems and we'll look into it when we can remove the asbestos suits. A person who won't read has no advantage over one who can't read. (Mark Twain) |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
Much ado about nothing. I am running SETI@home v7 on a Linux box, Astropulse V6 by Lunatics on another Linux box and SETI@home V6.03 by Dotsch on a Solaris Virtual Machine on the second Linux box, which houses also a BOINC_VM Virtual Machine. The two don't interfere except at start time, when I have to suspend Solaris to let BOINC_VM start, for unknown reasons. Tullio |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
I have two machines that have remained on stock applications. Neither of these have exhibited the issues of constantly requesting more work that you describe. I also have not rebooted either machine since the v7 application's release on Wednesday of last week. One is not processing GPU tasks and is on BOINC v7.0.64. The other is processing nVidia GPU tasks and is on BOINC v7.0.28. Both machines are running Windows 7 x64. This seems to support the idea that this bug is unique to v7.0.64. Repeatability is key to tracking down a problem. So different (nVidia?) GPUs, different OSes, but all using the same BOINC version? I do think this is a BOINC bug, but I think the v6 AP to v7 processing is merely a coincidence, as each application does not know about each other. The individual science apps don't leave configuration information behind. In fact, any command line switches or configuration is handed to the science application via BOINC, which brings us right back to BOINC as the likely problem. BTW, it would seem to me that somebody on the SETI@home staff could simply peruse the download server logs to see if these "Not requesting tasks" work fetches have proliferated. That would be a lot more productive that trying to speculate here in the forums! (Although, from what I've seen, speculation is what forum posters enjoy most.) :) At over 500,000 computers, I don't know if I'd want to keep all of that logged on my servers if it were me. That should be logged on the client if anything, but I admit that I don't know the extent of the logging on the SETI@home servers. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
At over 500,000 computers, I don't know if I'd want to keep all of that logged on my servers if it were me. That should be logged on the client if anything, but I admit that I don't know the extent of the logging on the SETI@home servers. All server requests are logged, or are capable of being logged, on the server by BOINC. You can actually see the logs live on Einstein's and Albert's web pages - for the most recent single request only. David sometimes requests that an observation (and this would be a case in point) be repeated using the SETI project, because this is the only one where he routinely has direct access to the server logs. I don't think they're kept for very long, though. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
Thanks for clearing that up Richard. With that information, I suppose it would be easy for the Project Admins to look up the amount of work requests by clients to see how many of them are not getting work when requested to see if this is a widespread problem. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Please see the Announcement in number crunching: Updated Installers, v0.41 for Windows Available now These support the new SETI@home Version 7 tasks we've been discussing in this thread. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
It's morning again and I guess I'll squeeze in one last post on this "fetch work / not requesting tasks" issue and then it looks like I should make way for installer-related posts. One is not processing GPU tasks and is on BOINC v7.0.64. The other is processing nVidia GPU tasks and is on BOINC v7.0.28. Both machines are running Windows 7 x64. This seems to support the idea that this bug is unique to v7.0.64. Sounds reasonable. So different (nVidia?) GPUs, different OSes, but all using the same BOINC version? Yes, a GTX 550 ti, a GT 640, an 8600 GT, and an old GeForce 405; basically whatever the MB and power supply in each box would support. All are on BOINC v7.0.64 and all with the latest NVIDIA driver (314.22). At over 500,000 computers, I don't know if I'd want to keep all of that logged on my servers if it were me. That should be logged on the client if anything, but I admit that I don't know the extent of the logging on the SETI@home servers. Actually, regardless of the number of connected computers, I'd think it would be irresponsible to not have at least some level of logging in place. In any event, I see from a later post that there might be something available for the Admins to look at, if they choose to. And from my own final post last night: I think this machine will complete a v6 AP GPU task overnight, so it will be interesting to see if the loop returns tomorrow. Yes, the v6 AP task completed and NO, the loop did not start back up. So, my next observable milestone will probably be tonight when the machine which did resume looping runs another AP GPU task. As far as opening a thread in another forum goes, I'll leave that to anyone who's still actively experiencing the problem. I just started posting here in an attempt to be helpful to a couple of users who had seemed to experience the problem after I had seemingly found a way to get past it. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
At over 500,000 computers, I don't know if I'd want to keep all of that logged on my servers if it were me. That should be logged on the client if anything, but I admit that I don't know the extent of the logging on the SETI@home servers. Agreed that it would be irresponsible to not have at least some level of logging in place. I don't know that I would log all work requests though as I would think most of that information to be largely irrelevant to the science, and would consume too much storage space for what little insight it would provide. For reference, my company has 6,000+ computers and the server logs consume well over a Gigabyte per day. |
Phil Send message Joined: 19 Jun 99 Posts: 110 Credit: 4,545,588 RAC: 0 |
After I enabled V7 I could not even navigate any of my 3 browsers to Berkely university websites... much less the SETI@home. I had to format my drive and re-install windows because I even have a hunch about users in here now and their custom worms Terrible, aint it. My AVG said there is some woodworm infection in the basement, so I'm even having to buy a new house. |
gs Send message Joined: 18 May 99 Posts: 45 Credit: 5,412,660 RAC: 8 |
Its 4 pages long. Already forgotten, also the part of whining and the rest of what you wrote... I usually don't take advice from people slapping me... |
gs Send message Joined: 18 May 99 Posts: 45 Credit: 5,412,660 RAC: 8 |
Please see the Announcement in number crunching: Thank you very much, Richard. This is what I was looking for. Cheers! |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Much ado about nothing. I am running SETI@home v7 on a Linux box, Astropulse V6 by Lunatics on another Linux box and SETI@home V6.03 by Dotsch on a Solaris Virtual Machine on the second Linux box, which houses also a BOINC_VM Virtual Machine. The two don't interfere except at start time, when I have to suspend Solaris to let BOINC_VM start, for unknown reasons. I've PM'd Dotsch to let him know SETI@home v7 has gone live here, and that his v5/v6 apps will be obsolete soon, he's going to start on the v7 apps within days. (as of the 31 May) Claggy |
GuyPilot Send message Joined: 27 Nov 12 Posts: 1 Credit: 30,229 RAC: 0 |
OK.....sorry but i have got to ask has anybody really found anything? Just figured you guys would be honest Thank, GuyPilot |
Ultrajohn Send message Joined: 4 Jan 01 Posts: 13 Credit: 19,695,377 RAC: 35 |
I get the following (as others have posted) what do we need to do on our end to continue processing. SETI @ home | Message from server: Your file app_info.xml not suitable version of SETI @ home v7. |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
I get the following (as others have posted) what do we need to do on our end to continue processing. Then update your app_info.xml with one that does, with the Latest Lunatics Installer. Claggy |
Robert Blair Send message Joined: 14 Jul 00 Posts: 8 Credit: 12,114,142 RAC: 15 |
I get the following (as others have posted) what do we need to do on our end to continue processing. I have the same problem. I installed the latest SETI version 7.0.65. Since "setiathome_v7" is what is in the app_info.xml file what is the correct string for version 7 (as I have not been able to find the correct string)? |
JarrettH Send message Joined: 14 Nov 02 Posts: 97 Credit: 25,385,250 RAC: 95 |
Tomorrow I'll post explaining why we wanted version 7 and what's different about the analysis it does. Where is this post? Thanks :) |
Thomas Send message Joined: 9 Dec 11 Posts: 1499 Credit: 1,345,576 RAC: 0 |
Tomorrow I'll post explaining why we wanted version 7 and what's different about the analysis it does. Jarrett, if this message of information about V7 was not posted yet, it's certainly that Eric Korpela has not still had time to do it. I'm persuaded that he didn't forget it but all the staff of the project SETI@home must be enormously busy at the moment with all these update. A little of patience, that will come ! :) |
Thomas Send message Joined: 9 Dec 11 Posts: 1499 Credit: 1,345,576 RAC: 0 |
I get the following (as others have posted) what do we need to do on our end to continue processing. From jason_gee My recommendation (Subject to change after I try it) would be: |
Robert Blair Send message Joined: 14 Jul 00 Posts: 8 Credit: 12,114,142 RAC: 15 |
I get the following (as others have posted) what do we need to do on our end to continue processing. Yes. SETI@home Enhanced: yes Astropulse v505: no SETI@home v7: yes AstroPulse v6: no I get the following message every time SETI starts. State file error: bad application name setiathome_v7 I get the following on most requests for work. [SETI@home] Requesting new tasks for CPU [SETI@home] Scheduler request completed: got 0 new tasks [SETI@home] No tasks sent [SETI@home] No tasks are available for SETI@home Enhanced [SETI@home] No tasks are available for SETI@home v7 [SETI@home] Your app_info.xml file doesn't have a usable version of SETI@home v7. [SETI@home] Your app_info.xml file doesn't have a usable version of AstroPulse v6. So what is the correct app_name for SETI v7.0.65? |
©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.