Jump to content

Server Misreporting State / Additional Health Check Ideas


MrDrip
 Share

Recommended Posts

This morning I encountered an issue where my Rippled node appeared to be in a valid state but seemed to be missing considerable amounts of data.

I consider my node to be "healthy" if it has a validated ledgers, and the state is "full". Once the server has reached this state I allow my app to start processing transactions. However this morning, my app stopped receiving withdrawals (txnNotFound) and stopped send withdrawals ( noCurrent). The server was reporting that it was keeping in sync with the network, but when a transaction was queried it was not there. I restarted the node and it then entered the expected "connected" state and did not print that it had validated ledgers.

Is this expected? and if so does anyone know of any additional health checks I could perform to determine whether my node is struggling and restart automatically.

Any help much appreciated.

PS.

I don't consider myself a rippled expert by any mean but i have been running and maintaining a node for 2+ years as part of my job. I have certainly had my ups and downs with rippled but I have had periods of months with great reliability but since the upgrade to 1.8 I have definitely noticed decreased stability.

Im currently running a medium sized node on what I consider to be fairly high end hardware... I know a lot of the time the answer it to give the node more resources but i am hesitant to throw more money at it since it has been managing fine until the upgrade.

Link to comment
Share on other sites

Hi @MrDrip, I'm not really technically qualified to know the exact answers  but I can tell you that ~ the same timeframe, the 2 public Ripple XRPL nodes fell out of sync for about 5 hours, resulting in problems. The upshot is that if you connect to S1, S2 you may want to change them?  Hope this helps.

The XUMM developers talk about it in this thread:

 

Edited by WrathofKahneman
Link to comment
Share on other sites

At another point they discussed that certain Ripple nodes should not be used for productive environments (Ripple themselves write this). Instead, exchanges, coin issuers etc. should rely on their own nodes.
These problems might be annoying at first but I think will help further decentralize the ledger.
These entities should have enough incentive to run an own node (for various reasons). One has to hope that in the future trustworthy projects and exchanges will own their own nodes and not rely on some test nodes setup by Ripple.

Link to comment
Share on other sites

Thanks @WrathofKahneman for that info. That makes me feel slightly better that i was not the only one experiencing difficulties.

 

@Triceratops Yes I agree with you. I've used the public apis in the past, but it's not suitable for production and you will get rate limited if you process a significant of transactions. I have been running my own node since February :)

 

Thanks to everyone who responded.

Link to comment
Share on other sites

It's hard to say, because all the network has some problems right now. I hope someone was able to save all the history correctly.

I personally had to restart my node and it's not able to get in sync anymore (in 24h it wasn't able to initialize). So I shut it down waiting for more info.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share



×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.