What version of Solaris are you running this on? Are the patches up-to-date?
It is a solaris 8 but from here I don't know th patch state.
BTW: I got it for 3 Servers all Solaris 8, but definitivly different patches.
I assume 1 did not have any patches since ages.
The other one should be quite recent.
Quote:
It might be a problem with the Core Client, or a with shared library (pthreads?).
BM
Which thread libs do you suggest. I not sure which ones I'm using. (I'm not used to these, most programs I use are single thread, but I think I can remember we sovled a thread problem by using a differnet LD_LIBRARY_PATH).
Which thread libs do you suggest. I not sure which ones I'm using. (I'm not used to these, most programs I use are single thread, but I think I can remember we sovled a thread problem by using a differnet LD_LIBRARY_PATH).
i think the einstein will not be able to compute correctly more than 1 WU of 10 on my computer...
perhaps its my computer, perhaps my old solaris 7, perhaps the boinc-client, or perhaps albert itself... i don't know...
but as seti works perfectly, i think it could be the albert-software...
WU staying a 100% without calling back the server, WU that never start, no restart after a boinc-client restart....
my question, do you think there will be a new version of boinc or albert for solaris in the next times ?
does someone analyze the errors like:
2006-01-20 23:18:44.8890 [normal]: Start of BOINC application 'albert_4.36_sparc-sun-solaris2.7'.
2006-01-20 23:18:44.8924 [normal]: Started search at lalDebugLevel = 0
2006-01-20 23:18:45.7155 [normal]: Checkpoint-file 'Fstat.out.ckp' not found.
2006-01-20 23:18:45.7214 [normal]: No usable checkpoint found, starting from beginning.
2006-01-21 00:05:28.9333 [normal]: Fstat file reached MaxFileSizeKB ==> compactifying ... done.
2006-01-21 06:34:25.3902 [normal]: Search finished successfully.
i don't want to give up, and i don't want my computer for only searching ET.... but.... without some changes i will have to disable einstein... :-(
i think the einstein will not be able to compute correctly more than 1 WU of 10 on my computer...
perhaps its my computer, perhaps my old solaris 7, perhaps the boinc-client, or perhaps albert itself... i don't know...
but as seti works perfectly, i think it could be the albert-software...
WU staying a 100% without calling back the server, WU that never start, no restart after a boinc-client restart....
my question, do you think there will be a new version of boinc or albert for solaris in the next times ?
does someone analyze the errors like:
2006-01-20 23:18:44.8890 [normal]: Start of BOINC application 'albert_4.36_sparc-sun-solaris2.7'.
2006-01-20 23:18:44.8924 [normal]: Started search at lalDebugLevel = 0
2006-01-20 23:18:45.7155 [normal]: Checkpoint-file 'Fstat.out.ckp' not found.
2006-01-20 23:18:45.7214 [normal]: No usable checkpoint found, starting from beginning.
2006-01-21 00:05:28.9333 [normal]: Fstat file reached MaxFileSizeKB ==> compactifying ... done.
2006-01-21 06:34:25.3902 [normal]: Search finished successfully.
i don't want to give up, and i don't want my computer for only searching ET.... but.... without some changes i will have to disable einstein... :-(
That is really strange --- either patch your system and/or use another BOINC client (newer one), before giving up, I guess. Both machines which I use currently (2 out of 5 available SPARC-Solaris systems), one running Solaris 9, and one Solaris 10, work just fine with albert 4.36, though slow (see below).
[quoteThat is really strange --- either patch your system and/or use another BOINC client (newer one), before giving up, I guess. Both machines which I use currently (2 out of 5 available SPARC-Solaris systems), one running Solaris 9, and one Solaris 10, work just fine with albert 4.36, though slow (see below).
i made this link...but the boinc client does now make a core..... nooooooo !!!!
If you have a pre-Solaris 10, your libstc++.so.x libs will reside in either /usr/local/lib (the 64 bit version in subdirectory sparcv9) resp. /opt/sfw/lib (again look for 64 bit version in subdirectory sparcv9). So just change into the respective directory and there create a softlink to the more current version:
if you have gcc 3.3.x or it's lib installed, version 5:
ln -s libstdc++.so.5 libstdc++.so.3
if you have gcc 3.4.x or it's lib installed, version 6:
ln -s libstdc++.so.6 libstdc++.so.3
Should usually work without complaints or mysterious errors, although it's some kind of fake, but the newer versions can cover the older.
But previously to do so check for two prerequisites:
1. do you have any g++ library at all on your system? The usual locations are as mentioned /opt/sfw/lib (from the software companion), /usr/local/lib (self compiled default location or by sunfreeware.com), /opt/csw/lib (from blastwave.org) or even (only Solaris 10) in /usr/sfw/lib. If not resort to one of those sites/CDs and install at least a libgcc in v3.2 or later (recommended 3.4.x or at least 3.3.x).
2. either extend or define at all your LD_LIBRARY_PATH previous to execution of the BOINC client or use crle to add your (open source) lib directory permanently (not recommended, and do only, if you know very well, what you're doing). For example:
LD_LIBRARY_PATH=/usr/local/lib:/opt/sfw/lib:/usr/lib:/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
(works in all shells but csh resp. tcsh, where you have to use set in front of the assignment of the variable and no export exists)
Afterwards you should be able to run the albert 4.36 app with the BOINC client you got.
first of all, thank you very much for those explanations.... but i'm not an expert :-)
Quote:
ln -s libstdc++.so.5 libstdc++.so.3
id did that... with the latest version i have /usr/local/lib/sparcv9/libstdc++.so.5.0.5
Quote:
1. do you have any g++ library at all on your system? The usual locations are as mentioned /opt/sfw/lib (from the software companion), /usr/local/lib (self compiled default location or by sunfreeware.com), /opt/csw/lib (from blastwave.org) or even (only Solaris 10) in /usr/sfw/lib. If not resort to one of those sites/CDs and install at least a libgcc in v3.2 or later (recommended 3.4.x or at least 3.3.x).
i think there is something like that on my system....
/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.3.2/sparcv9
Quote:
2. either extend or define at all your LD_LIBRARY_PATH previous to execution of the BOINC client or use crle to add your (open source) lib directory permanently (not recommended, and do only, if you know very well, what you're doing). For example:
LD_LIBRARY_PATH=/usr/local/lib:/opt/sfw/lib:/usr/lib:/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
(works in all shells but csh resp. tcsh, where you have to use set in front of the assignment of the variable and no export exists)
i extended my LD_LIBRARY_PATH.... and than i had a new error....
Which thread libs do you suggest. I not sure which ones I'm using. (I'm not used to these, most programs I use are single thread, but I think I can remember we sovled a thread problem by using a differnet LD_LIBRARY_PATH).
RE: What version of
)
It is a solaris 8 but from here I don't know th patch state.
BTW: I got it for 3 Servers all Solaris 8, but definitivly different patches.
I assume 1 did not have any patches since ages.
The other one should be quite recent.
Which thread libs do you suggest. I not sure which ones I'm using. (I'm not used to these, most programs I use are single thread, but I think I can remember we sovled a thread problem by using a differnet LD_LIBRARY_PATH).
Achim
RE: Which thread libs do
)
We added /usr/lib/lwp.
Don't know if this would help.
Achim
i think the einstein will not
)
i think the einstein will not be able to compute correctly more than 1 WU of 10 on my computer...
perhaps its my computer, perhaps my old solaris 7, perhaps the boinc-client, or perhaps albert itself... i don't know...
but as seti works perfectly, i think it could be the albert-software...
WU staying a 100% without calling back the server, WU that never start, no restart after a boinc-client restart....
my question, do you think there will be a new version of boinc or albert for solaris in the next times ?
does someone analyze the errors like:
2006-01-20 23:18:44.8890 [normal]: Start of BOINC application 'albert_4.36_sparc-sun-solaris2.7'.
2006-01-20 23:18:44.8924 [normal]: Started search at lalDebugLevel = 0
2006-01-20 23:18:45.7155 [normal]: Checkpoint-file 'Fstat.out.ckp' not found.
2006-01-20 23:18:45.7214 [normal]: No usable checkpoint found, starting from beginning.
2006-01-21 00:05:28.9333 [normal]: Fstat file reached MaxFileSizeKB ==> compactifying ... done.
2006-01-21 06:34:25.3902 [normal]: Search finished successfully.
i don't want to give up, and i don't want my computer for only searching ET.... but.... without some changes i will have to disable einstein... :-(
RE: i think the einstein
)
That is really strange --- either patch your system and/or use another BOINC client (newer one), before giving up, I guess. Both machines which I use currently (2 out of 5 available SPARC-Solaris systems), one running Solaris 9, and one Solaris 10, work just fine with albert 4.36, though slow (see below).
[quoteThat is really strange
)
[quoteThat is really strange --- either patch your system and/or use another BOINC client (newer one), before giving up, I guess. Both machines which I use currently (2 out of 5 available SPARC-Solaris systems), one running Solaris 9, and one Solaris 10, work just fine with albert 4.36, though slow (see below).
today i tried a other version
)
today i tried a other version ( 4.62 )...
but i have an error like this one describe on the boinc pages....
If BOINC produces messages of the form
ld.so.1: boinc: fatal: libstdc++.so.3: open failed: No such file or
directory
then you probably have a newer version of libstdc++.so, and you may need to symbolically link the newer version to libstdc++.so.3
how can i do this "symbolic link" ???
RE: how can i do this
)
i made this link...but the boinc client does now make a core..... nooooooo !!!!
RE: RE: how can i do this
)
If you have a pre-Solaris 10, your libstc++.so.x libs will reside in either /usr/local/lib (the 64 bit version in subdirectory sparcv9) resp. /opt/sfw/lib (again look for 64 bit version in subdirectory sparcv9). So just change into the respective directory and there create a softlink to the more current version:
if you have gcc 3.3.x or it's lib installed, version 5:
ln -s libstdc++.so.5 libstdc++.so.3
if you have gcc 3.4.x or it's lib installed, version 6:
ln -s libstdc++.so.6 libstdc++.so.3
Should usually work without complaints or mysterious errors, although it's some kind of fake, but the newer versions can cover the older.
But previously to do so check for two prerequisites:
1. do you have any g++ library at all on your system? The usual locations are as mentioned /opt/sfw/lib (from the software companion), /usr/local/lib (self compiled default location or by sunfreeware.com), /opt/csw/lib (from blastwave.org) or even (only Solaris 10) in /usr/sfw/lib. If not resort to one of those sites/CDs and install at least a libgcc in v3.2 or later (recommended 3.4.x or at least 3.3.x).
2. either extend or define at all your LD_LIBRARY_PATH previous to execution of the BOINC client or use crle to add your (open source) lib directory permanently (not recommended, and do only, if you know very well, what you're doing). For example:
LD_LIBRARY_PATH=/usr/local/lib:/opt/sfw/lib:/usr/lib:/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
(works in all shells but csh resp. tcsh, where you have to use set in front of the assignment of the variable and no export exists)
Afterwards you should be able to run the albert 4.36 app with the BOINC client you got.
first of all, thank you very
)
first of all, thank you very much for those explanations.... but i'm not an expert :-)
id did that... with the latest version i have /usr/local/lib/sparcv9/libstdc++.so.5.0.5
i think there is something like that on my system....
/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.3.2/sparcv9
i extended my LD_LIBRARY_PATH.... and than i had a new error....
ld.so.1: ./boinc: fatal: /usr/local/lib/sparcv9/libstdc++.so.3: wrong ELF class: ELFCLASS64
are the clients of boinc compiled for 32-bit libraries ?
if i try without de spracv9 sub-directories.... i have a core....
RE: RE: Which thread libs
)
For now it looks like this was the trick.