-
Notifications
You must be signed in to change notification settings - Fork 297
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
Error code 500 Internal Server Error #760
Comments
scheduler STDOUT: |
Scheduler core.log (splits): |
Scheduler Logs for the peer x.y.z.5-1-ede4ce6a-8600-4f51-acf0-132bfd143d49. |
Is there any log from dfdaemon stdout or stderr ? |
Attached dfdaemon stdout log. |
Attached two cdn logs. |
alpha.6 dfdaemon log: alpha.6 dfdaemon stdout: |
alpha.6 scheduler log: alpha.6 scheduler stdout: |
alpha.6 cdn log: |
Full dfdaemon.log: scheduler gc log: |
Same issue. Please not the error comes for manifest and not for blob. dfdaemon log: scheduler log: cdn log: |
Bug report:
FATAL: Unable to handle oras://registry1.com/repo/project:tag uri: failed to get checksum for oras://amr-registry.caas.intel.com/repo/project:tag: while reading manifest: httpReaderSeeker: failed open: unexpected status code https://oras://registry1.com/repo/project/manifests/sha256:b4b80c5e7ca6344d501efaed5dd6a44181acbc7fbb5f4197031f06f2b87d54c2: 500 Internal Server Error - Server message: unknown: internal server error
Attached the client core log.
Expected behavior:
How to reproduce it:
Environment:
uname -a
):[core.log]
The text was updated successfully, but these errors were encountered: