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

Computational node fails to upload files (after a re-run) #3230

Closed
elisabettai opened this issue Aug 2, 2022 · 5 comments
Closed

Computational node fails to upload files (after a re-run) #3230

elisabettai opened this issue Aug 2, 2022 · 5 comments
Assignees
Labels
bug buggy, it does not work as expected

Comments

@elisabettai
Copy link
Collaborator

Long story short

A computational service fails to upload the results, with:

Tue Aug 02 2022 15:28:03 GMT+0200 (Central European Summer Time) INFO 29cd40f5-a656-4434-8c9a-c327388425b2 ascent-runner: [sidecar] Task error:
The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. 

I am attaching the full logs from the logger. logs_ascent-runner_failedUploading.log

Some hints

The first time I run the service it run successfully, but the second time it failed uploading. I then re-tried to run and @sanderegg found in the database (file_meta_data table) that upload_expires_at was briefly filled in with the correct date, but then was overridden with NULL. The re-run also failed

Steps to reproduce

Based on what I did, I think we can reproduce it (on AWS prod) by:

  1. Add an ascent-runner node, run it with default input parameters
  2. Run it a second time

(When I actually got the error, I went back to the dashboard between 1 and 2.)

Your environment

osparc.io

@elisabettai elisabettai added the bug buggy, it does not work as expected label Aug 2, 2022
@elisabettai
Copy link
Collaborator Author

Small update: I've re-run again and it worked.

@sanderegg
Copy link
Member

@elisabettai shall we close this? is this still happening?

@sanderegg
Copy link
Member

@elisabettai can we close this or is it still happenning?

@sanderegg
Copy link
Member

@elisabettai I fixed an issue there maybe this is definitively fixed. can we close?

@sanderegg
Copy link
Member

closing this entry as stale and not reproducible

@sanderegg sanderegg closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug buggy, it does not work as expected
Projects
None yet
Development

No branches or pull requests

2 participants