SETI@home Version 7 has been released

Message boards : News : SETI@home Version 7 has been released
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 10 · 11 · 12 · 13 · 14 · 15 · 16 . . . 19 · Next

AuthorMessage
Profile William
Volunteer tester
Avatar

Send message
Joined: 14 Feb 13
Posts: 2037
Credit: 17,689,662
RAC: 0
Message 1375855 - Posted: 3 Jun 2013, 9:36:35 UTC - in response to Message 1375782.  

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.

The problem is not that they aren't getting any work, but that they are sending scheduler requests to fetch work and not requesting tasks.

Gruß,
Gundolf

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)
ID: 1375855 · Report as offensive
Profile tullio
Volunteer tester

Send message
Joined: 9 Apr 04
Posts: 8797
Credit: 2,930,782
RAC: 1
Italy
Message 1375895 - Posted: 3 Jun 2013, 11:37:10 UTC

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
ID: 1375895 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 1375897 - Posted: 3 Jun 2013, 11:43:48 UTC - in response to Message 1375742.  

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.

Both processing GPU tasks? Both NVIDIA GPUs. Okay, that's fine, then you have evidence / experience that contradicts mine. (Just a thought, are you also running BOINC 7.0.64?)


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.

Of course, which is why seeing it happen exactly the same way on all 4 of my GPU-enabled machines (with, as I said, 4 quite different GPUs and, as I hadn't previously mentioned, 2 different OS's - Win XP and Win Vista - 2 of each), leads me to what I think is a reasonable theory.


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.

Ummm, perhaps. The bug may be in BOINC but it seems to me like it must be picking up certain configuration information (beyond my expertise to understand at this point) from the application and what it picks up from a newly started v7 GPU app is somehow causing a misconfiguration with whatever it was just using for the v6 GPU app.


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.) :)


Isn't that assuming the SETI servers are recording "not requesting tasks" in their logs in the first place? (Speculation, if done properly, can help lead to solving a problem, provided one uses deductive reasoning along with speculation.) 8-)

Well, I would certainly hope that all incoming work fetch requests are being logged, but.....


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.
ID: 1375897 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1375914 - Posted: 3 Jun 2013, 12:35:46 UTC - in response to Message 1375897.  

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.
ID: 1375914 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 1375931 - Posted: 3 Jun 2013, 13:50:58 UTC - in response to Message 1375914.  

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.
ID: 1375931 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1375944 - Posted: 3 Jun 2013, 15:15:18 UTC

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.
ID: 1375944 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1375957 - Posted: 3 Jun 2013, 15:56:21 UTC - in response to Message 1375897.  

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.
ID: 1375957 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 1375962 - Posted: 3 Jun 2013, 16:05:34 UTC - in response to Message 1375957.  

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.


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.
ID: 1375962 · Report as offensive
Profile Phil
Volunteer tester
Avatar

Send message
Joined: 19 Jun 99
Posts: 110
Credit: 4,545,588
RAC: 0
United Kingdom
Message 1375995 - Posted: 3 Jun 2013, 16:49:17 UTC - in response to Message 1374931.  

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.
ID: 1375995 · Report as offensive
gs
Volunteer tester
Avatar

Send message
Joined: 18 May 99
Posts: 45
Credit: 5,412,660
RAC: 8
Germany
Message 1375998 - Posted: 3 Jun 2013, 16:50:59 UTC - in response to Message 1375589.  

Its 4 pages long.

The number of posts per page is user-configurable. On my current settings, it's 10 pages (or was, before this post).


Good call. Forgot about that. Sorry GS :)


Already forgotten, also the part of whining and the rest of what you wrote...
I usually don't take advice from people slapping me...
ID: 1375998 · Report as offensive
gs
Volunteer tester
Avatar

Send message
Joined: 18 May 99
Posts: 45
Credit: 5,412,660
RAC: 8
Germany
Message 1376002 - Posted: 3 Jun 2013, 16:53:02 UTC - in response to Message 1375944.  

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.


Thank you very much, Richard. This is what I was looking for. Cheers!
ID: 1376002 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1376186 - Posted: 3 Jun 2013, 21:40:54 UTC - in response to Message 1375895.  

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

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
ID: 1376186 · Report as offensive
GuyPilot

Send message
Joined: 27 Nov 12
Posts: 1
Credit: 30,229
RAC: 0
United States
Message 1376237 - Posted: 3 Jun 2013, 23:12:21 UTC

OK.....sorry but i have got to ask

has anybody really found anything?

Just figured you guys would be honest

Thank,

GuyPilot
ID: 1376237 · Report as offensive
Ultrajohn

Send message
Joined: 4 Jan 01
Posts: 13
Credit: 19,695,377
RAC: 35
United States
Message 1376242 - Posted: 3 Jun 2013, 23:22:13 UTC

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.


ID: 1376242 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1376244 - Posted: 3 Jun 2013, 23:23:22 UTC - in response to Message 1376242.  

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.


Then update your app_info.xml with one that does, with the Latest Lunatics Installer.

Claggy
ID: 1376244 · Report as offensive
Robert Blair

Send message
Joined: 14 Jul 00
Posts: 8
Credit: 12,114,142
RAC: 15
United States
Message 1376316 - Posted: 4 Jun 2013, 3:43:25 UTC - in response to Message 1376244.  

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.


Then update your app_info.xml with one that does, with the Latest Lunatics Installer.

Claggy


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)?

ID: 1376316 · Report as offensive
JarrettH

Send message
Joined: 14 Nov 02
Posts: 97
Credit: 25,385,250
RAC: 95
Canada
Message 1376329 - Posted: 4 Jun 2013, 4:09:08 UTC - in response to Message 1373202.  

Tomorrow I'll post explaining why we wanted version 7 and what's different about the analysis it does.


Where is this post? Thanks :)
ID: 1376329 · Report as offensive
Thomas
Volunteer tester

Send message
Joined: 9 Dec 11
Posts: 1499
Credit: 1,345,576
RAC: 0
France
Message 1376364 - Posted: 4 Jun 2013, 5:29:16 UTC - in response to Message 1376329.  

Tomorrow I'll post explaining why we wanted version 7 and what's different about the analysis it does.


Where is this post? Thanks :)

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 ! :)
ID: 1376364 · Report as offensive
Thomas
Volunteer tester

Send message
Joined: 9 Dec 11
Posts: 1499
Credit: 1,345,576
RAC: 0
France
Message 1376371 - Posted: 4 Jun 2013, 5:39:50 UTC - in response to Message 1376316.  

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.


Then update your app_info.xml with one that does, with the Latest Lunatics Installer.

Claggy


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)?

From jason_gee

My recommendation (Subject to change after I try it) would be:
- Set No New tasks
- Wait until tasks all complete, upload & report
- delete app_info.xml from the project directory
- reset the project
- Allow New tasks

Extra notes: Probably need to check web options too in there somewhere [OK :)]. I'd try let the server decide amongst the compatible versions over some time with one instance per GPU (underutilised due to memory intensive Autocorrelations) then worry about multi instances after things settle in. You'd likely want either newer Recommended Boinc for that, or wait for installer for older Boinc clients to run with app_info (anonymous platform)

You'll need to ensure the web preference for V7 is ticked as well, which I gather it probably is.

ID: 1376371 · Report as offensive
Robert Blair

Send message
Joined: 14 Jul 00
Posts: 8
Credit: 12,114,142
RAC: 15
United States
Message 1376386 - Posted: 4 Jun 2013, 6:04:49 UTC - in response to Message 1376371.  

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.


Then update your app_info.xml with one that does, with the Latest Lunatics Installer.

Claggy


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)?

From jason_gee

My recommendation (Subject to change after I try it) would be:
- Set No New tasks
- Wait until tasks all complete, upload & report
- delete app_info.xml from the project directory
- reset the project
- Allow New tasks

Extra notes: Probably need to check web options too in there somewhere [OK :)]. I'd try let the server decide amongst the compatible versions over some time with one instance per GPU (underutilised due to memory intensive Autocorrelations) then worry about multi instances after things settle in. You'd likely want either newer Recommended Boinc for that, or wait for installer for older Boinc clients to run with app_info (anonymous platform)

You'll need to ensure the web preference for V7 is ticked as well, which I gather it probably is.


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?

ID: 1376386 · Report as offensive
Previous · 1 . . . 10 · 11 · 12 · 13 · 14 · 15 · 16 . . . 19 · Next

Message boards : News : SETI@home Version 7 has been released


 
©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.