[Iplant-api-dev] job failures Lonestar

[Wang, Liya]

Rion,

My API jobs have been hanging in pending state again for a long time. Not sure whether it is related to the maintenance.

Thanks,
Liya
On Jul 26, 2013, at 5:54 PM, Rion Dooley <dooley at tacc.utexas.edu<mailto:dooley at tacc.utexas.edu>> wrote:

Thanks for the head's up. I kicked the execution system and jobs are flowing again. About 100 have finished. Another 100 or so are queued up or running. API jobs should be caught up in the next couple hours.


Rion

________________________________
From: iplant-api-dev-bounces at iplantcollaborative.org<mailto:iplant-api-dev-bounces at iplantcollaborative.org> [iplant-api-dev-bounces at iplantcollaborative.org<mailto:iplant-api-dev-bounces at iplantcollaborative.org>] on behalf of Sheldon McKay [sheldon.mckay at gmail.com<mailto:sheldon.mckay at gmail.com>]
Sent: Friday, July 26, 2013 2:36 PM
To: Rion Dooley
Cc: Discussion of iPlant API development
Subject: Re: [Iplant-api-dev] job failures Lonestar

We are also experiencing this since 7/23.


On Fri, Jul 26, 2013 at 3:27 PM, Jennewein, Douglas M <Doug.Jennewein at usd.edu<mailto:Doug.Jennewein at usd.edu>> wrote:
Not sure if this is related or not, but we’re experiencing API jobs on lonestar stuck in the Pending state.

Launching jobs via the Test Application as both djennewe and bioextract results in the jobs hanging in the Pending state.  This seems to happen for tools those accounts have deployed as well as for shared tools like clustalw2-lonestar-2.1.

We first noticed this on 7-24.

Doug Jennewein

From: iplant-api-dev-bounces at iplantcollaborative.org<mailto:iplant-api-dev-bounces at iplantcollaborative.org> [mailto:iplant-api-dev-bounces at iplantcollaborative.org<mailto:iplant-api-dev-bounces at iplantcollaborative.org>] On Behalf Of Rion Dooley
Sent: Tuesday, July 23, 2013 7:42 PM
To: Jennewein, Douglas M
Cc: iPlant API Developers Mailing List
Subject: Re: [Iplant-api-dev] job failures Lonestar

Something changed on lonestar. I wad getting tons of errors trying to source module load  irods. When I spidered, the module showed up as iRODS/3.1. I updated to that and the exceptions went away. I can update the db if need be as well.

-
Rion

----- Reply message -----
From: "Matthew Vaughn" <vaughn at tacc.utexas.edu<mailto:vaughn at tacc.utexas.edu>>
To: "Rion Dooley" <dooley at tacc.utexas.edu<mailto:dooley at tacc.utexas.edu>>
Cc: "Discussion of iPlant API development" <iplant-api-dev at iplantcollaborative.org<mailto:iplant-api-dev at iplantcollaborative.org>>
Subject: [Iplant-api-dev] job failures Lonestar
Date: Tue, Jul 23, 2013 5:22 PM

Not intentional. I suspect Chris Jordan didn't realize people were relying on irods lower case.

However, module load failures should not stop jobs from running. The iplant community account has the icommands in its default path. Please share the error messages from the failed jobs, especially the ones in the condor log as those contain info from the API service

On Jul 23, 2013, at 5:08 PM, "Barthelson, Roger A - (rogerab)" <rogerab at email.arizona.edu<mailto:rogerab at email.arizona.edu>>
 wrote:


I'm getting job failures for API jobs on Lonestar. It looks like the module for iRods is now iRODS instead of irods, which causes many of my Lonestar apps to fail. I suspect TACC module updates being the cause. I don't know if this was an intentional change or not.

Roger

Roger Barthelson Ph.D.
Scientific Analyst
iPlant Collaborative
BIO5 Institute, University of Arizona
Phone: 520-977-5249<tel:520-977-5249>
Email: rogerab at email.arizona.edu<mailto:rogerab at email.arizona.edu>
Web: www.iplantcollaborative.org/<http://www.iplantcollaborative.org/>
           bio-it.arizona.edu/Roger_Barthelson_Home.html<http://bio-it.arizona.edu/Roger_Barthelson_Home.html>

_______________________________________________
Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto: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/vaughn%40tacc.utexas.edu?unsub=1&unsubconfirm=1


_______________________________________________
Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto: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/mckays%40cshl.edu?unsub=1&unsubconfirm=1


_______________________________________________
Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto: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/wangli%40cshl.edu?unsub=1&unsubconfirm=1