 |
 |
Hi Santanu The LFC module is 32 bit, so it cannot be imported into a 64bit python (which naturally you have, running in x86_64). For ATLAS production we can find the ATLAS installed version of python, so we don't really need the python32 anymore. I'm not certain this applies to user analysis ganga jobs - though it has been claimed that python32 is not required we have occasionally seen problems here. Certainly it does no harm to have a python32. Cheers Graeme On 15 Apr 2008, at 12:22, Santanu Das 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