no more work from seti.

Message boards : Number crunching : no more work from seti.
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile robl

Send message
Joined: 8 Dec 12
Posts: 47
Credit: 2,587,572
RAC: 0
United States
Message 1381070 - Posted: 14 Jun 2013, 14:01:06 UTC

The following appears in my log file:

app_info.xml file does not have a usable version of SETI@home v7

I am using a Linux box and running Boinc 7.0.29

Other projects shared on this CPU are processing, downloading, uploading normaly, but not SETI.

Must I download a later version of BOINC to support SETI? If not then what might be the problem?
http://www.usefulramblings.org
ID: 1381070 · Report as offensive
Profile Gundolf Jahn

Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 446,358
RAC: 0
Germany
Message 1381074 - Posted: 14 Jun 2013, 14:13:35 UTC - in response to Message 1381070.  

Must I download a later version of BOINC to support SETI?

No, you must download a new version of SETI not of BOINC. And of course, you'll have to adjust your app_info.xml file accordingly.

Gruß,
Gundolf
ID: 1381074 · Report as offensive
Profile robl

Send message
Joined: 8 Dec 12
Posts: 47
Credit: 2,587,572
RAC: 0
United States
Message 1381163 - Posted: 14 Jun 2013, 17:40:28 UTC - in response to Message 1381074.  
Last modified: 14 Jun 2013, 17:42:04 UTC

Must I download a later version of BOINC to support SETI?

No, you must download a new version of SETI not of BOINC. And of course, you'll have to adjust your app_info.xml file accordingly.

Gruß,
Gundolf


How do you force a download of the seti project? remove the old seti directory and reset the project from within BOINC? and where is the new app_info.xml file.
The one I ran with I got from Lunatics. Do I need to get it from them or is there another depository?
http://www.usefulramblings.org
ID: 1381163 · Report as offensive
Alinator
Volunteer tester

Send message
Joined: 19 Apr 05
Posts: 4178
Credit: 4,647,982
RAC: 0
United States
Message 1381172 - Posted: 14 Jun 2013, 18:11:32 UTC
Last modified: 14 Jun 2013, 18:12:06 UTC

Yes, you will have to get the new ones from Lunatics here.
ID: 1381172 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1381187 - Posted: 14 Jun 2013, 18:48:44 UTC - in response to Message 1381172.  

Yes, you will have to get the new ones from Lunatics here.

The Cuda x41g Linux app is still made out for MB v6 use only, For Linux Cuda MB v7 use he'll need to use the app_info snippet posted by William:

Message 1377411

Claggy
ID: 1381187 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1381193 - Posted: 14 Jun 2013, 18:52:43 UTC - in response to Message 1381163.  
Last modified: 14 Jun 2013, 19:08:36 UTC

Must I download a later version of BOINC to support SETI?

No, you must download a new version of SETI not of BOINC. And of course, you'll have to adjust your app_info.xml file accordingly.

Gruß,
Gundolf


How do you force a download of the seti project? remove the old seti directory and reset the project from within BOINC? and where is the new app_info.xml file.
The one I ran with I got from Lunatics. Do I need to get it from them or is there another depository?

Just rename the app_info, and restart Boinc, you'll get sent the Stock v7 CPU apps, once you're got them you'll need to construct a new app_info using the Stock 7.01 Linux CPU app, and the new MB v7 app_info snippit.

The following should work (assuming you got sent the setiathome_7.01_x86_64-pc-linux-gnu app, and assuming the permissions for the apps are right):

<app_info>
<app>
 <name>setiathome_v7</name>
 </app>
 <file_info>
 <name>setiathome_7.01_x86_64-pc-linux-gnu</name>
 <executable/>
 </file_info>
 <app_version>
 <app_name>setiathome_v7</app_name>
 <version_num>701</version_num>
 <platform>x86_64-pc-linux-gnu</platform>
 <file_ref>
 <file_name>setiathome_7.01_x86_64-pc-linux-gnu</file_name>
 <main_program/>
 </file_ref>
 </app_version>
    <app>
        <name>setiathome_v7</name>
    </app>
    <file_info>
        <name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libcudart.so.3</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libcufft.so.3</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
        <platform>x86_64-pc-linux-gnu</platform>
        <plan_class>cuda32</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>libcudart.so.3</file_name>
        </file_ref>
        <file_ref>
            <file_name>libcufft.so.3</file_name>
        </file_ref>
    </app_version>
</app_info>


Claggy
ID: 1381193 · Report as offensive
Alinator
Volunteer tester

Send message
Joined: 19 Apr 05
Posts: 4178
Credit: 4,647,982
RAC: 0
United States
Message 1381211 - Posted: 14 Jun 2013, 19:29:23 UTC - in response to Message 1381187.  
Last modified: 14 Jun 2013, 19:30:03 UTC

Yes, you will have to get the new ones from Lunatics here.

The Cuda x41g Linux app is still made out for MB v6 use only, For Linux Cuda MB v7 use he'll need to use the app_info snippet posted by William:

Message 1377411

Claggy


Thanks for elaborating on the finer points of integrating MBv7 into his setup.

Hand to hand combat on Linux hosts isn't my strong suit. ;-)
ID: 1381211 · Report as offensive
Profile robl

Send message
Joined: 8 Dec 12
Posts: 47
Credit: 2,587,572
RAC: 0
United States
Message 1381484 - Posted: 15 Jun 2013, 12:20:48 UTC - in response to Message 1381193.  
Last modified: 15 Jun 2013, 12:25:28 UTC

I renamed the app_info.xml file, restarted the boinc client and created a new app_info.xml file based upon your code fragment. I do not have the setiathome_7.01_x86_64-pc-linux-gnu file. It did not download.
ID: 1381484 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1381488 - Posted: 15 Jun 2013, 12:54:14 UTC - in response to Message 1381484.  

I renamed the app_info.xml file, restarted the boinc client and created a new app_info.xml file based upon your code fragment. I do not have the setiathome_7.01_x86_64-pc-linux-gnu file. It did not download.

You should be able to download it manually from

http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_7.01_x86_64-pc-linux-gnu
ID: 1381488 · Report as offensive
Profile robl

Send message
Joined: 8 Dec 12
Posts: 47
Credit: 2,587,572
RAC: 0
United States
Message 1382192 - Posted: 17 Jun 2013, 16:59:59 UTC - in response to Message 1381488.  

apologize for delay in responding. needed to upgrade kernel and gpu drivers. always a bit of a challenge on Linux.

Seems to be working now.

Thanks for all the input.
http://www.usefulramblings.org
ID: 1382192 · Report as offensive

Message boards : Number crunching : no more work from seti.


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