XRP4bigDATA 0 Posted February 6 Hi friends, we built small cluster of rippled servers, one as validator (more info https://xrp.4bigdata.eu) and two proxy nodes. Everything was smooth and stable. But this night validator stopped to validate. I found that the problem might be in the expired list of validators. "validator_list": { "count": 1, "expiration": "2019-Feb-06 00:00:00.000000000", "status": "active" } I assumed that the list of validators and expiration date is periodically restored by server. It seems not. Restart of all servers helped, but it is not a solution. Next expiration date on all of them is now "expiration": "2019-Feb-13 00:00:00.000000000". I can't find any information about this. We want to do the utmost for a stable and reliable node. Thanx and have a nice day and greetings from europe. Jan Share this post Link to post Share on other sites
Sukrim 1,350 Posted February 6 Afaik that's part of the list you're using, not something you're setting. Unfortunately the format is undocumented afaik. Share this post Link to post Share on other sites
XRP4bigDATA 0 Posted February 6 hmm.. the documentation is brief and does not clarify more things but we used the recommended settings we are using an unmodified file validators.txt for the validator list - and it links to https://vl.ripple.com Share this post Link to post Share on other sites
nikb 3,727 Posted February 6 The behavior you describe is definitely a bug. The server should automatically refresh the lists that are defined in the configuration. The bug was recently discovered and a fix has already be made and will be included with the 1.2.0 release of rippled, which should be finalized early next week. 6 1 PhiGuy, XRP4bigDATA, Sukrim and 4 others reacted to this Share this post Link to post Share on other sites
XRP4bigDATA 0 Posted February 6 super, we will monitor availability and upgrade as soon as we get it Share this post Link to post Share on other sites
nikb 3,727 Posted February 6 11 minutes ago, XRP4bigDATA said: super, we will monitor availability and upgrade as soon as we get it Thanks! Apologies for the inconvenience. With 20/20 hindsight, a hotfix addressing this issue would also have been appropriate. But you know what they say: you live, you learn. 1 CryptoDrover reacted to this Share this post Link to post Share on other sites
XRP4bigDATA 0 Posted February 7 the fascinating consequence of this failure of the validator is the loss of domain verification xrp.4bigdata.eu (nHDB8VnzxPpvxm3sE4AEjARVmRm6ogQ7474okZVzcpu9AhVEWjHx) I do not understand the reason, there was only restart, no change of parameters. I have to ask for domain verification for validator again? Share this post Link to post Share on other sites
nikb 3,727 Posted February 10 The domain verification bit is, actually, unrelated. Let me kick the bot to reverify. 1 Tinyaccount reacted to this Share this post Link to post Share on other sites
