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

SerializationError: failed to unmarshal error message #5649

Open
solracsf opened this issue Feb 11, 2025 · 11 comments
Open

SerializationError: failed to unmarshal error message #5649

solracsf opened this issue Feb 11, 2025 · 11 comments
Assignees
Labels
kind/bug Something isn't working

Comments

@solracsf
Copy link
Contributor

solracsf commented Feb 11, 2025

<WARNING>: Delete data blocks of slice 4745074 (449 bytes): SerializationError: failed to unmarshal error message
#011status code: 404, request id: , host id:
caused by: UnmarshalError: failed to unmarshal error message
#01100000000  3c 68 74 6d 6c 3e 3c 62  6f 64 79 3e 3c 68 31 3e  |<html><body><h1>|
00000010  34 30 34 20 4e 6f 74 20  46 6f 75 6e 64 3c 2f 68  |404 Not Found</h|
00000020  31 3e 0a 54 68 65 20 72  65 73 6f 75 72 63 65 20  |1>.The resource |
00000030  63 6f 75 6c 64 20 6e 6f  74 20 62 65 20 66 6f 75  |could not be fou|
00000040  6e 64 2e 0a 3c 2f 62 6f  64 79 3e 3c 2f 68 74 6d  |nd..</body></htm|
00000050  6c 3e 0a                                          |l>.|
caused by: expected element type <Error> but have <html> [base.go:2177]
<WARNING>: Upload chunks/4/4744/4744557_2_4194304: SerializationError: failed to unmarshal error message
#011status code: 404, request id: , host id:
caused by: UnmarshalError: failed to unmarshal error message
#01100000000  3c 68 74 6d 6c 3e 3c 62  6f 64 79 3e 3c 68 31 3e  |<html><body><h1>|
00000010  34 30 34 20 4e 6f 74 20  46 6f 75 6e 64 3c 2f 68  |404 Not Found</h|
00000020  31 3e 0a 54 68 65 20 72  65 73 6f 75 72 63 65 20  |1>.The resource |
00000030  63 6f 75 6c 64 20 6e 6f  74 20 62 65 20 66 6f 75  |could not be fou|
00000040  6e 64 2e 0a 3c 2f 62 6f  64 79 3e 3c 2f 68 74 6d  |nd..</body></htm|
00000050  6c 3e 0a                                          |l>.|
caused by: expected element type <Error> but have <html> (try 1) [cached_store.go:407]
  • JuiceFS 1.2.3
  • Ceph S3
@solracsf solracsf added the kind/bug Something isn't working label Feb 11, 2025
@zhijian-pro
Copy link
Contributor

What is the Ceph version ?

@solracsf
Copy link
Contributor Author

Sorry, I don't have that information, it's a managed service.

@zhijian-pro
Copy link
Contributor

Is this a public cloud hosting platform? It seems to be a compatibility issue, we'd better have an environment to determine the cause.

@solracsf
Copy link
Contributor Author

Yes it is : https://www.hetzner.com/storage/object-storage/
What else do you need ?

@zhijian-pro
Copy link
Contributor

I tried to sign up, but the company immediately deactivated my account, probably for regional reasons.
The above issue seems to be related to the s3 compatibility of ceph provided by the cloud vendor, and it is possible to invoke the put-object interface using the aws cli tool to see if the same error occurs.

@solracsf
Copy link
Contributor Author

solracsf commented Feb 13, 2025

If you need a bucket, please let me know your email address.
FYI, all juicefs objbench test pass

@zhijian-pro
Copy link
Contributor

Ok,my email address is [email protected]

@zhijian-pro
Copy link
Contributor

zhijian-pro commented Feb 14, 2025

Image

Is this a problem of stability? I mean, every time I put it or delete it. I did not reproduce the problem.

@solracsf
Copy link
Contributor Author

I saw these warnings once in 10 days.

@zhijian-pro
Copy link
Contributor

Can you repeat the problem now?

@zhijian-pro zhijian-pro self-assigned this Feb 14, 2025
@solracsf
Copy link
Contributor Author

No. Maybe the service was somehow unavailable, returning plain HTML 404, and juicef was unable to parse it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants