Welcome to MilkyWay@home

libm.so.2 on solaris


Advanced search

Questions and Answers : Unix/Linux : libm.so.2 on solaris
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Dotsch

Send message
Joined: 31 Aug 07
Posts: 20
Credit: 1,022
RAC: 0
1 credit badge10 year member badge
Message 1253 - Posted: 2 Jan 2008, 11:18:27 UTC - in response to Message 1250.  
Last modified: 2 Jan 2008, 12:02:01 UTC

But to make sure that it work on all releases a check of the different libm.so.* on a Solaris 10 system would be needed.

What do you need:
/lib$ uname -srpiv
SunOS 5.10 Generic_118833-36 sparc SUNW,Sun-Fire-V490
/lib$ ls -l libm.so*
lrwxrwxrwx   1 root     root           9 Apr 10  2007 libm.so -> libm.so.2
-rwxr-xr-x   1 root     bin        23828 Jan 23  2005 libm.so.1
-rwxr-xr-x   1 root     bin       792916 Jan 23  2005 libm.so.2
/lib$


Thank you very much !

According to your output I think that the astro application has no problem, if it would be linked explicit against the libm.so.1.
ID: 1253 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
achims311

Send message
Joined: 30 Oct 07
Posts: 14
Credit: 203,123
RAC: 850
100 thousand credit badge10 year member badge
Message 1254 - Posted: 2 Jan 2008, 11:28:31 UTC

Now as this seems to be near a solution.
What about the new problem with the pthreads lib?

Remember I did not have any trouble with verion 1.07, but I have trouble with 1.13

Thanks
ID: 1254 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Dotsch

Send message
Joined: 31 Aug 07
Posts: 20
Credit: 1,022
RAC: 0
1 credit badge10 year member badge
Message 1586 - Posted: 24 Jan 2008, 21:56:01 UTC - in response to Message 1254.  

BUMP. Any news about this problem ?
ID: 1586 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileBlisteringSheep

Send message
Joined: 20 Dec 07
Posts: 1
Credit: 17,387,672
RAC: 50
10 million credit badge10 year member badge
Message 1587 - Posted: 24 Jan 2008, 23:38:53 UTC

Just wanted to add a voice to those who would be interested in running this project on a SPARC running Solaris 8. I applied some updates (hadn't been following patches), and got to a state where everything resolved, but it errors at startup.

~/boinc/BOINC>./boinc --version
5.10.17 sparc-sun-solaris

~/boinc/BOINC>./boinc_cmd --get_host_info
timezone: -18000
domain name: longwood
IP addr: 192.168.0.10
#CPUS: 1
CPU vendor: SUNW,Ultra-5_10
CPU model: sparcv9+vis
CPU FP OPS: 209424083.769634
CPU int OPS: 428183199.086342
CPU mem BW: 1000000000.000000
OS name: SunOS
OS version: 5.8
mem size: 402653184.000000
cache size: 1000000.000000
swap size: 537247744.000000
disk size: 56733159526249472000.000000
disk free: 6148447033722383360.000000

~/boinc/BOINC/projects/milkyway.cs.rpi.edu_milkyway>./astronomy_1.13_sparc-sun-solaris

~/boinc/BOINC/projects/milkyway.cs.rpi.edu_milkyway>cat stderr.txt
Can't open init data file - running in standalone mode
set_worker_timer(): pthread_create(): -1

~/boinc/BOINC/projects/milkyway.cs.rpi.edu_milkyway>ldd astronomy_1.13_sparc-sun-solaris
libCstd.so.1 => /lib/libCstd.so.1
libCrun.so.1 => /lib/libCrun.so.1
libm.so.2 => /lib/libm.so.2
libc.so.1 => /lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/lib/cpu/sparcv8plus/libCstd_isa.so.1
/usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1

Note that I did cheat on libm.so.2 (symlink to libm.so.1)

ID: 1587 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
tssmith2002

Send message
Joined: 17 Oct 07
Posts: 2
Credit: 300,139
RAC: 88
100 thousand credit badge10 year member badge
Message 1603 - Posted: 27 Jan 2008, 5:09:48 UTC

My dual processor Solaris 9.05 machine is failing as well. ldd shows all libraries in place. Like everyone else I cheated with the libm.so.2 file but everything should be fine.

Todd
ID: 1603 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
tssmith2002

Send message
Joined: 17 Oct 07
Posts: 2
Credit: 300,139
RAC: 88
100 thousand credit badge10 year member badge
Message 1616 - Posted: 28 Jan 2008, 18:35:37 UTC

This is the BOINC error log that hopefully can help troubleshooting.

This is Solaris 9 using the BOINC 5.10.17 client

1/27/2008 01:21:33|Milkyway@home|Starting gs_163_1201401068_278582_0
1/27/2008 01:21:33|Milkyway@home|Starting task gs_163_1201401068_278582_0 using astronomy version 113
1/27/2008 01:21:35|Milkyway@home|Deferring communication for 1 min 0 sec
1/27/2008 01:21:35|Milkyway@home|Reason: Unrecoverable error for result gs_163_1201401068_278582_0 (process exited with code 255 (0xff, -1))
1/27/2008 01:21:35|Milkyway@home|Computation for task gs_163_1201401068_278582_0 finished
1/27/2008 01:21:35|Milkyway@home|Output file gs_163_1201401068_278582_0_0 for task gs_163_1201401068_278582_0 absent
1/27/2008 01:21:35|Milkyway@home|Starting gs_163_1201401068_278583_0
1/27/2008 01:21:35|Milkyway@home|Starting task gs_163_1201401068_278583_0 using astronomy version 113
1/27/2008 01:21:35|Milkyway@home|Starting gs_163_1201401068_278584_0
1/27/2008 01:21:35|Milkyway@home|Starting task gs_163_1201401068_278584_0 using astronomy version 113
1/27/2008 01:21:36|Milkyway@home|Deferring communication for 1 min 0 sec
1/27/2008 01:21:36|Milkyway@home|Reason: Unrecoverable error for result gs_163_1201401068_278584_0 (process exited with code 255 (0xff, -1))
1/27/2008 01:21:36|Milkyway@home|Computation for task gs_163_1201401068_278584_0 finished
1/27/2008 01:21:36|Milkyway@home|Output file gs_163_1201401068_278584_0_0 for task gs_163_1201401068_278584_0 absent
1/27/2008 01:21:36|Milkyway@home|Starting gs_161_1201401068_278585_0
1/27/2008 01:21:36|Milkyway@home|Starting task gs_161_1201401068_278585_0 using astronomy version 113
1/27/2008 01:21:37|Milkyway@home|Deferring communication for 1 min 0 sec
1/27/2008 01:21:37|Milkyway@home|Reason: Unrecoverable error for result gs_161_1201401068_278585_0 (process exited with code 255 (0xff, -1))
1/27/2008 01:21:37|Milkyway@home|Computation for task gs_161_1201401068_278585_0 finished
1/27/2008 01:21:37|Milkyway@home|Output file gs_161_1201401068_278585_0_0 for task gs_161_1201401068_278585_0 absent
1/27/2008 01:21:37|Milkyway@home|Starting gs_161_1201401068_278586_0
1/27/2008 01:21:37|Milkyway@home|Starting task gs_161_1201401068_278586_0 using astronomy version 113
1/27/2008 01:21:38|Milkyway@home|Deferring communication for 1 min 0 sec
1/27/2008 01:21:38|Milkyway@home|Reason: Unrecoverable error for result gs_161_1201401068_278586_0 (process exited with code 255 (0xff, -1))
1/27/2008 01:21:38|Milkyway@home|Computation for task gs_161_1201401068_278586_0 finished
1/27/2008 01:21:39|Milkyway@home|Deferring communication for 1 min 29 sec
1/27/2008 01:21:39|Milkyway@home|Reason: Unrecoverable error for result gs_163_1201401068_278583_0 (process exited with code 255 (0xff, -1))
1/27/2008 01:21:39|Milkyway@home|Computation for task gs_163_1201401068_278583_0 finished
1/27/2008 01:21:39|Milkyway@home|Output file gs_163_1201401068_278583_0_0 for task gs_163_1201401068_278583_0 absent
ID: 1616 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Alessandro Freda

Send message
Joined: 11 Apr 08
Posts: 11
Credit: 43,597,062
RAC: 0
30 million credit badge10 year member badge
Message 3322 - Posted: 23 Apr 2008, 22:00:36 UTC - in response to Message 1616.  

This is the BOINC error log that hopefully can help troubleshooting.

This is Solaris 9 using the BOINC 5.10.17 client

1/27/2008 01:21:33|Milkyway@home|Starting gs_163_1201401068_278582_0
1/27/2008 01:21:33|Milkyway@home|Starting task gs_163_1201401068_278582_0 using astronomy version 113
1/27/2008 01:21:35|Milkyway@home|Deferring communication for 1 min 0 sec
1/27/2008 01:21:35|Milkyway@home|Reason: Unrecoverable error for result gs_163_1201401068_278582_0 (process exited with code 255 (0xff, -1))


I've found the same problem downgrading a sunfirev240 from Solaris 10 to 9.
I've backuped in a tar file the working boinc (5.10.17) user, and as usual move to the new env.

Without the libm.so.2 present the task continue to restart:

Project Date Message
Milkyway@home 23/04/2008 23.20.39 Restarting task gs_571_1208988172_92822_0 using astronomy version 121

after coping the libm.so.2 from a Solaris 10 server, (ldd => ok) I see a WUs waste with continue computation error.

Have you found the solution ?

Regards,

Alessandro
ID: 3322 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Alessandro Freda

Send message
Joined: 11 Apr 08
Posts: 11
Credit: 43,597,062
RAC: 0
30 million credit badge10 year member badge
Message 3323 - Posted: 23 Apr 2008, 22:08:23 UTC - in response to Message 3322.  


Project Date Message
Milkyway@home 23/04/2008 23.20.39 Restarting task gs_571_1208988172_92822_0 using astronomy version 121



Sorry, my complete log was:

Project Date Message
Milkyway@home 23/04/2008 23.20.41 Restarting task gs_571_1208988172_92822_0 using astronomy version 121
Milkyway@home 23/04/2008 23.20.42 Task gs_571_1208988172_92822_0 exited with zero status but no 'finished' file
Milkyway@home 23/04/2008 23.20.42 If this happens repeatedly you may need to reset the project.
ID: 3323 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 · 2

Questions and Answers : Unix/Linux : libm.so.2 on solaris

©2020 Astroinformatics Group