Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store the inputs used for failed processes #131

Open
tomLandry opened this issue Nov 30, 2016 · 2 comments
Open

Store the inputs used for failed processes #131

tomLandry opened this issue Nov 30, 2016 · 2 comments
Assignees

Comments

@tomLandry
Copy link

At the moment, only the log is available for failed processes. That log doesn't contain any information on inputs used. The inputs could be persisted to ease debugging or reproduction of the problem. The same logic could be applied for the "restart" option, even knowing it will probably fail again if no modification were applied to the implementations.

@tomLandry tomLandry changed the title Store the inputs usef for failed processes Store the inputs used for failed processes Nov 30, 2016
@cehbrecht
Copy link
Member

cehbrecht commented Nov 30, 2016

The inputs/outputs are taken from the lineage info in the wps response xml document. I thought the lineage info was only available in case of a successful process ... that is why these infos are missing.

But i have seen cases now when the wps answers with a failure message including the input lineage. So, i can add this to phoenix.

You can see the status document by clicking on "status location" for async jobs.

On the development branch of phoenix there is now a "View as XML" tab in the details view which shows the xml response document (both for sync and async):
https://mouflon.dkrz.de/monitor/details/df4090ed078549b183e4fdfc1f469070/xml

In cases where i don't get the lineage info i could store the "execute request" in the phoenix session.

As a developer you can see error messages in the pywps logs.

@cehbrecht cehbrecht self-assigned this Nov 30, 2016
@tomLandry
Copy link
Author

I would have labeled this issue as "improvement", don't think I have permission to do so. This is not really important, juste a note.

I've seen the "View as XML" on Mouflon. I'll fetch that soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants