[Iplant-api-dev] API failures

[Rion Dooley]

It was caused by an update I pushed the fix another issue some people were having. Just a race condition...I thought the 3 seconds it took to bounce the server would be safe. I was wrong. My apologies. Updates to Foundation don't generally happen that often anymore, but when they do it's due to address a systematic issue with either the HPC systems of the Foundation infrastructure.

Rion

________________________________________
From: Darren Boss [dboss at email.arizona.edu]
Sent: Wednesday, December 11, 2013 1:32 PM
To: Rion Dooley
Cc: Discussion of iPlant API development
Subject: Re: [Iplant-api-dev] API failures

It's part of a larger job so having one task fail is bad news. I'll
make the changes to my script to kill off the successfully submitted
jobs when this occurs.

Is the problem between the fapi server and lonestar?

On Wed, Dec 11, 2013 at 2:28 PM, Rion Dooley <dooley at tacc.utexas.edu> wrote:
> Check again. Your jobs are running or about to run.
>
> Rion
>
> ________________________________________
> From: iplant-api-dev-bounces at iplantcollaborative.org [iplant-api-dev-bounces at iplantcollaborative.org] on behalf of Darren Boss [dboss at email.arizona.edu]
> Sent: Wednesday, December 11, 2013 1:27 PM
> To: Rion Dooley
> Cc: Discussion of iPlant API development
> Subject: [Iplant-api-dev] API failures
>
> I'm getting repeated failures while submitting v1 jobs:
>
> Failed to submit job 36159: java.io.IOException: Error completing
> remote execution after:
>
> That's all I'm getting in the json message.
>
> 36149 also failed.
> _______________________________________________
> Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org
> List Info and Archives: http://mail.iplantcollaborative.org/mailman/listinfo/iplant-api-dev
> One-click Unsubscribe: http://mail.iplantcollaborative.org/mailman/options/iplant-api-dev/dooley%40tacc.utexas.edu?unsub=1&unsubconfirm=1