I am experiencing some very weird behaviour regarding the loading of a shared library from an NFS4 mount, and am hoping someone can shed light on it.
Consider the following:
$ ucto ucto: error while loading shared libraries: libfolia.so.3: cannot open shared object file: No such file or directory
Upon investigation I see no reason this error should appear:
$ which ucto /vol/customopt/lamachine/bin/ucto $ echo $LD_LIBRARY_PATH /vol/customopt/lamachine/lib:/vol/customopt/machine-translation/lib:/vol/customopt/nlptools/lib/: $ ls -lh /vol/customopt/lamachine/lib/libfolia.so.3* lrwxrwxrwx 1 proycon customopt 17 Sep 18 16:42 /vol/customopt/lamachine/lib/libfolia.so.3 -> libfolia.so.3.0.1 -rwxr-xr-x 1 proycon customopt 9.5M Sep 18 16:42 /vol/customopt/lamachine/lib/libfolia.so.3.0.1
I verified I can open the library file without issues.
Now when I switch to another host that uses the very same NFS mount, I have no trouble whatsoever and the library is found and loaded without issue.
The mount is mounted as follows:
customopt-srv.mydomain.com:/export/customopt on /vol/customopt type nfs (rw,nosuid,tcp,hard,intr,sloppy,vers=4)
What is going on here? Is there some caching I'm unaware of? Has anybody experienced similar issues? Should I look client-side or server-side?
Both clients and servers are running Ubuntu 14.04 LTS.