rippled server - validator_list - expiration

[XRP4bigDATA 3]

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

 

[Sukrim 1,725]

Afaik that's part of the list you're using, not something you're setting. Unfortunately the format is undocumented afaik.

[XRP4bigDATA 3]

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

[nikb 4,060]

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.

[XRP4bigDATA 3]

super, we will monitor availability and upgrade as soon as we get it

[nikb 4,060]

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.

[XRP4bigDATA 3]

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?

[nikb 4,060]

The domain verification bit is, actually, unrelated. Let me kick the bot to reverify.

[XRP4bigDATA 3]

Hi friends, the same bug is back. As I mentioned, we built small cluster of rippled servers, one as validator (more info https://xrp.4bigdata.eu) and two proxy nodes. Everything fine. We are using the last stable version 1.2.2.

But this night validator stopped to validate again.  I found that the problem might be AGAIN in the expired list of validators.

"validator_list": {
                "count": 1,
                "expiration": "2019-Mar-19 00:00:00.000000000",
                "status": "active"
            }

It is important, that when using version 1.2.0, validator lists on all servers expired, but we are using 1.2.2 now and all stock (proxy nodes) servers are good - Validator_list expiration was refreshed and has value: "expiration": "2019-Apr-02 00:00:00.000000000".

But validator server validator_list was NOT updated and question is WHY ? The same version. The only difference is that:

- it is validator

- it uses only 2 peers - stock servers within cluster

Any advice ?

Jan

 

[mDuo13 2,303]

The only thing I can think of is that your validator is somehow unable to reach https://vl.ripple.com/ to download the updated validator list. (The previous bug was that servers would sometimes give up even trying to fetch the list; that should be fixed, but the symptom can occur if your server is still unable to get the list despite trying.)

From the validator server, are you able to connect to the site to fetch the list manually? For example:

wget https://vl.ripple.com/

If so, it should be possible to load the validator list from file as a temporary workaround. Here's an example from the PR that added that feature: https://github.com/ripple/rippled/pull/2744/files#diff-48a8459379995a830937c804745efe14R34

You'll still want to figure out why your validator isn't able to download the latest list (and switch it back to downloading the list automatically), though.

[XRP4bigDATA 3]

yes, from server there is no problem with

wget https://vl.ripple.com/

thanx..

[nikb 4,060]

Weird. I’m curious what the issue here is.