I have some software which uses the HADDOCK xmlrpc interface to submit and track runs. After switching to the 2.2 server, the function ‘launchproject(user, pass, name, params)’ fails. The error the server returns is ‘<Fault 1: “<type ‘exceptions.AttributeError’>:getvar”>’.
It’s our in-house software which we are developing (Mass Spec Studio at University of Calgary). It’s built using .NET and uses CookComputing XML-RPC library.
To avoid any library specific problems, we can isolate the launchProject function using a short python script. See script:
I have an update on this: submitting the parameter file via the webserver interface works, but the status is stuck on “Processing”. There might be something wrong with the parameter file itself.
How I generated the parameter file: I used the easy haddock interface to submit a job and downloaded its parameter file. (maybe line endings get scrambled or something?)
I have an update on this: submitting the parameter file via the webserver interface works, but the status is stuck on “Processing”. There might be something wrong with the parameter file itself.
Give it some time - could be busy.
If still stuck I will try to look into it
You can simply submit manually a job, and save the generated HADDOCK parameter file - there is a link to it in the first page returned by the server upon submission.
Indeed, we did that using the E2A-HPr-demo data on the first page. We submitted it via web interface, downloaded the parameter file and tried submitting the unchanged parameter file using the XML-RPC interface. What we observed:
Version 2.0 accepts the ‘launchProject’ call and starts a new run, but gets stuck on “Processing”.
Version 2.2 rejects the ‘launchProject’ call with the ‘getvar’ error described above.
As a control, version 2.2 manual file upload web interface runs normally.