[20:36:05] Trying to send all finished work units[20:36:05] + No unsent completed units remaining.[20:36:05] - Preparing to get new work unit...[20:36:05] Cleaning up work directory[20:36:05] + Attempting to get work packet[20:36:05] Passkey found[20:36:05] - Will indicate memory of 2013 MB[20:36:05] - Connecting to assignment server[20:36:05] Connecting to http://assign.stanford.edu:8080/fah6: relocation error: /lib/libnss_files.so.2: symbol __rawmemchr, version GLIBC_2.2.5 not defined in file libc.so.6 with link time referencethunderrd@OPTERON-185:~/FAH6$ thunderrd@OPTERON-185:~/FAH6$ fah

Note: Please read the license agreement (fah6 -license). Further use of this software requires that you have read and accepted this agreement.

Interestingly enough, I ran apt-get dist-upgrade just yesterday, and everything seemed to upgrade flawlessly. I'm wondering if this could be similar to the Fedora13 problem people have been complaining about lately, maybe a version mismatch or something? Is this machine suddenly a candidate for the alternate fah executables, fah6.static or fah6_alt?

Last edited by ThunderRd on Tue Jun 01, 2010 1:43 pm, edited 1 time in total.

I read those threads before I posted; I just wasn't sure if the problem was the same. The Hus fix is for "Could not CosmHTTPOpen", which I do not see, but tear has deprecated his fix as of yesterday and said to use it: is it correct for me? I mean, running sidux or Debian Sid is a bit touchy at times, and I don't want to screw something up...

In the meantime, while waiting for someone to post, I tried fah6.static and fah6_alt.

fah6_alt runs, but returns an endless "no appropriate server available". fah6.static gives me the immediate relocation error. What does this mean to me?

Home now. Two datapoints:1. I recalled that when I had installed nscd it got set up for automatic startup2. The tool you need to use is update-rc.d, i.e. "sudo update-rc.d nscd enable" -- this will store your preference

Very, very odd;I had nscd installed and configured shortly after it was posted and I 've been running Linux SMP at night and in weekends (lower power tariff here) !Never in all these attempts I had this error again / I run this system in DUAL-boot, WinXP and Ubuntu 10.04 Desktop.So it has been rebooted and even shut down (for air cooling maintenance) several times without any hick-ups

Only last night, I got this message to my utter surprize; so I linked it to the possibility that a system upgrade had changed a or more settings ...

Anyway, I tracked back to that original post about the nscd solution and I found the update; I just ran that command and hope this is fixed now.

Thanks to 'tear' for getting this fix in so soon / I 'm a happy Folder again / last night I just reran the service start command; that fixed it for that session

.

Last edited by noorman on Thu Jul 22, 2010 2:31 pm, edited 1 time in total.

I wouldn't be surprised if there was a bug in nscd that would cause it to... crashgiven some... input (or something).

Your report makes it the third (you said it was a sudden change in behaviour):-- first one was reported with non-forum channels-- second one is there: viewtopic.php?f=44&t=15297 (whoever locked the thread apparently didn't give the subject a lot of thought)