Gopherine Posted October 6, 2020 Share Posted October 6, 2020 Hi, I installed rippled node running inside a container. Everything works fine apart from transaction, it just gets submitted and i get tesSuccess but is never validated. I have enabled history sharding with 50 gb and node size set to medium right now the docker image has only occuppied like 6.7 gb, I am inferring that this problem might be because it does not has complete history or is missing shards and transaction will only be validated properly after 50gb is downloaded or i dont know if i am doing something wrong here, below is my config - i am using https://github.com/WietseWind/docker-rippled/blob/master/Dockerfile this docker image and have edited the config file as below. Thanks in advance. # https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg # NOTE # # To accept connections on well known ports such as 80 (HTTP) or # 443 (HTTPS), most operating systems will require rippled to # run with administrator privileges, or else rippled will not start. [server] port_rpc_admin_local port_peer port_ws_admin_local #port_ws_public #ssl_key = /etc/ssl/private/server.key #ssl_cert = /etc/ssl/certs/server.crt [port_rpc_admin_local] port = 5005 ip = 0.0.0.0 admin = 0.0.0.0 protocol = http [port_peer] port = 51235 ip = 0.0.0.0 # alternatively, to accept connections on IPv4 + IPv6, use: #ip = :: protocol = peer [port_ws_public] port = 80 ip = 0.0.0.0 protocol = ws [port_ws_admin_local] port = 6006 ip = 0.0.0.0 admin = 0.0.0.0 protocol = ws [node_size] medium [node_db] type=NuDB path=/var/lib/rippled/db/nudb online_delete=32768 advisory_delete=0 # This is the persistent datastore for shards. It is important for the health # of the ripple network that rippled operators shard as much as practical. # NuDB requires SSD storage. Helpful information can be found at # https://xrpl.org/history-sharding.html [shard_db] path=/var/lib/rippled/db/shards/nudb max_size_gb=50 [database_path] /var/lib/rippled/db # This needs to be an absolute directory reference, not a relative one. # Modify this value as required. [debug_logfile] /var/log/rippled/debug.log [sntp_servers] time.windows.com time.apple.com time.nist.gov pool.ntp.org # To use the XRP test network # (see https://xrpl.org/connect-your-rippled-to-the-xrp-test-net.html), # use the following [ips] section: [ips] r.altnet.rippletest.net 51235 # File containing trusted validator keys or validator list publishers. # Unless an absolute path is specified, it will be considered relative to the # folder in which the rippled.cfg file is located. [validators_file] validators.txt # Turn down default logging to save disk space in the long run. # Valid values here are trace, debug, info, warning, error, and fatal [rpc_startup] { "command": "log_level", "severity": "warning" } # If ssl_verify is 1, certificates will be validated. # To allow the use of self-signed certificates for development or internal use, # set to ssl_verify to 0. [ssl_verify] 1 [ledger_history] 32768 Link to comment Share on other sites More sharing options...
Gopherine Posted October 7, 2020 Author Share Posted October 7, 2020 xrp LedgerHistory:ERR valid InboundLedger:WRN Want LedgerHistory:ERR Mismatch Err Built LedgerConsensus:WRN Network_Ops: WRN we are not running on the consensus ledger These are the above warnings i see in debug log Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now