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

http://oda-dispatcher:8000 is not a valid url got from /call_back #558

Closed
dsavchenko opened this issue Jul 17, 2023 · 10 comments
Closed

http://oda-dispatcher:8000 is not a valid url got from /call_back #558

dsavchenko opened this issue Jul 17, 2023 · 10 comments

Comments

@dsavchenko
Copy link
Member

Just received it in Sentry. This never happened before.

UserError /call_back

UserError: http://oda-dispatcher:8000 is not a valid url. 
A valid url should be like `https://www.astro.unige.ch/mmoda/dispatch-data`, you might verify if, for example, a valid schema is provided, i.e. url should start with http:// or https:// .
Please check it and try to issue again the request
@dsavchenko
Copy link
Member Author

@volodymyrss @burnout87 any ideas?

@volodymyrss
Copy link
Member

any more info, which site even?

@dsavchenko
Copy link
Member Author

It's obviously in the French instance (I don't have others connected to my Sentry account).

The request looks legitimate

Query String
action done
file_name job_monitor.json
instrument_name fermi
job_id f68d919839198bb3
session_id MYD95576HWPDVD4E
time_original_request 1689608438.0057309
token [Filtered]
work_dir scratch_sid_MYD95576HWPDVD4E_jid_f68d919839198bb3

Dispatcher container is running for 42h, no such issues before

@volodymyrss
Copy link
Member

It's obviously in the French instance (I don't have others connected to my Sentry account).

oh but we connected different people to our collective sentries at different time, you might have suddenly gotten a message.

The request looks legitimate

Query String

action done
file_name job_monitor.json
instrument_name fermi
job_id f68d919839198bb3
session_id MYD95576HWPDVD4E
time_original_request 1689608438.0057309
token [Filtered]
work_dir scratch_sid_MYD95576HWPDVD4E_jid_f68d919839198bb3

Dispatcher container is running for 42h, no such issues before

this exception must be somewhere in the code. By the way I do not seem to get "ready" emails so maybe "ready" callback always fails with some similar exception. Then it's strange you only got the alert one. Do you get ready emails from this instance?

@dsavchenko
Copy link
Member Author

No, I don't get "ready" emails. We have an issue on it, @burnout87 also noticed it (BTW, in which instance?)

@volodymyrss
Copy link
Member

please refer to the issue and to where @burnout87 noticed it.

@dsavchenko
Copy link
Member Author

Here #553 (comment)_

@burnout87
Copy link
Collaborator

I noticed a weird behavior on the staging dispatcher, in particular completion emails for images are not sent. Whereas for light curves and spectra, behavior is as expected.

@volodymyrss
Copy link
Member

it's not likely that this is related but maybe. Might have something to do with size of the output. Anyway since "ready" status is achieved means that the callback message arrives. Just that the email is not sent in this case, which should trigger an exception.

@dsavchenko
Copy link
Member Author

This is fixed by oda-hub/oda_api#220

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

No branches or pull requests

3 participants