[Swift-user] Swift crash

Michael Wilde wilde at anl.gov
Tue May 6 18:05:04 CDT 2014


Bill, since you are running on Open Science Grid with no specific Condor 
requirements to select specific sites or node types, it looks like some 
sites that your app tasks are running at do not have a Python 
environment that works with your wrapper script.

This might have something to do with that way you have set up or are 
using virtualenv.

You might want to start by adding requirements tags to specify that your 
tasks should only run on the UC3 cycle-seeder nodes, make sure 
everything works correctly there, and then add tags for one additional 
pool of OSG Connect resources at a time. You can find info on this in 
the OSG Connect Book.

You can also log the site name in your returned .err or .out file, via 
your wrapper, which will help a lot in debugging.

Then you can force tasks to the *bad* sites to debug and fix your python 
environment for those sites.

I can help more on this after Friday.  Perhaps others on the Swift team 
or this list can also provide assistance.

- Mike


On 5/6/14, 5:53 PM, William Catino wrote:
> I have a script that crashed 3 times, then succeeded, with no change.
> When it crashed, the .err file in the data directory contained a message
> about not finding a file whose name included
>
>             /usr/lib64/libpython2.6.so.1.0
>
> The attached log file that corresponds to a crash is:
>                 df-20140506-1724-d6au5ct7.log
> The attached log file that corresponds to a subsequent success is:
>                 df-20140506-1727-39v1is9b.log
>
> I might have specific files confused, but these files (and others from
> prior crashes) are located in my home directory on OSG, at /home/wcatino/df.
> This configuration is identical to that used when working with Mike today,
> except that the data directory was reduced to 5 files.
>
> I also noticed that my PATH is pointing swift to version 0.94 rather than
> 0.95.
> Perhaps I should change my PATH to fix this.
> The instructions I followed had me append the 0.95 path to PATH, which
> contains a 0.94 path earlier in the PATH string.
>
> Thanks.

-- 
Michael Wilde
Mathematics and Computer Science          Computation Institute
Argonne National Laboratory               The University of Chicago




More information about the Swift-user mailing list