You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple small issues one can run into when running a node, but there is no documentation on how to handle those issues. One issue where i ran into today is the "too many open files" error which kills the daemon. The solution appeared to be quite easy, namely increase the max open file limit, but it was hard to find.
Troubleshooting node issues can be hard and is not well documented across the ecosystem.
Proposal
As Osmosis' docs are one of the most elaborate out there, it would be great to have a node troubleshooting page as part of the docs. Just make a single item, for example the max open file limit, and then add a link where people can suggest issues. Maybe some webscrapping would also help finding common issues.
The text was updated successfully, but these errors were encountered:
Summary
There are multiple small issues one can run into when running a node, but there is no documentation on how to handle those issues. One issue where i ran into today is the "too many open files" error which kills the daemon. The solution appeared to be quite easy, namely increase the max open file limit, but it was hard to find.
this eventually helped me: axelarnetwork/axelarate-community#257
Problem Definition
Troubleshooting node issues can be hard and is not well documented across the ecosystem.
Proposal
As Osmosis' docs are one of the most elaborate out there, it would be great to have a node troubleshooting page as part of the docs. Just make a single item, for example the max open file limit, and then add a link where people can suggest issues. Maybe some webscrapping would also help finding common issues.
The text was updated successfully, but these errors were encountered: