Search the Community

Hi, I run a rippled node. When I run the command 'rippled book_offers BTC/rJHygWcTLVpSXkowott6kzgZU6viQSVYM1 5852534849420000000000000000000000000000/rN3EeRSxh9tLHAUDmL7Chh3vYYoUafAyyM' (this is the XRSHIB currency) I get the following error: {'error': 'invalidParams', 'error_code': 31, 'error_message': "Invalidcurrency/issuer'5852534849420000000000000000000000000000/rN3EeRSxh9tLHAUDmL7Chh3vYYoUafAyyM'", 'rpc': {'method': 'book_offers', 'params': ['BTC/rJHygWcTLVpSXkowott6kzgZU6viQSVYM1', '5852534849420000000000000000000000000000/rN3EeRSxh9tLHAUDmL7Chh3vYYoUafAyyM']}, 'status': 'error'} I also tried to replace it with the currency code "XRSHIB". This does not work either. For other pairs it works perfectly fine. Anyone know what I am doing wrong? When I run it in the websocket-api-tool of xrpl.org it also works fine. Thanks!

Hi everyone, To make test API requests to the rippled server easier, I've created a Postman Collection for the JSON-RPC API with many of the methods. It has most of the Public APIs and just some of the Admin APIs so far. It includes the request bodies from https://xrpl.org so it's quick to make API calls and change parameters like account addresses. The rippled server JSON-RPC URL is set via a Postman environment variable so it's easy to switch to any server you want. I'm still adding to it but wanted to share it to get feedback. If you have any questions, please respond here or post to GitHub Issues. You can find it here: https://github.com/goxrp/rippled-postman Here's a screenshot in the Postman client:

Hi everyone!, I'm experimenting with the rippled software server and its configuration options. I stumbled upon the file src/ripple/protocol/SystemParameters.h and I saw a a constant function that sets the currency code (systemCurrencyCode) and it made me wonder, is it possible to change the currency code to a custom one (like, for example XYZ)? Since XRP is not a "currency" (as it would be any other issued currency like ETH, USD, etc...) in the ledger, does this make any sense at all? Would I need to perform this change in the source code of the server and recompile it instead of using this configuration value?. I have been testing it in a Stand Alone server running in my local machine and, although the server works fine as usual, I haven't found a way to check which currency code is the node using, if it's XRP or XYZ. I'm sorry if the question is too stupid, but I haven't seen any documentation about this topic and I'm an absolute beginner with this technology. Thank you very much in advance!

Rather than continue to derail TWarden's UNL security blanket thread, I decided it would be a good idea to share knowledge and collect information on people's experiences with running rippled. We can see what kinds of specs and settings people have had success or problems with, and go from there. I'll start with my own experience: I have a home desktop PC which I use for my daily computing needs. I built the computer in 2009 and have upgraded it slightly over the years. Since late January 2016, I've been running rippled as a validator more or less continuously. System specs: CPU: 2.66GHz Intel Core i7 "Bloomfield" CPU RAM: 16GB Corsair XMS3 (what can I say, it was a Black Friday sale!) Disks: System partition is on a 80GB Intel X-25M SSD. My rippled's database is on my 2x3TB 7200 RPM disks in software RAID1 using mdadm. I think they're Hitachi-branded? OS: Arch Linux x86_64 (latest Linux kernel, which I've updated a few times in the time I've been running the validator) Network: I'm wired to a cheapo 10/100MBit Netgear ethernet switch and use my house's residential broadband. Settings: I'm using the default settings from the rippled-example.cfg, except for adding my validation seed. The automatic online delete seems to work just fine. Maintenance: Basically, the only maintenance I do is to upgrade to a new version of rippled when one comes out. So far I haven't had any problems with disk space: rippled seems to purge old ledgers often enough to stay within a reasonable amount of disk usage. Usage patterns: I occasionally run RPC commands against rippled for testing / work purposes, but by and large the daemon is dedicated to validating. I do use the machine for my daily computing and I've noticed that the process tends to use up as much RAM as it can when my computer is idle, but it quickly yields it to other programs when I'm actively using the computer. There hasn't been any major adverse effect on my general computing performance. Meanwhile, my validation agreement percentage has been hovering around 98% with few exceptions during that time.

XRP Ledger core server, rippled, v1.5.0 has been released! You can read the full v1.5.0 Release Announcement on the XRPL Blog. Also, we've published a whole bunch of changes to the documentation on xrpl.org, including: Known Amendments has the new protocol amendments listed and statuses updated: https://xrpl.org/known-amendments.html New fields in the response to the submit method: https://xrpl.org/submit.html#response-format server_info method updated with more recent examples and updated time fields: https://xrpl.org/server_info.html New manifest method: https://xrpl.org/manifest.html New validator_info method: https://xrpl.org/validator_info.html New fields in tx method providing for more robust Not Found errors: https://xrpl.org/tx.html#not-found-response Updated account_channels method to reflect bug fixes: https://xrpl.org/account_channels.html Instructions on how to enable the new gRPC API on your rippled server: https://xrpl.org/configure-grpc.html New warnings in API responses if your server is, or is about to be, amendment blocked: https://xrpl.org/response-formatting.html#api-warnings Request Formatting updated with better formatting and new API Versioning information: https://xrpl.org/request-formatting.html Other very minor cleanup and corrections Let me know if you have any questions or comments, and enjoy the new version!

I work in an exchange and we run one rippled node for signing our transactions, node was pretty much stable when running last versions, prior than 1.1.0 now we are running version 1.3.1 and its getting worst every new release. I know the hunger of rippled for disk io, but it was mandatory that we used encrypted disks. Our config does not differ from most common here, but we are currently using the db/file config below: [node_db] type=rocksdb path=/home/xrpd/db/rocksdb open_files=3000 filter_bits=12 cache_mb=512 file_size_mb=64 file_size_mult=2 online_delete=20000 That config used to satisfy our needs for having a historical of almost one week within our node, but nowadays rippled will consume lots of cpu, like sometimes it will drag entire server to an almost unresponsive level, needing admin action. Currently server wont stay stable for one week, requiring admin to clear its db and resync it again. cpu : Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz ram : 131981704 debian : bullseye/sid kernel 5.2.9-2 (2019-08-21) x86_64 GNU/Linux I am not responsible for the setup, I just need to maintain it working, thus my question: Could this load be related to a heavy io demand in a encrypted disk space ? I would be glad to provide checks and results of any request to be able to clarify conditions and create a good basement to the head admins. We are already running a tiny server, we used to run it huge, memory is not an issue, but cpu load thanks for any support given. delphus

I am new to rippled and am trying to learn what the difference is between a stock rippled node and a validating node. As I've read, a Stock server follows the network with a local copy of the ledger whereas a Validating server participates in consensus (and does everything a stock server does, too). I am currently running an instance of rippled and have run a performance profiler on the node, first on the non-validating node and then again when the node is running as a validator. Looking through the results, it seems that even when not running as a validator, the server makes calls to functions associated with consensus (ripple::RCLConsensus::Adaptor::doAccept, ripple::RCLConsensus::Adaptor::buildLCL, etc.) If a stock server is not supposed to be participating in consensus, why would there be calls to these functions? Could anyone explain to me why this is?

I am trying to understand the difference between stock rippled servers, validators, and client-applications when it comes to signing. When looking through the documentation in dev portal, it states that Cryptographic key pairs are always tied to a specific signing algorithm. Further, one can specifically choose the key type when using the wallet_propose method to choose which cryptographic signing algorithm to use to derive the keys (secp256k1 or ed25519). However, when running a rippled server or validator, is there such an option when creating key pairs? What signing algorithm is used when sending ledgers and ledger proposals when running as a rippled server or a validator?

Hello im using testnet to validate my transaction, transaction : {"transaction":"ECAB482EB34177FA1B1E6C724F038C42308004B1F307A169FAEA88C825E11642","command":"tx","id":0} Response : {id=0, status='success', errorMessage='null', result=TxResult{validated=false}} Im using websocket , method 'tx' to check. Can i somehow figure out what the problem is? Im connected to wss://s.altnet.rippletest.net:51233 ,address i use is rKHDh61BpcojAoiATgJgDaVwdSJ64fGNwF. Can someone help a bit ?:) Fee is at 1 000 000 drops. This is the transaction blob 1200002200000000240000000061D4838D7EA4C680000000000000000000000000005553440000000000C882FD6AB9862C4F90E57E1BA15C248CABAD5BF96840000000000F42407321033BF063167F21FF6C01045B4E2F03F519879B552D2611F0E885E01F08C88D15247446304402202E90609AAFBF4C105408CFF2377D48085879BEE3C7DE57AF125F73926284362A022002D7A487F5929F9A3E1050FC2B5D6AE1DD5384647AD1ABF6D322765F0ABE0A498114C882FD6AB9862C4F90E57E1BA15C248CABAD5BF983148DC6B336C7D3BE007297DB086B1D3483DEA24C2A

What are the incentive at the moment to run a validator on XRP mainnet? Can I run it without the ~17TB of the block history installed localy?

Hi All, How long does a Rippled validator check process take usually? I sent my request to Ripple in June, but it is still unverified and I didn't get any email what the issue is (if there is any) ? Regards, Pal

I am facing an issue with my local ripple server. I have setup the ripple server in my system as local. So its running under localhost or 127.0.0.1:6006. As I tried to connect the ripple server using ripple-api I am getting Socket hangup issue as in below error. While running rippled server with my local IP address (127.0.0.1:6006) is not connecting it's throwing [NotConnectedError(socket hang up,{Error:Socket hang up})] and [RippledNotInitilizedError(RippledNotInitilized)] const RippleAPI = require('ripple-lib').RippleAPI; const api = new RippleAPI({ server: 'wss://127.0.0.1:6006' // my Own local rippled server }); Please find the attachment for error details

hi, i'm installing rippled on ubuntu with alien: 1.I run this commands "sudo apt-get update", "sudo apt-get install yum-utils alien" then alien installed fine. 2.while I Installing Ripple RPM Repository with "sudo rpm -Uvh https://mirrors.ripple.com/ripple-repo-el7.rpm" I getting error like "RPM should not be used directly install RPM packages, use Alien instead!" 3.so I tried to install RPM packages with command "sudo alien package.rpm" It shows "File "package.rpm" not found" I didn't found any .rpm files in alien folder but in that have .pm files only please lookup below what I get: chandu@ubuntu:~$ sudo rpm -Uvh https://mirrors.ripple.com/ripple-repo-el7.rpm [sudo] password for chandu: rpm: RPM should not be used directly install RPM packages, use Alien instead! rpm: However assuming you know what you are doing... Retrieving https://mirrors.ripple.com/ripple-repo-el7.rpm error: skipping https://mirrors.ripple.com/ripple-repo-el7.rpm - transfer failed chandu@ubuntu:~$ sudo alien package.rpm File "package.rpm" not found. chandu@ubuntu:~$ anyone can please suggest me how to do resolve these issues thanks.

https://ripple.com/dev-blog/rippled-version-0-90-1/ Hotfix release that patches some crash bugs (including several reported by Guido Vranken, whose work is impressive). No new features or other changes. Along with the release itself, Ripple is starting to vote in favor of the Checks, DepositAuth, and fix1513 amendments, so expect those to turn on in 2 weeks. (Note to self: update the "Known Amendments" page with the updated expected time)

Is there a RESTful API that I can curl in rippled? I want to do like this with my rippled. ``` curl myrippled_ip/v2/transactions ```

Hi everyone! First off, let me apologize for cross-posting. I know this is a major faux pas, but realize now that "Problem Solving" was the wrong place. Anyhow... I am brand new to Ripple in general, but a friend of mine has watched it quite closely. He has tasked me with running our own rippled instance. Really, my goal at this point is to be able to connect to it from a local ripple-lib script over WSS and query account info -- that's all. I have rippled installed and as far as I can tell have a valid configuration, such that it does run, however the process is constantly being killed and restarted. The response from my script upon api.connect vacillates from garden-variety "NotConnectedError" (when the process is restarting) to "[RippledNotInitializedError(Rippled not initialized)]" (when it is briefly running). My environment is Ubuntu 16.04.1 on a very cheap Digitalocean droplet. I fully realize I will need a more powerful VPS if I want a working, live instance, but I would assume something basic is ok for testing. Please correct me if I am wrong on this. My config as of now is: [server] port_rpc_admin_local port_peer port_ws_admin_local port_ws_public [port_rpc_admin_local] port = 5006 ip = 127.0.0.1 admin = 127.0.0.1 protocol = http [port_peer] port = 51235 ip = 0.0.0.0 protocol = peer [port_ws_admin_local] port = 6006 ip = 127.0.0.1 admin = 127.0.0.1 protocol = ws [port_ws_public] port = 5005 ip = my.ip.addr protocol = wss ssl_key = /etc/opt/ripple/key.pem ssl_cert = /etc/opt/ripple/cert.pem #------------------------------------------------------------------------------- [node_size] medium [node_db] type=RocksDB path=/var/lib/rippled/db/rocksdb open_files=2000 filter_bits=12 cache_mb=256 file_size_mb=8 file_size_mult=2 online_delete=2000 advisory_delete=0 [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 [sntp_servers] time.windows.com time.apple.com time.nist.gov pool.ntp.org # Where to find some other servers speaking the Ripple protocol. # [ips] r.ripple.com 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": "info" } # 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] 0 A log of when I run rippled with "--fg --net" is below (it's long....sorry): 2018-Jan-08 00:45:04 JobQueue:NFO Auto-tuning to 3 validation/transaction/proposal threads. 2018-Jan-08 00:45:04 Amendments:DBG Amendment C6970A8B603D8778783B61C0D445C23D1633CCFAEF0D43E7DBCD1521D34BD7C3 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 740352F2412A9909880C23A559FCECEDA3BE2126FED62FC7660D628A06927F11 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 532651B4FD58DF8922A49BA101AB3E996E5BFBF95A913B3E392504863E63B164 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment E2E6F2866106419B88C50045ACE96368558C345566AC8F2BDF5A5B5587F0E6FA is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 07D43DCE529B15A10827E5E04943B496762F9A88E3268269D69C44BE49E21104 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 86E83A7D2ECE3AD5FA87AB2195AE015C950469ABF0B72EAACED318F74886AE90 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 3012E8230864E95A58C60FD61430D7E1B4D3353195F2981DC12B0C7C0950FFAC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment CC5ABAE4F3EC92E94A59B1908C2BE82D2228B6485C00AFF8F22DF930D89C194E is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment B4D44CC3111ADD964E846FC57760C8B50FFCD5A82C86A72756F6B058DDDF96AD is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 6C92211186613F9647A89DFFBAB8F94C99D4C7E956D495270789128569177DA1 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment B9E739B8296B4A1BB29BE990B17D66E21B62A300A909F25AC55C22D6C72E1F9D is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 1D3463A5891F9E589C5AE839FFAC4A917CE96197098A1EF22304E1BC5B98A454 is supported. 2018-Jan-08 00:45:04 OrderBookDB:DBG Advancing from 0 to 3 2018-Jan-08 00:45:04 OrderBookDB:DBG OrderBookDB::update> 2018-Jan-08 00:45:04 OrderBookDB:DBG OrderBookDB::update< 0 books found 2018-Jan-08 00:45:04 ValidatorList:DBG Loading configured trusted validator list publisher keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loaded 0 keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loading configured validator keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loaded 5 entries 2018-Jan-08 00:45:04 ValidatorSite:DBG Loading configured validator list sites 2018-Jan-08 00:45:04 ValidatorSite:DBG Loaded 0 sites 2018-Jan-08 00:45:04 NodeObject:DBG NodeStore target size set to 131072 2018-Jan-08 00:45:04 NodeObject:DBG NodeStore target age set to 120000000000 2018-Jan-08 00:45:04 TaggedCache:DBG LedgerCache target size set to 256 2018-Jan-08 00:45:04 TaggedCache:DBG LedgerCache target age set to 180000000000 2018-Jan-08 00:45:04 TaggedCache:DBG TreeNodeCache target size set to 512000 2018-Jan-08 00:45:04 TaggedCache:DBG TreeNodeCache target age set to 90000000000 2018-Jan-08 00:45:04 NetworkOPs:NFO Consensus time for #3 with LCL 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 2018-Jan-08 00:45:04 ValidatorList:DBG 5 of 5 listed validators eligible for inclusion in the trusted set 2018-Jan-08 00:45:04 ValidatorList:DBG Using quorum of 3 for new set of 5 trusted validators 2018-Jan-08 00:45:04 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:04 LedgerConsensus:NFO Consensus mode change before=observing, after=observing 2018-Jan-08 00:45:04 NetworkOPs:DBG Initiating consensus engine 2018-Jan-08 00:45:04 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5006, admin IPs:127.0.0.1, http) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_ws_public' (ip=my.ip.addr:5005, wss) 2018-Jan-08 00:45:04 Application:FTL Startup RPC: { "command" : "log_level", "severity" : "info" } 2018-Jan-08 00:45:04 Application:FTL Result: {} 2018-Jan-08 00:45:04 PeerFinder:NFO Opening database at '/var/lib/rippled/db/peerfinder.sqlite' 2018-Jan-08 00:45:04 PeerFinder:NFO Opened version 4 database 2018-Jan-08 00:45:04 PeerFinder:NFO Bootcache loaded 187 addresses 2018-Jan-08 00:45:04 Application:NFO Application starting. Version is 0.80.2 2018-Jan-08 00:45:04 PeerFinder:NFO Logic added 0 new addresses from config: r.ripple.com 51235 2018-Jan-08 00:45:05 NetworkOPs:NFO STATE->connected 2018-Jan-08 00:45:05 NetworkOPs:NFO Node count (0) is sufficient. 2018-Jan-08 00:45:05 Peer:NFO [011] Public Key: n9KiJ4JHhajZ3mQ2k29ekz1ixnDYaQdF6bNi2hiKDhRM9nhwaLfW 2018-Jan-08 00:45:05 Peer:NFO [011] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.239.120.20:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [014] Public Key: n9MXY1xfS1VWmazwoYc98zvS28eVu1RQcYhWNKmzqxHd56oeRHQC 2018-Jan-08 00:45:05 Peer:NFO [014] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 52.55.102.204:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [010] Public Key: n9LGt2t1h1P76SnG86sEBTGdT6GrfxcT23KZ4nZX7xbGDYu3Y8Fc 2018-Jan-08 00:45:05 Peer:NFO [010] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.201.251.148:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [009] Public Key: n94KWZ9yJNJhaSqnn1S4K7Kna7ciaVBpjrqgHHyBM6g6NfgRAXT5 2018-Jan-08 00:45:05 Peer:NFO [009] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 184.72.137.59:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [019] Public Key: n9MqFgf89C1Q81rUXmunZjhFr1sZwaaQYoknVzTVwNC9ky9u2Mxb 2018-Jan-08 00:45:05 Peer:NFO [019] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.229.128.152:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [012] Public Key: n9Jt8awsPzWLjBCNKVEEDQnw4bQEPjezfcQ4gttD1UzbLT1FoG99 2018-Jan-08 00:45:05 Peer:NFO [012] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 52.90.42.69:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [013] Public Key: n94hKvqUffbA2cY49wz2Q7X2JoxtFW9o4dcWi6CSzUfXDTt3MWEi 2018-Jan-08 00:45:05 Peer:NFO [013] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.201.105.122:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [006] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [002] Public Key: n9KJb7NMxGySRcjCqh69xEPMUhwJx22qntYYXsnUqYgjsJhNoW7g 2018-Jan-08 00:45:05 Peer:NFO [002] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 54.84.21.230:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [018] Public Key: n9LnqwvUxFBUdnS1JzbziohwVium9EkYL5i7TuTx2TvPSskPPcVs 2018-Jan-08 00:45:05 Peer:NFO [018] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 169.54.2.157:51235 with 1 success 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #1 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #2 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #3 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #4 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #5 2018-Jan-08 00:45:05 Peer:NFO [008] Public Key: n94rE1SydpHTvJ4NyX9vC1cdeDmYP5nQSXTyeMnLh8jMJSRdcy9Q 2018-Jan-08 00:45:05 Peer:NFO [008] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 54.86.175.122:51235 with 33 successes 2018-Jan-08 00:45:05 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:05 Peer:NFO [017] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [005] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [001] Public Key: n9JAeNYjfb1Uzf5RHRpvDbYTvVNgPWiUfPUhdDtakQ1yXJ32n51c 2018-Jan-08 00:45:05 Peer:NFO [001] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 184.173.45.38:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [020] Public Key: n9MGChK9EgiCBM6s15EwF9d6m4LWZHh1UnJcgr16kQr4xBpx71fS 2018-Jan-08 00:45:05 Peer:NFO [020] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 198.11.206.6:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [004] Public Key: n9LieQkojpM1wsqman9d8jxVXrLxRh8RAmwv5rDvC5ea3kxnEVUn 2018-Jan-08 00:45:05 Peer:NFO [004] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 198.11.206.26:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [016] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:06 Peer:NFO [003] Public Key: n9MT5EjnV912KGuBUqPs4tpdhzMPGcnDBrTuWkD9sWQHJ1kDcUcz 2018-Jan-08 00:45:06 Peer:NFO [003] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 54.186.248.91:51235 with 33 successes 2018-Jan-08 00:45:06 Peer:NFO [007] Public Key: n9JySgyBVcQKvyDoeRKg7s2Mm6ZcFHk22vUZb3o1HSosWxcj9xPt 2018-Jan-08 00:45:06 Peer:NFO [007] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 54.186.73.52:51235 with 33 successes 2018-Jan-08 00:45:06 LedgerConsensus:WRN View of consensus changed during open status=open, mode=observing 2018-Jan-08 00:45:06 LedgerConsensus:WRN 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 to 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:06 LedgerConsensus:WRN { "accepted" : true, "account_hash" : "183D5235C7C1FB5AE67AD2F6CC3B28F5FB86E8C4F89DB50DD85641A96470534E", "close_flags" : 0, "close_time" : 568687500, "close_time_human" : "2018-Jan-08 00:45:00", "close_time_resolution" : 30, "closed" : true, "hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "ledger_hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "ledger_index" : "2", "parent_close_time" : 0, "parent_hash" : "AB868A6CFEEC779C2FF845C0AF00A642259986AF40C01976A7F842B6918936C7", "seqNum" : "2", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:06 LedgerConsensus:WRN Need consensus ledger 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:06 LedgerConsensus:NFO Consensus mode change before=observing, after=wrongLedger 2018-Jan-08 00:45:06 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:06 Peer:NFO [015] Public Key: n9KybMFrer7erpQDh58epdQkQga3pSaVYhD855h4gTkHtMUGVMx2 2018-Jan-08 00:45:06 Peer:NFO [015] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 52.78.78.122:51235 with 1 success 2018-Jan-08 00:45:07 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Proposers:5 nw:50 thrV:2 thrC:4 2018-Jan-08 00:45:08 LedgerConsensus:NFO Position change: CTime 568687501, tx 850CD9248733D95D8B3A79F452966CBCDFB4AAF01E48FCDD5B56EF9E943DF4A2 2018-Jan-08 00:45:08 LedgerConsensus:NFO Converge cutoff (5 participants) 2018-Jan-08 00:45:08 LedgerConsensus:NFO CNF buildLCL CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:08 NetworkOPs:WRN We are not running on the consensus ledger 2018-Jan-08 00:45:08 NetworkOPs:NFO Our LCL: { "accepted" : true, "account_hash" : "A0D5E308F7D3104D15CC4D73E6C0E88C17073FEF30F3AE9C09AB4A214A9390B4", "close_flags" : 0, "close_time" : 568687501, "close_time_human" : "2018-Jan-08 00:45:01", "close_time_resolution" : 30, "closed" : true, "hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "ledger_hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "ledger_index" : "3", "parent_close_time" : 568687500, "parent_hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "seqNum" : "3", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:08 NetworkOPs:NFO Net LCL 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:08 NetworkOPs:NFO Consensus time for #4 with LCL CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:08 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:08 LedgerConsensus:NFO Entering consensus with: 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 2018-Jan-08 00:45:08 LedgerConsensus:NFO Correct LCL is: 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:09 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:09 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LedgerConsensus:NFO Proposers:5 nw:50 thrV:2 thrC:4 2018-Jan-08 00:45:10 LedgerConsensus:NFO Position change: CTime 568687502, tx 850CD9248733D95D8B3A79F452966CBCDFB4AAF01E48FCDD5B56EF9E943DF4A2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Converge cutoff (5 participants) 2018-Jan-08 00:45:10 LedgerConsensus:NFO CNF buildLCL 11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149 2018-Jan-08 00:45:10 NetworkOPs:WRN We are not running on the consensus ledger 2018-Jan-08 00:45:10 NetworkOPs:NFO Our LCL: { "accepted" : true, "account_hash" : "B0FD2544671D7B6FF68C11E316B61FAD2C00357D6B264835D28DB4AFD0596329", "close_flags" : 0, "close_time" : 568687502, "close_time_human" : "2018-Jan-08 00:45:02", "close_time_resolution" : 30, "closed" : true, "hash" : "11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149", "ledger_hash" : "11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149", "ledger_index" : "4", "parent_close_time" : 568687501, "parent_hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "seqNum" : "4", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:10 NetworkOPs:NFO Net LCL BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 NetworkOPs:NFO Consensus time for #5 with LCL 11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149 2018-Jan-08 00:45:10 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:10 LedgerConsensus:WRN Need consensus ledger BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Entering consensus with: CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:10 LedgerConsensus:NFO Correct LCL is: BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LoadMonitor:WRN Job: processLedgerData run: 2058ms wait: 0ms 2018-Jan-08 00:45:11 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger Killed If I run: ps -eo pid,comm,lstart,etime,time,args | grep rippled I can see: 22497 rippled: #142 Mon Jan 8 00:12:37 2018 30:29 00:00:00 /opt/ripple/bin/rippled --net 25235 rippled: main Mon Jan 8 00:43:02 2018 00:04 00:00:00 /opt/ripple/bin/rippled --net The duration of the main process never exceeds 0:15 or so, which strikes me as the root issue, however the numbered child process is fine. **It is also worth noting that if I run rippled in standalone mode, this issue doesn't occur, but then I am obviously unable to query any account info.** I've dug this forum and others for possible solutions as to why I would be seeing this, but I continue to hit dead ends. If anybody here has any ideas for what to look at, I would be incredibly grateful! Thank you! - Johnny

Hey guys, I'm currently trying to set up a ripple validator but keep getting errors when trying to access ripple repositories. I have tried the instructions on the ripple website and the docker method that is posted here but keep getting the same errors. Any suggestions? I'll have my recent attempt with docker posted as a screenshot.

When running rippled on Centos 6 using the yum package, you may encounter this error: Or something to the effect that 1024 file descriptors are available and 4096 were requested from rippled, so it shut down. To fix this error, open /etc/security/limits.conf and at the bottom of the file add: Next, open /etc/sysctl.conf and at the bottom of the file add: Run ulimit -Ha to check if open files has been updated to 10240, such as: Execute service rippled start and it should operate correctly.

Hello! I usually don't post into technical, because I don't know much of the technicals. I bumped into this on Ripple's website and just wanted to ask what it means. Someone who knows can give a sort of ELI5 kind of answer https://ripple.com/build/build-run-rippled-ubuntu/ Lose money in the sense of losing the transactions to hackers with wrong kind of data or just lose money in the sense of "your validator is outdated and does not any bring anything to the network, thus you're wasting resources while running it". Thanks.

Last night we added several new pieces of documentation to the XRP Ledger in preparation for the upcoming release of rippled 0.90.0: Deposit Authorization is a new feature for compliance with regulations such as the New York Bitlicense. In addition to the concept page, the flag has been added in appropriate places such as the AccountSet transaction reference. Checks documentation has been added to the transaction reference and ledger reference. Checks are a feature originally conceived back in, like, 2012 or something, which got new life recently when we realized they'd solve one of the challenges with Deposit Authorization. We also added specific instructions for how to build and run rippled 0.90.0 and higher on Ubuntu Linux. That's important, because rippled 0.90.0 must be compiled against the latest version of Boost, which now includes Vinnie Falco's Beast library (originally developed to use in rippled). There'll be more coming out in the coming days, including an article on another key 0.90.0 feature, history sharding. I can't give a specific release date for 0.90.0, but the feature set is final, as we're just now polishing up the details and ironing out the bugs. As per usual, it'll be out soon—when it's ready—and no sooner. P.S. if you want to try out Checks and Deposit Auth leading up to the release, they're already available for use on the Test Net.

I am trying to send a payment using ripple-lib, and I am getting this error: Here is my code: Thanks so much!

https://ripple.com/dev-blog/rippled-version-0-81-0/ This is a big step towards decentralizing control of the XRP Ledger! Update your validator settings!

Hi everyone! I am brand new to Ripple in general, but a friend of mine studies it quite closely. He has tasked me with running our own rippled instance. Really, my goal at this point is to be able to connect to it from a local ripple-lib script over WSS and query account info -- that's all. I have rippled installed and as far as I can tell have a valid configuration, such that it does run, however the process is constantly being killed and restarted. The response from my script upon api.connect vacillates from garden-variety "NotConnectedError" (when the process is restarting) to "[RippledNotInitializedError(Rippled not initialized)]" (when it is briefly running). My environment is Ubuntu 16.04.1 on a very cheap Digitalocean droplet. I fully realize I will need a more powerful VPS if I want a working, live instance, but I would assume something basic is ok for testing. Please correct me if I am wrong on this. My config as of now is: [server] port_rpc_admin_local port_peer port_ws_admin_local port_ws_public [port_rpc_admin_local] port = 5006 ip = 127.0.0.1 admin = 127.0.0.1 protocol = http [port_peer] port = 51235 ip = 0.0.0.0 protocol = peer [port_ws_admin_local] port = 6006 ip = 127.0.0.1 admin = 127.0.0.1 protocol = ws [port_ws_public] port = 5005 ip = my.ip.addr protocol = wss ssl_key = /etc/opt/ripple/key.pem ssl_cert = /etc/opt/ripple/cert.pem #------------------------------------------------------------------------------- [node_size] medium [node_db] type=RocksDB path=/var/lib/rippled/db/rocksdb open_files=2000 filter_bits=12 cache_mb=256 file_size_mb=8 file_size_mult=2 online_delete=2000 advisory_delete=0 [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 [sntp_servers] time.windows.com time.apple.com time.nist.gov pool.ntp.org # Where to find some other servers speaking the Ripple protocol. # [ips] r.ripple.com 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": "info" } # 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] 0 A log of when I run rippled with "--fg --net" is below (it's long....sorry): 2018-Jan-08 00:45:04 JobQueue:NFO Auto-tuning to 3 validation/transaction/proposal threads. 2018-Jan-08 00:45:04 Amendments:DBG Amendment C6970A8B603D8778783B61C0D445C23D1633CCFAEF0D43E7DBCD1521D34BD7C3 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 740352F2412A9909880C23A559FCECEDA3BE2126FED62FC7660D628A06927F11 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 532651B4FD58DF8922A49BA101AB3E996E5BFBF95A913B3E392504863E63B164 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment E2E6F2866106419B88C50045ACE96368558C345566AC8F2BDF5A5B5587F0E6FA is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 07D43DCE529B15A10827E5E04943B496762F9A88E3268269D69C44BE49E21104 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 86E83A7D2ECE3AD5FA87AB2195AE015C950469ABF0B72EAACED318F74886AE90 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 3012E8230864E95A58C60FD61430D7E1B4D3353195F2981DC12B0C7C0950FFAC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment CC5ABAE4F3EC92E94A59B1908C2BE82D2228B6485C00AFF8F22DF930D89C194E is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment B4D44CC3111ADD964E846FC57760C8B50FFCD5A82C86A72756F6B058DDDF96AD is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 6C92211186613F9647A89DFFBAB8F94C99D4C7E956D495270789128569177DA1 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment B9E739B8296B4A1BB29BE990B17D66E21B62A300A909F25AC55C22D6C72E1F9D is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 1D3463A5891F9E589C5AE839FFAC4A917CE96197098A1EF22304E1BC5B98A454 is supported. 2018-Jan-08 00:45:04 OrderBookDB:DBG Advancing from 0 to 3 2018-Jan-08 00:45:04 OrderBookDB:DBG OrderBookDB::update> 2018-Jan-08 00:45:04 OrderBookDB:DBG OrderBookDB::update< 0 books found 2018-Jan-08 00:45:04 ValidatorList:DBG Loading configured trusted validator list publisher keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loaded 0 keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loading configured validator keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loaded 5 entries 2018-Jan-08 00:45:04 ValidatorSite:DBG Loading configured validator list sites 2018-Jan-08 00:45:04 ValidatorSite:DBG Loaded 0 sites 2018-Jan-08 00:45:04 NodeObject:DBG NodeStore target size set to 131072 2018-Jan-08 00:45:04 NodeObject:DBG NodeStore target age set to 120000000000 2018-Jan-08 00:45:04 TaggedCache:DBG LedgerCache target size set to 256 2018-Jan-08 00:45:04 TaggedCache:DBG LedgerCache target age set to 180000000000 2018-Jan-08 00:45:04 TaggedCache:DBG TreeNodeCache target size set to 512000 2018-Jan-08 00:45:04 TaggedCache:DBG TreeNodeCache target age set to 90000000000 2018-Jan-08 00:45:04 NetworkOPs:NFO Consensus time for #3 with LCL 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 2018-Jan-08 00:45:04 ValidatorList:DBG 5 of 5 listed validators eligible for inclusion in the trusted set 2018-Jan-08 00:45:04 ValidatorList:DBG Using quorum of 3 for new set of 5 trusted validators 2018-Jan-08 00:45:04 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:04 LedgerConsensus:NFO Consensus mode change before=observing, after=observing 2018-Jan-08 00:45:04 NetworkOPs:DBG Initiating consensus engine 2018-Jan-08 00:45:04 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5006, admin IPs:127.0.0.1, http) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_ws_public' (ip=my.ip.addr:5005, wss) 2018-Jan-08 00:45:04 Application:FTL Startup RPC: { "command" : "log_level", "severity" : "info" } 2018-Jan-08 00:45:04 Application:FTL Result: {} 2018-Jan-08 00:45:04 PeerFinder:NFO Opening database at '/var/lib/rippled/db/peerfinder.sqlite' 2018-Jan-08 00:45:04 PeerFinder:NFO Opened version 4 database 2018-Jan-08 00:45:04 PeerFinder:NFO Bootcache loaded 187 addresses 2018-Jan-08 00:45:04 Application:NFO Application starting. Version is 0.80.2 2018-Jan-08 00:45:04 PeerFinder:NFO Logic added 0 new addresses from config: r.ripple.com 51235 2018-Jan-08 00:45:05 NetworkOPs:NFO STATE->connected 2018-Jan-08 00:45:05 NetworkOPs:NFO Node count (0) is sufficient. 2018-Jan-08 00:45:05 Peer:NFO [011] Public Key: n9KiJ4JHhajZ3mQ2k29ekz1ixnDYaQdF6bNi2hiKDhRM9nhwaLfW 2018-Jan-08 00:45:05 Peer:NFO [011] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.239.120.20:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [014] Public Key: n9MXY1xfS1VWmazwoYc98zvS28eVu1RQcYhWNKmzqxHd56oeRHQC 2018-Jan-08 00:45:05 Peer:NFO [014] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 52.55.102.204:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [010] Public Key: n9LGt2t1h1P76SnG86sEBTGdT6GrfxcT23KZ4nZX7xbGDYu3Y8Fc 2018-Jan-08 00:45:05 Peer:NFO [010] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.201.251.148:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [009] Public Key: n94KWZ9yJNJhaSqnn1S4K7Kna7ciaVBpjrqgHHyBM6g6NfgRAXT5 2018-Jan-08 00:45:05 Peer:NFO [009] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 184.72.137.59:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [019] Public Key: n9MqFgf89C1Q81rUXmunZjhFr1sZwaaQYoknVzTVwNC9ky9u2Mxb 2018-Jan-08 00:45:05 Peer:NFO [019] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.229.128.152:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [012] Public Key: n9Jt8awsPzWLjBCNKVEEDQnw4bQEPjezfcQ4gttD1UzbLT1FoG99 2018-Jan-08 00:45:05 Peer:NFO [012] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 52.90.42.69:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [013] Public Key: n94hKvqUffbA2cY49wz2Q7X2JoxtFW9o4dcWi6CSzUfXDTt3MWEi 2018-Jan-08 00:45:05 Peer:NFO [013] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.201.105.122:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [006] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [002] Public Key: n9KJb7NMxGySRcjCqh69xEPMUhwJx22qntYYXsnUqYgjsJhNoW7g 2018-Jan-08 00:45:05 Peer:NFO [002] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 54.84.21.230:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [018] Public Key: n9LnqwvUxFBUdnS1JzbziohwVium9EkYL5i7TuTx2TvPSskPPcVs 2018-Jan-08 00:45:05 Peer:NFO [018] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 169.54.2.157:51235 with 1 success 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #1 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #2 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #3 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #4 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #5 2018-Jan-08 00:45:05 Peer:NFO [008] Public Key: n94rE1SydpHTvJ4NyX9vC1cdeDmYP5nQSXTyeMnLh8jMJSRdcy9Q 2018-Jan-08 00:45:05 Peer:NFO [008] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 54.86.175.122:51235 with 33 successes 2018-Jan-08 00:45:05 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:05 Peer:NFO [017] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [005] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [001] Public Key: n9JAeNYjfb1Uzf5RHRpvDbYTvVNgPWiUfPUhdDtakQ1yXJ32n51c 2018-Jan-08 00:45:05 Peer:NFO [001] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 184.173.45.38:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [020] Public Key: n9MGChK9EgiCBM6s15EwF9d6m4LWZHh1UnJcgr16kQr4xBpx71fS 2018-Jan-08 00:45:05 Peer:NFO [020] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 198.11.206.6:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [004] Public Key: n9LieQkojpM1wsqman9d8jxVXrLxRh8RAmwv5rDvC5ea3kxnEVUn 2018-Jan-08 00:45:05 Peer:NFO [004] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 198.11.206.26:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [016] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:06 Peer:NFO [003] Public Key: n9MT5EjnV912KGuBUqPs4tpdhzMPGcnDBrTuWkD9sWQHJ1kDcUcz 2018-Jan-08 00:45:06 Peer:NFO [003] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 54.186.248.91:51235 with 33 successes 2018-Jan-08 00:45:06 Peer:NFO [007] Public Key: n9JySgyBVcQKvyDoeRKg7s2Mm6ZcFHk22vUZb3o1HSosWxcj9xPt 2018-Jan-08 00:45:06 Peer:NFO [007] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 54.186.73.52:51235 with 33 successes 2018-Jan-08 00:45:06 LedgerConsensus:WRN View of consensus changed during open status=open, mode=observing 2018-Jan-08 00:45:06 LedgerConsensus:WRN 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 to 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:06 LedgerConsensus:WRN { "accepted" : true, "account_hash" : "183D5235C7C1FB5AE67AD2F6CC3B28F5FB86E8C4F89DB50DD85641A96470534E", "close_flags" : 0, "close_time" : 568687500, "close_time_human" : "2018-Jan-08 00:45:00", "close_time_resolution" : 30, "closed" : true, "hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "ledger_hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "ledger_index" : "2", "parent_close_time" : 0, "parent_hash" : "AB868A6CFEEC779C2FF845C0AF00A642259986AF40C01976A7F842B6918936C7", "seqNum" : "2", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:06 LedgerConsensus:WRN Need consensus ledger 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:06 LedgerConsensus:NFO Consensus mode change before=observing, after=wrongLedger 2018-Jan-08 00:45:06 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:06 Peer:NFO [015] Public Key: n9KybMFrer7erpQDh58epdQkQga3pSaVYhD855h4gTkHtMUGVMx2 2018-Jan-08 00:45:06 Peer:NFO [015] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 52.78.78.122:51235 with 1 success 2018-Jan-08 00:45:07 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Proposers:5 nw:50 thrV:2 thrC:4 2018-Jan-08 00:45:08 LedgerConsensus:NFO Position change: CTime 568687501, tx 850CD9248733D95D8B3A79F452966CBCDFB4AAF01E48FCDD5B56EF9E943DF4A2 2018-Jan-08 00:45:08 LedgerConsensus:NFO Converge cutoff (5 participants) 2018-Jan-08 00:45:08 LedgerConsensus:NFO CNF buildLCL CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:08 NetworkOPs:WRN We are not running on the consensus ledger 2018-Jan-08 00:45:08 NetworkOPs:NFO Our LCL: { "accepted" : true, "account_hash" : "A0D5E308F7D3104D15CC4D73E6C0E88C17073FEF30F3AE9C09AB4A214A9390B4", "close_flags" : 0, "close_time" : 568687501, "close_time_human" : "2018-Jan-08 00:45:01", "close_time_resolution" : 30, "closed" : true, "hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "ledger_hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "ledger_index" : "3", "parent_close_time" : 568687500, "parent_hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "seqNum" : "3", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:08 NetworkOPs:NFO Net LCL 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:08 NetworkOPs:NFO Consensus time for #4 with LCL CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:08 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:08 LedgerConsensus:NFO Entering consensus with: 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 2018-Jan-08 00:45:08 LedgerConsensus:NFO Correct LCL is: 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:09 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:09 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LedgerConsensus:NFO Proposers:5 nw:50 thrV:2 thrC:4 2018-Jan-08 00:45:10 LedgerConsensus:NFO Position change: CTime 568687502, tx 850CD9248733D95D8B3A79F452966CBCDFB4AAF01E48FCDD5B56EF9E943DF4A2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Converge cutoff (5 participants) 2018-Jan-08 00:45:10 LedgerConsensus:NFO CNF buildLCL 11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149 2018-Jan-08 00:45:10 NetworkOPs:WRN We are not running on the consensus ledger 2018-Jan-08 00:45:10 NetworkOPs:NFO Our LCL: { "accepted" : true, "account_hash" : "B0FD2544671D7B6FF68C11E316B61FAD2C00357D6B264835D28DB4AFD0596329", "close_flags" : 0, "close_time" : 568687502, "close_time_human" : "2018-Jan-08 00:45:02", "close_time_resolution" : 30, "closed" : true, "hash" : "11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149", "ledger_hash" : "11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149", "ledger_index" : "4", "parent_close_time" : 568687501, "parent_hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "seqNum" : "4", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:10 NetworkOPs:NFO Net LCL BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 NetworkOPs:NFO Consensus time for #5 with LCL 11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149 2018-Jan-08 00:45:10 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:10 LedgerConsensus:WRN Need consensus ledger BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Entering consensus with: CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:10 LedgerConsensus:NFO Correct LCL is: BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LoadMonitor:WRN Job: processLedgerData run: 2058ms wait: 0ms 2018-Jan-08 00:45:11 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger Killed If I run: ps -eo pid,comm,lstart,etime,time,args | grep rippled I can see: 22497 rippled: #142 Mon Jan 8 00:12:37 2018 30:29 00:00:00 /opt/ripple/bin/rippled --net 25235 rippled: main Mon Jan 8 00:43:02 2018 00:04 00:00:00 /opt/ripple/bin/rippled --net The duration of the main process never exceeds 0:15 or so, which strikes me as the root issue, however the numbered child process is fine. **It is also worth noting that if I run rippled in standalone mode, this issue doesn't occur, but then I am obviously unable to query any account info.** I've dug this forum and others for possible solutions as to why I would be seeing this, but I continue to hit dead ends. If anybody here has any ideas for what to look at, I would be incredibly grateful! Thank you! - Johnny

i am trying to start an private ripple blockchain with one validator but when i check the status it gives me error root@admin1-OptiPlex-9020:~# sudo systemctl status rippled.service ● rippled.service - Ripple Daemon Loaded: loaded (/usr/lib/systemd/system/rippled.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/rippled.service.d └─nofile_limit.conf Active: inactive (dead) since Wed 2017-07-19 13:58:15 IST; 3min 36s ago Process: 4254 ExecStart=/opt/ripple/bin/rippled --net --silent --conf /etc/opt/ripple/rippled.cfg (code=exited, status=0/SUCCESS) Main PID: 4254 (code=exited, status=0/SUCCESS) Jul 19 13:57:25 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 1 Jul 19 13:57:25 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:57:35 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 2 Jul 19 13:57:35 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:57:45 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 3 Jul 19 13:57:45 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:57:55 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 4 Jul 19 13:57:55 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:58:05 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 5 My rippled.cfg -- [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 = 127.0.0.1 admin = 127.0.0.1 protocol = http [port_peer] port = 51235 ip = 0.0.0.0 protocol = peer [port_ws_admin_local] port = 6006 ip = 127.0.0.1 admin = 127.0.0.1 protocol = ws #[port_ws_public] #port = 5005 #ip = 127.0.0.1 #protocol = wss #------------------------------------------------------------------------------- [node_db] type=RocksDB path=/var/lib/rippled/db/rocksdb open_files=2000 filter_bits=12 cache_mb=256 file_size_mb=8 file_size_mult=2 online_delete=2000 advisory_delete=0 [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 # Where to find some other servers speaking the Ripple protocol. # [ips] #r.ripple.com 51235 [validator_token] ey-------------------------------------token # 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 Please help me to resolve it

Wow guys, what a horrible day. It only seems like its going to get worse. Looks like there is absolutely no buy support as the bears are demolishing the price of XRP. It may even end up cheaper than when the AMEX partnership was announced. Crazy right? I really don't get it. What I do get is that lots of people are probably losing money at this point on this trade if they bought on the way up. This is another pump and dump. Sickening. I'm tired of Ripple doing this every single time. I have made so much more money with Stellar Lumens. I'll keepp Holding because you don't realize a loss until you sell, but my God this is frustrating. Not to mention the opportunity cost since you are basically stuck in a trade. Will we ever catch a real break with XRP? God help us!