[root@node001 ~]# rpm -qa|grep ^python
python-sqlite-1.1.6-1.x86_64
python-2.3.4-14.4.i386
python-elementtree-1.2.6-4.x86_64
python-ldap-2.0.1-2.x86_64
python-2.3.4-14.4.el4.1.x86_64
[root@node001 ~]# python -c 'import lfc'
Traceback (most recent call last):
File "<string>", line 1, in ?
File "/opt/lcg/lib/python/lfc.py", line 5, in ?
import _lfc
ImportError: /opt/lcg/lib/python/_lfc.so: cannot open shared object
file: No such file or directory
[root@node001 ~]# python32 -c 'import lfc'
[root@node001 ~]# echo $?
0
Note, the python32 thing is a hack, not sure if it's still needed but if
so, see here:
http://www.gridpp.ac.uk/wiki/Workarounds_for_gLite3_on_SC4
Cheers,
Peter
Santanu Das ([log in to unmask]) wrote:
> Dear all,
>
> It seems to be a problem here with python installation on a x86_64 WN.
> The error we get here:
>
> /opt/lcg/lib/python/_lfc.so: cannot open shared object file: No such file
> or directory
>
>
> but the file is actually there but cannot be opened. My collegue made a
> tarball from the CERN installation of the python lfc directory
> (/opt/lcg/lib/python) to check if the lfc libraries installed here on
> 64-bit could are corrupted; but found that both local and tarball import
> failed the same way when running on our 64-bit node. Which implies the
> problem probably is deep within the python installation itself.
>
> Interestingly, Steve L's tests are passing though.
>
> The native version of python is 2.3.4 here:
>
> [root@farm045 ~]# python -V
> Python 2.3.4
>
>
> And these are all the python packages I've got installed here:
>
> [root@farm045 ~]# rpm -qa | grep ^python
> python-devel-2.3.4-14.4.el4.1.x86_64
> python-ldap-2.0.1-2.x86_64
> python-sqlite-1.1.6-1.x86_64
> python-2.3.4-14.4.el4_6.1.i386
> python-elementtree-1.2.6-4.x86_64
> python-2.3.4-14.4.el4.1.x86_64
>
>
>
> Can anyone please provide me the complete list of python 2.3.4 rpms for
> cross-checking, and in particular which one would be causing the the
> type of import error as stated above?
>
>
> Cheers,
> Santanu
|