Hello,

I am trying to run seti@home on a couple solaris 10 x86_64 boxes, using the package from: http://www.lb.shuttle.de/apastron/boincDown.shtml#solx86

I bypassed the problem with not being able to attach correctly by creating my own account_setiathome.berkeley.edu.xml file, now when I try to launch, I get this:


./boinc_4.32_amd64-solaris10
2006-09-15 16:48:41 [---] Starting BOINC client version 4.32 for i386-pc-solaris2.10
2006-09-15 16:48:41 [---] Data directory: /export/home/johnb/temp2
2006-09-15 16:48:41 [SETI@home] Using your default project prefs
2006-09-15 16:48:41 [SETI@home] Host ID not assigned yet
2006-09-15 16:48:41 [---] No general preferences found - using BOINC defaults
2006-09-15 16:48:41 [---] Insufficient work; requesting more
2006-09-15 16:48:43 [---] Insufficient work; requesting more
2006-09-15 16:48:43 [SETI@home] Requesting 8640.00 seconds of work
2006-09-15 16:48:43 [SETI@home] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-09-15 16:48:44 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-09-15 16:48:44 [SETI@home] Message from server: platform 'i386-pc-solaris2.10' not found
2006-09-15 16:48:44 [SETI@home] No work from project
2006-09-15 16:48:44 [SETI@home] No work from project
2006-09-15 16:48:44 [SETI@home] Deferring communication with project for 23 hours, 59 minutes, and 59 seconds
2006-09-15 16:48:44 [SETI@home] Deferring communication with project for 23 hours, 59 minutes, and 59 seconds


Not sure what is happening, but did they drop support for solaris 10 x86? I saw that others have been able to run it.....


thanks in advance,

John

Ok, well, I think I solved that problem and ran into another.

Apparently when I first ran boinc, it deleted my app_info.xml and the binary, so after the cpu checks finished, i just untarred the file again, to get the binary and the xml back (both located under projects/setathome....) I also deleted client_state.xml, which is why it ran the cpu checks again.

now im getting farther, but still no success:


./boinc_4.32_amd64-solaris10 -return_results_immediately
2006-09-15 17:08:56 [---] Starting BOINC client version 4.32 for i386-pc-solaris2.10
2006-09-15 17:08:56 [---] Data directory: /export/home/johnb/temp2
2006-09-15 17:08:56 [SETI@home] Using your default project prefs
2006-09-15 17:08:56 [SETI@home] Found app_info.xml; using anonymous platform
2006-09-15 17:08:56 [SETI@home] Host ID not assigned yet
2006-09-15 17:08:56 [---] General prefs: from SETI@home (last modified 2006-09-13 17:33:16)
2006-09-15 17:08:56 [---] General prefs: using your defaults
2006-09-15 17:08:56 [---] Running CPU benchmarks
2006-09-15 17:09:55 [---] Benchmark results:
2006-09-15 17:09:55 [---] Number of CPUs: 2
2006-09-15 17:09:55 [---] 1931 double precision MIPS (Whetstone) per CPU
2006-09-15 17:09:55 [---] 5639 integer MIPS (Dhrystone) per CPU
2006-09-15 17:09:55 [---] Finished CPU benchmarks
2006-09-15 17:09:55 [---] Resuming computation and network activity
2006-09-15 17:09:55 [---] Insufficient work; requesting more
2006-09-15 17:09:57 [---] Insufficient work; requesting more
2006-09-15 17:09:57 [SETI@home] Requesting 864000.00 seconds of work
2006-09-15 17:09:57 [SETI@home] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-09-15 17:09:58 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-09-15 17:09:58 [SETI@home] Message from server: No work sent
2006-09-15 17:09:58 [SETI@home] Message from server: No work sent
2006-09-15 17:09:58 [SETI@home] No work from project
2006-09-15 17:09:58 [SETI@home] No work from project
2006-09-15 17:09:58 [SETI@home] Deferring communication with project for 59 minutes and 59 seconds
2006-09-15 17:09:58 [SETI@home] Deferring communication with project for 59 minutes and 59 seconds

Ok, well, I think I solved that problem and ran into another.

Apparently when I first ran boinc, it deleted my app_info.xml and the binary, so after the cpu checks finished, i just untarred the file again, to get the binary and the xml back (both located under projects/setathome....) I also deleted client_state.xml, which is why it ran the cpu checks again.

There was a problem with the older boinc clients, which deleted the whole project directory, if you do a -attach_project.

2006-09-15 17:09:57 [---] Insufficient work; requesting more
2006-09-15 17:09:57 [SETI@home] Requesting 864000.00 seconds of work
2006-09-15 17:09:57 [SETI@home] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-09-15 17:09:58 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-09-15 17:09:58 [SETI@home] Message from server: No work sent
2006-09-15 17:09:58 [SETI@home] Message from server: No work sent
2006-09-15 17:09:58 [SETI@home] No work from project
2006-09-15 17:09:58 [SETI@home] No work from project

Which SETI app do you use ?
Could you please try a boinc_client -update_prefs, too.

---

I'm having the same issue as well with seti using solaris x86 on a 32 bit platform..

compiled boinc just fine, cpu is an athlon-xp, I successfully attached to the project, and I believe this is the problem:

9/30/2006 9:36:46 AM||Starting BOINC client version 5.4.11 for i386-pc-solaris
9/30/2006 9:36:46 AM||libcurl/7.15.5 OpenSSL/0.9.7d zlib/1.1.4
9/30/2006 9:36:46 AM||Data directory: /opt/boinc
9/30/2006 9:36:46 AM|SETI@home|Found app_info.xml; using anonymous platform
9/30/2006 9:36:46 AM||Processor: 1 i86pc pentium_pro+mmx
9/30/2006 9:36:46 AM||Memory: 767.56 MB physical, 0 bytes virtual
9/30/2006 9:36:46 AM||Disk: 35.67 GB total, 31.14 GB free
9/30/2006 9:36:46 AM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 2710366; location: home; project prefs: default
9/30/2006 9:36:46 AM||No general preferences found - using BOINC defaults
2006-09-30 09:27:50 [http://setiathome.berkeley.edu/] Requesting 8640 seconds of new work
2006-09-30 09:27:53 [http://setiathome.berkeley.edu/] Scheduler request succeeded
2006-09-30 09:27:53 [SETI@home] Message from server: platform 'i386-pc-solaris' not found


I went and downloaded apastron's client setiathome-4.7.i386-pc-solaris2.10 from http://www.lb.shuttle.de/apastron/boincDown.shtml#solx86 , put the client and the app_info.xml into the /projects/setiathome.berkeley.edu directly..

when I fire it up, this is the message reported:

9/30/2006 9:37:27 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/30/2006 9:37:27 AM|SETI@home|Reason: Requested by user
9/30/2006 9:37:27 AM|SETI@home|Requesting 8640 seconds of new work
9/30/2006 9:37:32 AM|SETI@home|Scheduler request succeeded
9/30/2006 9:37:32 AM|SETI@home|General preferences have been updated
9/30/2006 9:37:32 AM|SETI@home|Message from server: No work sent

plain and simple, Berkeley isn't supporting Solaris x86 and will not send work to a platform their server says is not found..

I went and downloaded apastron's client setiathome-4.7.i386-pc-solaris2.10 from http://www.lb.shuttle.de/apastron/boincDown.shtml#solx86 , put the client and the app_info.xml into the /projects/setiathome.berkeley.edu directly..

when I fire it up, this is the message reported:

9/30/2006 9:37:27 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/30/2006 9:37:27 AM|SETI@home|Reason: Requested by user
9/30/2006 9:37:27 AM|SETI@home|Requesting 8640 seconds of new work
9/30/2006 9:37:32 AM|SETI@home|Scheduler request succeeded
9/30/2006 9:37:32 AM|SETI@home|General preferences have been updated
9/30/2006 9:37:32 AM|SETI@home|Message from server: No work sent

You have downloaded the wrong version. SETI 4.x is obsolated by the SETI Enhanced 5.x. Please download the 5.x SETI application.

---

You have downloaded the wrong version. SETI 4.x is obsolated by the SETI Enhanced 5.x. Please download the 5.x SETI application.

I would if there were one available for Solaris x86

I've been trying to build my own but the compile fails

You have downloaded the wrong version. SETI 4.x is obsolated by the SETI Enhanced 5.x. Please download the 5.x SETI application.

I would if there were one available for Solaris x86

I've been trying to build my own but the compile fails

Stefan is working on the solaris x86 i386/i686 and Solaris SPARC Ultra 1/2/3 optimized port.

---

You have downloaded the wrong version. SETI 4.x is obsolated by the SETI Enhanced 5.x. Please download the 5.x SETI application.

I would if there were one available for Solaris x86

I've been trying to build my own but the compile fails

Stefan is working on the solaris x86 i386/i686 and Solaris SPARC Ultra 1/2/3 optimized port.

ok.. I got 5.17 to build..

ls -l /opt/boinc/projects/setiathome.berkeley.edu/
total 3266
-rw-r--r-- 1 keherma staff 434 Sep 30 12:21 app_info.xml
-rwxr-xr-x 1 keherma staff 1661808 Sep 30 12:19 setiathome-5.17.i386-pc-solaris


setiathome-5.17.i386-pc-solaris: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, stripped

and ... more app_info.xml

<app_info>
    <app>
        <name>setiathome</name>
    </app>
    <file_info>
        <name>setiathome-5.17.i386-pc-solaris</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome</app_name>
        <version_num>517</version_num>
        <file_ref>
            <file_name>setiathome-5.17.i386-pc-solaris</file_name>
            <main_program/>
        </file_ref>
    </app_version>
</app_info>

same result.. no work is given out from the server...

ok.. I got 5.17 to build..

Oh, 5.17 is for use in the beta project only. It is not vaild in the main project !
For the main project, 5.12 to 5.15 are vailid.

same result.. no work is given out from the server...

A "boinc_client -update_prefs http://setiathome.berkeley.edu" or a update projects within the boinc manager will do the job, and your system will download work.

---

ok.. I got 5.17 to build..

Oh, 5.17 is for use in the beta project only. It is not vaild in the main project !
For the main project, 5.12 to 5.15 are vailid.

same result.. no work is given out from the server...

A "boinc_client -update_prefs http://setiathome.berkeley.edu" or a update projects within the boinc manager will do the job, and your system will download work.

can you point me to the 5.12 or 5.15 source? it seems everything at http://setiweb.ssl.berkeley.edu/sah/seti_source/ are all beta's.. (at least every build I tried came up 5.17)

the build I compiled was setiathome_enhanced-client-cvs-2006-08-01.tar.gz

ok.. I got 5.17 to build..

Oh, 5.17 is for use in the beta project only. It is not vaild in the main project !
For the main project, 5.12 to 5.15 are vailid.

same result.. no work is given out from the server...

A "boinc_client -update_prefs http://setiathome.berkeley.edu" or a update projects within the boinc manager will do the job, and your system will download work.

built and installed setiathome-5.13.i386-pc-solaris (used setiathome_enhanced-client-cvs-2006-05-10.tar.gz).. updated the app_info.xml

also tried boinc_client -update_prefs http://setiathome.berkeley.edu

same deal.. server will not send work.. is this also a beta I'm running?

I still say the reason is that Berkeley simply does not recognize my platform, going back to the original message when I attached:

2006-09-30 09:27:53 [SETI@home] Message from server: platform 'i386-pc-solaris' not found

because of this I think the server just refuses to send work to a platform it doesn't know about.

built and installed setiathome-5.13.i386-pc-solaris (used setiathome_enhanced-client-cvs-2006-05-10.tar.gz).. updated the app_info.xml

also tried boinc_client -update_prefs http://setiathome.berkeley.edu

same deal.. server will not send work.. is this also a beta I'm running?

I still say the reason is that Berkeley simply does not recognize my platform, going back to the original message when I attached:

2006-09-30 09:27:53 [SETI@home] Message from server: platform 'i386-pc-solaris' not found

because of this I think the server just refuses to send work to a platform it doesn't know about.

SETI 5.13 is OK.
If could be, that the app_info.xml file will not found. Please verify if the file is in your $BOINCDIR/projects/setiathome.berkeley.edu and stop/start the boinc client.
If the app_info.xml is not there, it could be that it was deleted by one of your previous tries. Also, you can copy back the file from Stefan, and change it for your needs.
Btw. you should also let the reference WU run, to verify that your binary produces correct results.

---

still no go.. I am currently trying setiathome-5.15.i386-pc-solaris, which I compiled..

% file setiathome-5.15.i386-pc-solaris
setiathome-5.15.i386-pc-solaris: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, stripped

and unless I am missing something, it is currently working on the reference work unit (as work_unit.sah)

% ps -ef | grep seti
keherma 15336 2496 98 14:25:27 pts/2 7:25 ./setiathome-5.15.i386-pc-solaris -standalone

the other version I had, 3.13 would segfault.. this one appears to be work.. however Berkely STILL does not send this client work.

I am 1000% sure everything is good on my end.. It is Berkeley that will not recognize an i386-pc-solaris client.

perhapse because it's not set to recognize it?

the other version I had, 3.13 would segfault.. this one appears to be work.. however Berkely STILL does not send this client work.

Oh. Not cool.

I am 1000% sure everything is good on my end.. It is Berkeley that will not recognize an i386-pc-solaris client.

perhapse because it's not set to recognize it?

Do you have a app_info.xml installed ? - If you start the boinc client there should be a message, that the boinc client has found app_info.xml and using the anonymous platform.

Also, you could wait, till Stefan has a compiled a binary. I could ask him, when he would have a binary available.

---

Do you have a app_info.xml installed ? - If you start the boinc client there should be a message, that the boinc client has found app_info.xml and using the anonymous platform.

like this?

2006-10-02 14:59:59 [---] Starting BOINC client version 5.4.11 for i386-pc-solaris
2006-10-02 14:59:59 [---] libcurl/7.15.5 OpenSSL/0.9.7d zlib/1.1.4
2006-10-02 14:59:59 [---] Data directory: /opt/boinc
2006-10-02 14:59:59 [SETI@home] Found app_info.xml; using anonymous platform

<app_info>
    <app>
        <name>setiathome</name>
    </app>
    <file_info>
        <name>setiathome-5.15.i386-pc-solaris</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome</app_name>
        <version_num>515</version_num>
        <file_ref>
            <file_name>setiathome-5.15.i386-pc-solaris</file_name>
            <main_program/>
        </file_ref>
    </app_version>
</app_info>

is this not the correct format?

I got it!!!

all I had to do was a change in the app_info.xml file....

<app_name>setiathome</app_name>

to

<app_name>setiathome_enhanced</app_name>

fired up boinc and a WU was sent immediately!

10/2/2006 6:51:54 PM||Starting BOINC client version 5.4.11 for i386-pc-solaris
10/2/2006 6:51:54 PM||libcurl/7.15.5 OpenSSL/0.9.7d zlib/1.1.4
10/2/2006 6:51:54 PM||Data directory: /opt/boinc
10/2/2006 6:51:54 PM|SETI@home|Found app_info.xml; using anonymous platform
10/2/2006 6:51:54 PM||Processor: 1 i86pc pentium_pro+mmx
10/2/2006 6:51:54 PM||Memory: 767.56 MB physical, 0 bytes virtual
10/2/2006 6:51:54 PM||Disk: 35.67 GB total, 31.07 GB free
10/2/2006 6:51:54 PM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 2710784; location: home; project prefs: home
10/2/2006 6:51:54 PM||General prefs: from SETI@home (last modified 2006-09-30 20:22:35)
10/2/2006 6:51:54 PM||General prefs: using separate prefs for home
10/2/2006 6:51:54 PM||Remote control allowed
10/2/2006 6:51:54 PM||Listening on port 31416
10/2/2006 6:51:54 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
10/2/2006 6:51:54 PM|SETI@home|Reason: To fetch work
10/2/2006 6:51:54 PM|SETI@home|Requesting 8640 seconds of new work
10/2/2006 6:51:59 PM|SETI@home|Scheduler request succeeded
10/2/2006 6:52:01 PM|SETI@home|Started download of file 28ap03aa.13742.28641.561076.3.212
10/2/2006 6:52:05 PM|SETI@home|Finished download of file 28ap03aa.13742.28641.561076.3.212
10/2/2006 6:52:05 PM|SETI@home|Throughput 124104 bytes/sec
10/2/2006 6:52:06 PM||Rescheduling CPU: files downloaded
10/2/2006 6:52:06 PM|SETI@home|Starting task 28ap03aa.13742.28641.561076.3.212_1 using setiathome_enhanced version 515


woo hoo!

I just want to thank you guys for working through the problems you had here. The info mentioned helped me get my solaris host running as well. you can check out this thread to see how, if interested: http://setiathome.berkeley.edu/forum_thread.php?id=31531

Thanks!

---

I want to thank you guys too but I still can't get anything to work.
For a while I had various clients running on my machine (Solaris 10/SunFire X2100 [Opteron]) but failed to ever get any work units. Now I'm looking at this client from http://www.lb.shuttle.de/apastron/boincDown.shtml for Opteron, and first it complains can't find libstdc++.so.6.. well I know I have it so I set LD_LIBRARY_PATH (which was supposed to be set already??) and end up with

ld.so.1: boinc_5.2.14_amd64-solaris10: fatal: /usr/local/lib/libstdc++.so.6: wrong ELF class: ELFCLASS32
Killed

Soo, I don't have time for this anymore, I would love to help but I quit.

---

I want to thank you guys too but I still can't get anything to work.
For a while I had various clients running on my machine (Solaris 10/SunFire X2100 [Opteron]) but failed to ever get any work units. Now I'm looking at this client from http://www.lb.shuttle.de/apastron/boincDown.shtml for Opteron, and first it complains can't find libstdc++.so.6.. well I know I have it so I set LD_LIBRARY_PATH (which was supposed to be set already??) and end up with

ld.so.1: boinc_5.2.14_amd64-solaris10: fatal: /usr/local/lib/libstdc++.so.6: wrong ELF class: ELFCLASS32
Killed

You need to install the 64 bit libstdc++ (it should be available on Stefans site, or at www.sunfreeware.com), if you have not installed it. This is a Solaris problem. Solaris could not mix 32 and 64 bit libs. But Your LD_LIBRARY_PATH statement points to the 32 bit library. So the binary crashs.

With "find /usr -name libstdc++\\* -exec file {} \\;" you can verify, if you have installed a 64 bit libstdc++.

---

I will try again with the 5.4.9

---