-
Notifications
You must be signed in to change notification settings - Fork 683
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
Failed to assemble or send inherent data err=SendInherentDataTimeout #769
Comments
That warning is likely only a symptom of something else going wrong. Do you have any more details? Does this happen repeatedly? Only once? Something different that usual? Node recently updated? ... If it happens repeatedly, enabling debug logs for the parachain target would likely be of good help. Thanks! |
@eskimor could you point me to the parameter to enable parachain debug logs? Also, what do you mean by target? A parachain in particualr? |
@polkalegos you can either add a command like flag However, I strongly suspect that as with other issues you reported #817, this is like caused by memory corruption of some sorts. |
Since this is the third issue you posted here about weird crashes, lets make sure it is not on your side (cc @koute):
|
* Basic channel v3: blockchain updates (paritytech#766) * Remove message bundles from outbound channel * Remove MessageBundle from inbound channel contract * Rework inbound channel contract * Remove submitBatch * Fix basic channel tests * Fix outbound channel tests * Add explicit PartialEq * Remove TODO * Use checked_add to return an error on overflow * s/who/source_id/ * Basic channel v3: relayer updates (paritytech#769) * Remove message bundles from parachain relayer * s/account/sourceID/g (more or less) * Emit MessageDispatched event * Remove dispatchBatch * s/sourceId/sourceID/ * Formatting * Check remaining gas before dispatch * Remove redundant validation
* Create Cargo.toml * Move with-rocksdb-weights feature declaration to default Co-authored-by: Wei Tang <wei@that.world>
The node restarts without any specific reason, just the log in the title.
Memory usage ramps up during this event:
The text was updated successfully, but these errors were encountered: