On Fri, Sep 19, 2008 at 12:03 PM, Santanu Das <[log in to unmask]> wrote:
> I've seen here, even if "/opt/lcg/lib/python" in the PYTHONPATH, still it
> fails to import lfc unless "python32" is used (in stead of python).
That's because 64 bit pythons cannot install 32 bit python modules. At
the moment the LFC plugin you are using is 32 bit, so you need a 32
bit build of python.
I would caution any ATLAS site before upgrading to "native" 64 bit
glite-WN that you might well break ATLAS production jobs. The
production pilot will try and run using the (32 bit) python 2.5
installation in the ATLAS software area (python 2.3, like most of SL4
is antediluvian). If you have a 64 bit python module then this will
cause trouble. Caveat emptor when it comes to 64 bit glite (Andrew has
tried the install a couple of times at Glasgow and it always hits the
skids).
>
> I've also started seeing this at the very end every time I reconfigure a WN
> (since last night):
>
> WARNING: /opt/lcg/lib64 doesn't exist. PYTHONPATH and PERL5LIB won't contain
> 64bit libraries
> WARNING: /opt/glite/lib64 doesn't exist. PYTHONPATH and PERL5LIB won't
> contain 64bit libraries
>
>
> I didn't see this before. Should there a be a "lib64" in there?
No - YAIM is screwed up as Ewan explained (and so is Cambridge, I'm
afraid: https://gus.fzk.de/pages/ticket_details.php?ticket=41099).
Please add /opt/lcg/lib/python back into PYTHONPATH.
Cheers
Graeme
--
Dr Graeme Stewart http://www.physics.gla.ac.uk/~graeme/
Department of Physics and Astronomy, University of Glasgow, Scotland
|