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

again "Failed to get reply! The buffer was not large enough to complete the deserialize operation"' #14

Closed
phip1611 opened this issue Dec 23, 2020 · 4 comments
Assignees
Labels
OCP Netlink / OCP

Comments

@phip1611
Copy link
Collaborator

phip1611 commented Dec 23, 2020

I thought this issue is gone since Neli 0.5.0 .. but it still happens :( I don't know why it just started to appear again.
Similar to #9

Might be useful: jbaublitz/neli#110

Problem: Ovey device is created via OCP and in some cases the reply can't be deserialized... But I'm sure the kernel sends valid output..because it only happens inside neli if multiple messages has been sent.

@phip1611 phip1611 added the OCP Netlink / OCP label Dec 23, 2020
@phip1611 phip1611 self-assigned this Dec 23, 2020
@phip1611
Copy link
Collaborator Author

phip1611 commented Dec 23, 2020

I checked out the original PR branch and built libocp with it. Seems like it's helping me to further investigate issues. great!

@phip1611
Copy link
Collaborator Author

phip1611 commented Dec 23, 2020

okay most probably because if kernel panics when deleting an ovey device. I thought these errors are gone..

@phip1611
Copy link
Collaborator Author

hm.. not always. There are cases where neli can read the reply and cases where it can't read the reply.

@phip1611
Copy link
Collaborator Author

phip1611 commented Dec 23, 2020

I'm sure it is not a neli bug. I'm pretty sure I have a memory bug inside the kernel! I did 1000 requests/replies with OCP ECHO - everything fine @planetA. But as soon as I have OCP request that includes verbs it sometimes fails and sometimes not.
I probably have silent memory errors and this way sometimes the socket buffer (and other memory) gets corrupted.. :(

@phip1611 phip1611 closed this as completed Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCP Netlink / OCP
Projects
None yet
Development

No branches or pull requests

1 participant