[Iplant-api-dev] Agave server may be acting hinky

[Duvick, Jonathan P [GDCBS]]

I've had a similar issue submitting job requests via cURL from a virtual server on Atmosphere. Not all the time, but frequently over the past few days.

It seems to happen as follows with repeated submissions:

attempt 1 returns a Proxy Server error and 504 error (gateway timeout) after about 60 seconds

attempt 2 returns 'Call Failed' with 500 error code and '101507Status reportRuntime ErrorError in Sender'

attempt 3 succeeds


Almost as if I have to kick the server awake a few times like a sleeping teenager!


Jon

Jon Duvick
PlantGDB Manager
http://www.plantgdb.org/
Department of Genetics, Development and Cell Biology
2258 Molecular Biology Building
Iowa State University
Ames IA 50011

(515) 294-2360
(515) 294-6755 FAX
________________________________
From: iplant-api-dev-bounces at iplantcollaborative.org <iplant-api-dev-bounces at iplantcollaborative.org> on behalf of Martha Narro <narro at iplantcollaborative.org>
Sent: Tuesday, June 16, 2015 7:10 PM
To: Duvick, Jonathan P [GDCBS]
Cc: A. M. Predoehl; Discussion of iPlant API development
Subject: [Iplant-api-dev] Agave server may be acting hinky

Hi All,

Andrew Predoehl (copied) reported the problem described below to support. I'm moving it to this list so the right people see it.

Martha

==== From Andrew Predoehl =========

You might be (painfully?) aware of this, but in case not:

The Agave API server at agave.iplantc.org<http://agave.iplantc.org> seems to be acting a bit
squirrelly.  I tried to submit two jobs, using some static files
containing JSON, and using the "jobs-submit" script.  Each failed, and
I stubbornly just re-submitted using the same file -- no
modifications.  Each eventually worked.  That seems weird, so I
thought you folks might want to know about it.


Here's a transcript, with the responses and error messages from the
jobs-submit script.

# JOB 1, attempt 1 -- fails mysteriously.
login2.stampede(175)$ jobs-submit -F run_ties_minimal.json
Expecting , delimiter: line 1 column 49 (char 49)
<am:fault xmlns:am="http://wso2.org/apimanager"><am:code>101507</am:code><am:type>Status
report</am:type><am:message>Runtime
Error</am:message><am:description>Error in
Sender</am:description></am:fault>

# JOB 1, attempt 2 -- success, with the very same input file.
login2.stampede(176)$ jobs-submit -F run_ties_minimal.json
Successfully submitted job 0001434497420792-5056a550b8-0001-007

# JOB 2, attempt 1 -- fails mysteriously like job 1
login2.stampede(177)$ jobs-submit -F run_ties_basic_complete.json
Expecting , delimiter: line 1 column 49 (char 49)
<am:fault xmlns:am="http://wso2.org/apimanager"><am:code>101507</am:code><am:type>Status
report</am:type><am:message>Runtime
Error</am:message><am:description>Error in
Sender</am:description></am:fault>

# JOB 2, attempt 2 -- also fails
login2.stampede(178)$ jobs-submit -F run_ties_basic_complete.json
Unable to contact api server at https://agave.iplantc.org/jobs/v2/

# JOB 2, attempt 3 -- success, and my input is unchanged.
login2.stampede(179)$ jobs-submit -F run_ties_basic_complete.json
Successfully submitted job 0001434497509094-5056a550b8-0001-007


Thanks!  Again, I'm just letting you know in the hope that this is
helpful debugging information -- I do not need any assistance on this
matter.  Let me know if you have questions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20150617/3face9b0/attachment.html