Some API functions stopped working:
returns:
Error: Argument is out of range. (System.ArgumentOutOfRangeException)
This slipped through our testing, but is now affecting the production server :\
This is with version 8.0.10.4
Some API functions stopped working:
returns:
Error: Argument is out of range. (System.ArgumentOutOfRangeException)
This slipped through our testing, but is now affecting the production server :\
This is with version 8.0.10.4
Another one:
/api/jobs?JobID=581aabbee1a82539002c6174
results:
Error: Argument is out of range. (System.ArgumentOutOfRangeException)
Is this fixable by patching the python API?
Hmm thats very odd, I am not able to reproduce this behavior. Are you connecting to the web service with the Python API or with some other client? Can you provide the Web Service logs from when the errors occurred?
We noticed it with the python api, but then i also reproduced it simply in a browser. The webservice machines were self updated from an earlier version of deadline (8.0.4), maybe its a problem with the self update procedure?
Here is one error log:
2016-11-03 06:26:19: Web Service - Received request from: 172.18.3.250
2016-11-03 06:26:19: Web Service - Request: GET /api/jobs?JobID=581aabbee1a82539002c6174
2016-11-03 06:26:19: Web Service - Found API command: jobs
2016-11-03 06:26:19: Web Service - Error: Argument is out of range. (System.ArgumentOutOfRangeException)
2016-11-03 06:26:19: Web Service - Web Service listening for requests…
Seems like its the self updating that didn’t do a sufficient job. I tried reinstalling deadline on those machines from scratch, and now the call works. Thats a bit odd? Could this also affect our slave behavior? (some dlls being out of date?)
Huh. That’s very odd… We’re not aware of any issues with auto-upgrading our binaries.
Are you guys running the webservice on a Linux box? Or is it Windows? And which installer did you run to update the repo files? Presumably the Windows one?
Yep, the webservice and pulse services all run on a cluster of linux boxes, the repo installer was windows.
Hmmm, interesting. I’ll be sure to test this out with the next round of installers.