Atlas-connect-l mailing list

[Ilija Vukotic <ivukotic AT uchicago.edu>]

Hi,

There is some networking issue at MWT2, so the issue will affect xrdcp too. We are trying to understand it, it goes slowly as Lincoln is on vacation…

If you use dagman it should resend the job. We are still not sure if there is a pattern in which nodes can not access the data, is it all the time or the problem “moves”.

Ilija

On Feb 12, 2016, at 12:00 , Christopher Meyer <chris.meyer AT cern.ch> wrote:

Hello again,

To work around this issue, is there a better way for me to submit jobs? For example, xrdcp the file locally, and then run? Or is it possible to send a return code to condor requesting that the job be retried on a different node?

Thanks,
Chris

On Thu, Feb 11, 2016, 10:27 Christopher Meyer <chris.meyer AT cern.ch> wrote:

Hi ilija,

Thanks for taking a look. I submitted another set of jobs last night, and this morning it looks like ~15% failed with the same issues as above.

Cheers,

Chris

On Wed, Feb 10, 2016 at 9:50 PM Ilija Vukotic <ivukotic AT uchicago.edu> wrote:

Hi Chris,

Now that you excluded a possibility that the files are actually corrupted, it must be a networking issue. We will test again from these hosts just to make sure this was a transient issue.

Thanks for reporting,

Ilija

On Feb 10, 2016, at 14:06 , Christopher Meyer <chris.meyer AT cern.ch> wrote:

Dear Experts,

A few days ago I submitted a large number of jobs using condor through ATLAS connect. However, a number of them failed with errors like those in the log file I've attached. I've run on some of these files directly from login.usatlas.org (using the root:// path) and everything works fine.

There was only one of the first type, which failed on:

iut2-c191.iu.edu

The second type failed on these nodes:

uct2-c166.mwt2.org

uct2-c173.mwt2.org

uct2-c127.mwt2.org

uct2-c086.mwt2.org

uct2-c108.mwt2.org

uct2-c180.mwt2.org

uct2-c154.mwt2.org

uct2-c078.mwt2.org

uct2-c045.mwt2.org

uct2-c170.mwt2.org

uct2-c133.mwt2.org

uct2-c103.mwt2.org

uct2-c172.mwt2.org

uct2-c080.mwt2.org

uct2-c171.mwt2.org

Does anyone have an idea what might be going wrong? Or if there's something I can do to protect against this?

Thanks!

Chris

<crash_type1.txt><crash_type2.txt>_______________________________________________
Atlas-connect-l mailing list
Atlas-connect-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/atlas-connect-l

_______________________________________________
Atlas-connect-l mailing list
Atlas-connect-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/atlas-connect-l
_______________________________________________
ATLAS Midwest Tier2 mailing list
http://mwt2.usatlasfacility.org