Jump to content

XRP4bigDATA

Member
  • Content Count

    6
  • Joined

  • Last visited

1 Follower

About XRP4bigDATA

  • Rank
    Newbie

Contact Methods

  • Website URL
    https://xrp.4bigdata.eu

Profile Information

  • Gender
    Male
  • Interests
    metadata, data, databases, bigdata
  • Location
    Bratislava
  • Country
    Slovak Republic

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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, "expiratio´╗┐n": "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
  2. I'm running validator node in cluster of other two XRPL nodes. Why? It is stable and secure solution to get perfect access to the XRP ledger. And of course, as solid, stable and reliable partner we can later offer some paying services based on ledger. We would like to expand this revolution to Europe...
  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?
  4. super, we will monitor availability and upgrade as soon as we get it
  5. 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
  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
×
×
  • Create New...