From 18b8d3761de7737ea255ab574c0d024fc6356563 Mon Sep 17 00:00:00 2001 From: Alloy Networks <45832257+alloynetworks@users.noreply.github.com> Date: Mon, 24 May 2021 14:36:59 +0300 Subject: [PATCH 01/10] Change download link/version for Boost v 1.76.0 Update the download links and change the latest available Boost version from 1.71 to 1.75 --- .../installation/build-run-rippled-ubuntu.md | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md index 5b46d8623f..c267892c48 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md @@ -49,21 +49,21 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof 5. Compile Boost. - Version 1.7.0 of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself. The following examples use Boost 1.71.0, which was the newest version at the time of writing. + Version 1.7.0 of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself. The following examples use Boost 1.76.0, which was the newest version at the time of writing. - If you have previously built Boost 1.71.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps. + If you have previously built Boost 1.76.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps. - 1. Download Boost 1.71.0. + 1. Download Boost 1.76.0. + + wget https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.gz - wget https://dl.bintray.com/boostorg/release/1.71.0/source/boost_1_71_0.tar.gz + 2. Extract `boost_1_76_0.tar.gz`. - 2. Extract `boost_1_71_0.tar.gz`. + tar xvzf boost_1_76_0.tar.gz - tar xvzf boost_1_71_0.tar.gz + 3. Change to the new `boost_1_76_0` directory. - 3. Change to the new `boost_1_71_0` directory. - - cd boost_1_71_0 + cd boost_1_76_0 4. Prepare the Boost.Build system for use. @@ -75,9 +75,9 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof **Tip:** This example uses 4 processes to build in parallel. The best number of processes to use depends on how many CPU cores your hardware has available. You can use `cat /proc/cpuinfo` to get information about your hardware's processor. - 6. Set the environment variable `BOOST_ROOT` to point to the new `boost_1_71_0` directory. It's best to put this environment variable in your `.profile`, or equivalent, file for your shell so it's automatically set when you log in. Add the following line to the file: + 6. Set the environment variable `BOOST_ROOT` to point to the new `boost_1_76_0` directory. It's best to put this environment variable in your `.profile`, or equivalent, file for your shell so it's automatically set when you log in. Add the following line to the file: - export BOOST_ROOT=/home/my_user/boost_1_71_0 + export BOOST_ROOT=/home/my_user/boost_1_76_0 7. Source your updated `.profile` file. For example: From 86d5bee93710b8964a2186d65f620da7ef71eedd Mon Sep 17 00:00:00 2001 From: Mayukha Vadari Date: Thu, 3 Jun 2021 13:30:50 -0400 Subject: [PATCH 02/10] fix send_xrp --- content/_code-samples/send-xrp/send-xrp.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/_code-samples/send-xrp/send-xrp.py b/content/_code-samples/send-xrp/send-xrp.py index ba14b2211a..7e2f4d32cc 100644 --- a/content/_code-samples/send-xrp/send-xrp.py +++ b/content/_code-samples/send-xrp/send-xrp.py @@ -16,7 +16,6 @@ from xrpl.wallet import generate_faucet_wallet test_wallet = generate_faucet_wallet(client, debug=True) # Prepare transaction ---------------------------------------------------------- -import xrpl.utils # workaround for https://github.com/XRPLF/xrpl-py/issues/222 my_payment = xrpl.models.transactions.Payment( account=test_wallet.classic_address, amount=xrpl.utils.xrp_to_drops(22), @@ -28,9 +27,11 @@ print("Payment object:", my_payment) signed_tx = xrpl.transaction.safe_sign_and_autofill_transaction( my_payment, test_wallet, client) max_ledger = signed_tx.last_ledger_sequence +tx_id = signed_tx.get_hash() print("Signed transaction:", signed_tx) print("Transaction cost:", xrpl.utils.drops_to_xrp(signed_tx.fee), "XRP") print("Transaction expires after ledger:", max_ledger) +print("Identifying hash:", tx_id) # Submit transaction ----------------------------------------------------------- validated_index = xrpl.ledger.get_latest_validated_ledger_sequence(client) @@ -41,10 +42,9 @@ print(f"Can be validated in ledger range: {min_ledger} - {max_ledger}") # to send the transaction and wait for the results to be validated. try: prelim_result = xrpl.transaction.submit_transaction(signed_tx, client) -except xrpl.transaction.XRPLReliableSubmissionException as e: +except xrpl.clients.XRPLRequestFailureException as e: exit(f"Submit failed: {e}") print("Preliminary transaction result:", prelim_result) -tx_id = prelim_result.result["tx_json"]["hash"] # Wait for validation ---------------------------------------------------------- # Note: If you used xrpl.transaction.send_reliable_submission, you can skip this From 04e6ac795c1d01bc305045affe7fa0d766390f0d Mon Sep 17 00:00:00 2001 From: Mayukha Vadari Date: Thu, 3 Jun 2021 13:33:25 -0400 Subject: [PATCH 03/10] fix prepare payment --- content/_code-samples/xrpl-py/prepare-payment.py | 1 - 1 file changed, 1 deletion(-) diff --git a/content/_code-samples/xrpl-py/prepare-payment.py b/content/_code-samples/xrpl-py/prepare-payment.py index 8d04fb1ce7..02932ddb37 100644 --- a/content/_code-samples/xrpl-py/prepare-payment.py +++ b/content/_code-samples/xrpl-py/prepare-payment.py @@ -27,7 +27,6 @@ my_tx_payment = Payment( account=test_account, amount=xrp_to_drops(22), destination="rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe", - sequence=test_wallet.sequence, ) # print prepared payment From 2e8074865cdbae6508aa17d92cf5382596db0def Mon Sep 17 00:00:00 2001 From: Mayukha Vadari Date: Thu, 3 Jun 2021 13:36:12 -0400 Subject: [PATCH 04/10] fix secure signing --- content/_code-samples/secure-signing/py/sign-payment.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/_code-samples/secure-signing/py/sign-payment.py b/content/_code-samples/secure-signing/py/sign-payment.py index b3c82cf9d5..3dafef9426 100644 --- a/content/_code-samples/secure-signing/py/sign-payment.py +++ b/content/_code-samples/secure-signing/py/sign-payment.py @@ -2,7 +2,7 @@ import os my_secret = os.getenv("MYSECRET") from xrpl.wallet import Wallet -wallet = Wallet(seed="MYSECRET", sequence=16237283) +wallet = Wallet(seed=my_secret, sequence=16237283) print(wallet.classic_address) # "raaFKKmgf6CRZttTVABeTcsqzRQ51bNR6Q" from xrpl.models.transactions import Payment @@ -12,7 +12,7 @@ my_payment = Payment( amount=xrp_to_drops(22), fee="10", destination="rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe", - sequence=16126889, + sequence=16237283, ) print("Payment object:", my_payment) From d8fe0ec35784a14a8b3a82bc0e5a4843a4e6fc3f Mon Sep 17 00:00:00 2001 From: Mayukha Vadari Date: Tue, 8 Jun 2021 10:28:01 -0400 Subject: [PATCH 05/10] fix wallet sequence --- content/_code-samples/secure-signing/py/sign-payment.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/_code-samples/secure-signing/py/sign-payment.py b/content/_code-samples/secure-signing/py/sign-payment.py index 3dafef9426..d30dfa7c96 100644 --- a/content/_code-samples/secure-signing/py/sign-payment.py +++ b/content/_code-samples/secure-signing/py/sign-payment.py @@ -12,7 +12,7 @@ my_payment = Payment( amount=xrp_to_drops(22), fee="10", destination="rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe", - sequence=16237283, + sequence=wallet.sequence, # this needs to be incremented upon every successful transaction ) print("Payment object:", my_payment) From 5e61fa116495ebaaf9b3770be05d544321832797 Mon Sep 17 00:00:00 2001 From: Alloy Networks <45832257+alloynetworks@users.noreply.github.com> Date: Mon, 14 Jun 2021 15:28:55 +0300 Subject: [PATCH 06/10] Update to change boost version to 1.75.0 As described in comments, the latest compatible version of Boost is 1.75.0 and not 1.76.0 --- .../installation/build-run-rippled-ubuntu.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md index c267892c48..2eeefd08cb 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md @@ -49,21 +49,21 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof 5. Compile Boost. - Version 1.7.0 of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself. The following examples use Boost 1.76.0, which was the newest version at the time of writing. + Version 1.7.0 and higher of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself. The following examples use Boost 1.75.0, which was the newest version compatible with `rippled` at the time of writing. - If you have previously built Boost 1.76.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps. + If you have previously built Boost 1.75.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps. - 1. Download Boost 1.76.0. + 1. Download Boost 1.75.0. - wget https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.gz + wget https://boostorg.jfrog.io/artifactory/main/release/1.75.0/source/boost_1_75_0.tar.gz - 2. Extract `boost_1_76_0.tar.gz`. + 2. Extract `boost_1_75_0.tar.gz`. - tar xvzf boost_1_76_0.tar.gz + tar xvzf boost_1_75_0.tar.gz - 3. Change to the new `boost_1_76_0` directory. + 3. Change to the new `boost_1_75_0` directory. - cd boost_1_76_0 + cd boost_1_75_0 4. Prepare the Boost.Build system for use. From 85fd5b10a2e0573fb2bfcafe89ce1f19bbd3019b Mon Sep 17 00:00:00 2001 From: Elliot Lee Date: Tue, 15 Jun 2021 22:14:46 -0700 Subject: [PATCH 07/10] macOS build: build boost yourself again MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I was not able to install boost@1.75 using homebrew: ➜ brew install boost@1.75 ==> Searching for similarly named formulae... Error: No similarly named formulae found. Error: No available formula or cask with the name "boost@1.75". ==> Searching for a previously deleted formula (in the last month)... Error: No previously deleted formula found. ==> Searching taps on GitHub... Error: No formulae found in taps. --- .../installation/build-run-rippled-macos.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md index 3a4aae9ee0..dc478ef7fb 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md @@ -27,13 +27,11 @@ For development purposes, run `rippled` as a non-admin user, not using `sudo`. 0. Use Homebrew to install dependencies. - $ brew install git cmake pkg-config protobuf openssl ninja boost@1.75 + $ brew install git cmake pkg-config protobuf openssl ninja -{##} + 0. Ensure that your `BOOST_ROOT` environment points to the directory created by the Boost installation: 1. To find your Boost directory, use `pwd` if you installed the Boost manually or use `brew --prefix boost` if you installed the Boost with Homebrew. @@ -50,9 +48,9 @@ For development purposes, run `rippled` as a non-admin user, not using `sudo`. 2. Edit the code below with your Boost directory location and run it to add Boost environment variable to your `.zshrc` or `.bash_profile` file so it's automatically set when you log in. # for zsh - $ echo "export BOOST_ROOT=/Users/my_user/boost_1_71_0" >> ~/.zshrc + $ echo "export BOOST_ROOT=/Users/my_user/boost_1_75_0" >> ~/.zshrc # for bash - $ echo "export BOOST_ROOT=/Users/my_user/boost_1_71_0" >> ~/.bash_profile + $ echo "export BOOST_ROOT=/Users/my_user/boost_1_75_0" >> ~/.bash_profile 0. If you updated your `.bash_profile` file in the previous step, be sure to source it in a new Terminal window. For example: From e73c7918dc251a66a4d857e8b78705d5cb3fbc94 Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Wed, 16 Jun 2021 11:43:37 -0700 Subject: [PATCH 08/10] Ubuntu build: edits per review --- .../installation/build-run-rippled-ubuntu.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md index 2eeefd08cb..10e1c9fba0 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md @@ -49,7 +49,7 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof 5. Compile Boost. - Version 1.7.0 and higher of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself. The following examples use Boost 1.75.0, which was the newest version compatible with `rippled` at the time of writing. + Version 1.7.0 of `rippled` requires the Boost library and is compatible with Boost versions 1.70.0 to 1.75.0. The Ubuntu 18.04 (or 16.04) software repositories don't have a compatible Boost version, so you must compile it yourself. The following examples use Boost 1.75.0. If you have previously built Boost 1.75.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps. @@ -75,9 +75,9 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof **Tip:** This example uses 4 processes to build in parallel. The best number of processes to use depends on how many CPU cores your hardware has available. You can use `cat /proc/cpuinfo` to get information about your hardware's processor. - 6. Set the environment variable `BOOST_ROOT` to point to the new `boost_1_76_0` directory. It's best to put this environment variable in your `.profile`, or equivalent, file for your shell so it's automatically set when you log in. Add the following line to the file: + 6. Set the environment variable `BOOST_ROOT` to point to the new `boost_1_75_0` directory. It's best to put this environment variable in your `.profile`, or equivalent, file for your shell so it's automatically set when you log in. Add the following line to the file: - export BOOST_ROOT=/home/my_user/boost_1_76_0 + export BOOST_ROOT=/home/my_user/boost_1_75_0 7. Source your updated `.profile` file. For example: From 95921639b564b41544396b4fd552fdb55a8d77aa Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Wed, 16 Jun 2021 12:06:25 -0700 Subject: [PATCH 09/10] Build instructions: minor updates & cleanup --- .../build-run-rippled-macos.ja.md | 98 +++++++++---------- .../installation/build-run-rippled-macos.md | 92 ++++++++--------- .../build-run-rippled-ubuntu.ja.md | 28 +++--- .../installation/build-run-rippled-ubuntu.md | 18 ++-- 4 files changed, 118 insertions(+), 118 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md index 0c030d9934..ad5ca9d9a3 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md @@ -29,9 +29,9 @@ blurb: macOSでrippledを自分でコンパイルします。 $ brew install git cmake pkg-config protobuf openssl ninja -0. Boost 1.70.0以降をインストールします。`rippled`1.7.0はBoost 1.70.0以降と互換性があります。HomebrewのリポジトリにあるBoostの最新バージョンでは不十分であるため、Boostを手動でインストールする必要があります。(次の例では、本書執筆時点の最新バージョンであるBoost 1.71.0を使用しています。) +0. Boost 1.75.0以降をインストールします。`rippled`1.7.2はBoost 1.75.0以降と互換性があります。HomebrewのリポジトリにあるBoostの最新バージョンでは不十分であるため、Boostを手動でインストールする必要があります。 - 1. [Boost 1.71.0](https://dl.bintray.com/boostorg/release/1.71.0/source/boost_1_71_0.tar.bz2)をダウンロードします。 + 1. [Boost 1.75.0](https://www.boost.org/users/history/version_1_75_0.html)をダウンロードします。 2. フォルダに抽出します。場所をメモしておいてください。 @@ -47,7 +47,7 @@ blurb: macOSでrippledを自分でコンパイルします。 2. 以下のコードをBoostディレクトリーの場所に編集して実行し、Boost環境変数が`.bash_profile`ファイルに追加されるようにします。そうすることで、ログイン時にこの環境変数が自動的に設定されます。 - $ echo $"export BOOST_ROOT=/Users/my_user/boost_1_71_0" >> ~/.bash_profile + $ echo $"export BOOST_ROOT=/Users/my_user/boost_1_75_0" >> ~/.bash_profile 0. 前のステップで`.bash_profile`ファイルをアップデートした場合には、新しいターミナルウィンドウでそれを読み込みます。例: @@ -118,52 +118,52 @@ blurb: macOSでrippledを自分でコンパイルします。 以下は、ターミナルに表示される内容の抜粋です。 -``` - 2018-Oct-26 18:21:39.593738 JobQueue:NFO Auto-tuning to 6 validation/transaction/proposal threads. - 2018-Oct-26 18:21:39.599634 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported. - 2018-Oct-26 18:21:39.599874 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported. - 2018-Oct-26 18:21:39.599965 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported. - 2018-Oct-26 18:21:39.600024 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported. - ... - 2018-Oct-26 18:21:39.603201 OrderBookDB:DBG Advancing from 0 to 3 - 2018-Oct-26 18:21:39.603291 OrderBookDB:DBG OrderBookDB::update> - 2018-Oct-26 18:21:39.603480 OrderBookDB:DBG OrderBookDB::update< 0 books found - 2018-Oct-26 18:21:39.649617 ValidatorList:DBG Loading configured trusted validator list publisher keys - 2018-Oct-26 18:21:39.649709 ValidatorList:DBG Loaded 0 keys - 2018-Oct-26 18:21:39.649798 ValidatorList:DBG Loading configured validator keys - 2018-Oct-26 18:21:39.650213 ValidatorList:DBG Loaded 5 entries - 2018-Oct-26 18:21:39.650266 ValidatorSite:DBG Loading configured validator list sites - 2018-Oct-26 18:21:39.650319 ValidatorSite:DBG Loaded 0 sites - 2018-Oct-26 18:21:39.650829 NodeObject:DBG NodeStore.main target size set to 131072 - 2018-Oct-26 18:21:39.650876 NodeObject:DBG NodeStore.main target age set to 120000000000 - 2018-Oct-26 18:21:39.650931 TaggedCache:DBG LedgerCache target size set to 256 - 2018-Oct-26 18:21:39.650981 TaggedCache:DBG LedgerCache target age set to 180000000000 - 2018-Oct-26 18:21:39.654252 TaggedCache:DBG TreeNodeCache target size set to 512000 - 2018-Oct-26 18:21:39.654336 TaggedCache:DBG TreeNodeCache target age set to 90000000000 - 2018-Oct-26 18:21:39.674131 NetworkOPs:NFO Consensus time for #3 with LCL AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D - 2018-Oct-26 18:21:39.674271 ValidatorList:DBG 5 of 5 listed validators eligible for inclusion in the trusted set - 2018-Oct-26 18:21:39.674334 ValidatorList:DBG Using quorum of 4 for new set of 5 trusted validators (5 added, 0 removed) - 2018-Oct-26 18:21:39.674400 LedgerConsensus:NFO Entering consensus process, watching, synced=no - 2018-Oct-26 18:21:39.674475 LedgerConsensus:NFO Consensus mode change before=observing, after=observing - 2018-Oct-26 18:21:39.674539 NetworkOPs:DBG Initiating consensus engine - 2018-Oct-26 18:21:39.751225 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5005, admin IPs:127.0.0.1, http) - 2018-Oct-26 18:21:39.751515 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) - 2018-Oct-26 18:21:39.751689 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) - 2018-Oct-26 18:21:39.751915 Application:FTL Startup RPC: - { - "command" : "log_level", - "severity" : "warning" - } - 2018-Oct-26 18:21:39.752079 Application:FTL Result: {} - 2018-Oct-26 18:22:33.013409 NetworkOPs:WRN We are not running on the consensus ledger - 2018-Oct-26 18:22:33.013875 LedgerConsensus:WRN Need consensus ledger 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 - 2018-Oct-26 18:22:33.883648 LedgerConsensus:WRN View of consensus changed during open status=open, mode=wrongLedger - 2018-Oct-26 18:22:33.883815 LedgerConsensus:WRN 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 to 9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1 - 2018-Oct-26 18:22:33.884068 LedgerConsensus:WRN {"accepted":true,"account_hash":"BBA0E7273005D42E5548DD6456E5AD1F7C89B6EDCB01881E1EECD393E8545947","close_flags":0,"close_time":593893350,"close_time_human":"2018-Oct-26 18:22:30.000000","close_time_resolution":30,"closed":true,"hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_index":"3","parent_close_time":593893290,"parent_hash":"AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D","seqNum":"3","totalCoins":"100000000000000000","total_coins":"100000000000000000","transaction_hash":"0000000000000000000000000000000000000000000000000000000000000000"} - 2018-Oct-26 18:23:03.034119 InboundLedger:WRN Want: D901E53926E68EFDA33172DDAC74E8C767D280B68EE68E3010AB0E3179D07B1C - 2018-Oct-26 18:23:03.034334 InboundLedger:WRN Want: 1C01EE79083DE5CE76F3634519D6364C589C4D48631CB9CD10FC2408F87684E2 - 2018-Oct-26 18:23:03.034560 InboundLedger:WRN Want: 8CFE3912001BDC5B2C4B2691F3C7811B9F3F193E835D293459D80FBF1C4E684E - 2018-Oct-26 18:23:03.034750 InboundLedger:WRN Want: 8DFAD21AD3090DE5D6F7592B3821C3DA77A72287705B4CF98DC0F84D5DD2BDF8 +```text +2018-Oct-26 18:21:39.593738 JobQueue:NFO Auto-tuning to 6 validation/transaction/proposal threads. +2018-Oct-26 18:21:39.599634 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported. +2018-Oct-26 18:21:39.599874 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported. +2018-Oct-26 18:21:39.599965 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported. +2018-Oct-26 18:21:39.600024 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported. +... +2018-Oct-26 18:21:39.603201 OrderBookDB:DBG Advancing from 0 to 3 +2018-Oct-26 18:21:39.603291 OrderBookDB:DBG OrderBookDB::update> +2018-Oct-26 18:21:39.603480 OrderBookDB:DBG OrderBookDB::update< 0 books found +2018-Oct-26 18:21:39.649617 ValidatorList:DBG Loading configured trusted validator list publisher keys +2018-Oct-26 18:21:39.649709 ValidatorList:DBG Loaded 0 keys +2018-Oct-26 18:21:39.649798 ValidatorList:DBG Loading configured validator keys +2018-Oct-26 18:21:39.650213 ValidatorList:DBG Loaded 5 entries +2018-Oct-26 18:21:39.650266 ValidatorSite:DBG Loading configured validator list sites +2018-Oct-26 18:21:39.650319 ValidatorSite:DBG Loaded 0 sites +2018-Oct-26 18:21:39.650829 NodeObject:DBG NodeStore.main target size set to 131072 +2018-Oct-26 18:21:39.650876 NodeObject:DBG NodeStore.main target age set to 120000000000 +2018-Oct-26 18:21:39.650931 TaggedCache:DBG LedgerCache target size set to 256 +2018-Oct-26 18:21:39.650981 TaggedCache:DBG LedgerCache target age set to 180000000000 +2018-Oct-26 18:21:39.654252 TaggedCache:DBG TreeNodeCache target size set to 512000 +2018-Oct-26 18:21:39.654336 TaggedCache:DBG TreeNodeCache target age set to 90000000000 +2018-Oct-26 18:21:39.674131 NetworkOPs:NFO Consensus time for #3 with LCL AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D +2018-Oct-26 18:21:39.674271 ValidatorList:DBG 5 of 5 listed validators eligible for inclusion in the trusted set +2018-Oct-26 18:21:39.674334 ValidatorList:DBG Using quorum of 4 for new set of 5 trusted validators (5 added, 0 removed) +2018-Oct-26 18:21:39.674400 LedgerConsensus:NFO Entering consensus process, watching, synced=no +2018-Oct-26 18:21:39.674475 LedgerConsensus:NFO Consensus mode change before=observing, after=observing +2018-Oct-26 18:21:39.674539 NetworkOPs:DBG Initiating consensus engine +2018-Oct-26 18:21:39.751225 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5005, admin IPs:127.0.0.1, http) +2018-Oct-26 18:21:39.751515 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) +2018-Oct-26 18:21:39.751689 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) +2018-Oct-26 18:21:39.751915 Application:FTL Startup RPC: +{ + "command" : "log_level", + "severity" : "warning" +} +2018-Oct-26 18:21:39.752079 Application:FTL Result: {} +2018-Oct-26 18:22:33.013409 NetworkOPs:WRN We are not running on the consensus ledger +2018-Oct-26 18:22:33.013875 LedgerConsensus:WRN Need consensus ledger 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 +2018-Oct-26 18:22:33.883648 LedgerConsensus:WRN View of consensus changed during open status=open, mode=wrongLedger +2018-Oct-26 18:22:33.883815 LedgerConsensus:WRN 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 to 9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1 +2018-Oct-26 18:22:33.884068 LedgerConsensus:WRN {"accepted":true,"account_hash":"BBA0E7273005D42E5548DD6456E5AD1F7C89B6EDCB01881E1EECD393E8545947","close_flags":0,"close_time":593893350,"close_time_human":"2018-Oct-26 18:22:30.000000","close_time_resolution":30,"closed":true,"hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_index":"3","parent_close_time":593893290,"parent_hash":"AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D","seqNum":"3","totalCoins":"100000000000000000","total_coins":"100000000000000000","transaction_hash":"0000000000000000000000000000000000000000000000000000000000000000"} +2018-Oct-26 18:23:03.034119 InboundLedger:WRN Want: D901E53926E68EFDA33172DDAC74E8C767D280B68EE68E3010AB0E3179D07B1C +2018-Oct-26 18:23:03.034334 InboundLedger:WRN Want: 1C01EE79083DE5CE76F3634519D6364C589C4D48631CB9CD10FC2408F87684E2 +2018-Oct-26 18:23:03.034560 InboundLedger:WRN Want: 8CFE3912001BDC5B2C4B2691F3C7811B9F3F193E835D293459D80FBF1C4E684E +2018-Oct-26 18:23:03.034750 InboundLedger:WRN Want: 8DFAD21AD3090DE5D6F7592B3821C3DA77A72287705B4CF98DC0F84D5DD2BDF8 ``` `rippled`ログメッセージの詳細は、[ログメッセージについて](understanding-log-messages.html)を参照してください。 diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md index dc478ef7fb..612c7696ed 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md @@ -132,52 +132,52 @@ For development purposes, run `rippled` as a non-admin user, not using `sudo`. Here's an excerpt of what you can expect to see in your terminal: -``` - 2018-Oct-26 18:21:39.593738 JobQueue:NFO Auto-tuning to 6 validation/transaction/proposal threads. - 2018-Oct-26 18:21:39.599634 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported. - 2018-Oct-26 18:21:39.599874 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported. - 2018-Oct-26 18:21:39.599965 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported. - 2018-Oct-26 18:21:39.600024 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported. - ... - 2018-Oct-26 18:21:39.603201 OrderBookDB:DBG Advancing from 0 to 3 - 2018-Oct-26 18:21:39.603291 OrderBookDB:DBG OrderBookDB::update> - 2018-Oct-26 18:21:39.603480 OrderBookDB:DBG OrderBookDB::update< 0 books found - 2018-Oct-26 18:21:39.649617 ValidatorList:DBG Loading configured trusted validator list publisher keys - 2018-Oct-26 18:21:39.649709 ValidatorList:DBG Loaded 0 keys - 2018-Oct-26 18:21:39.649798 ValidatorList:DBG Loading configured validator keys - 2018-Oct-26 18:21:39.650213 ValidatorList:DBG Loaded 5 entries - 2018-Oct-26 18:21:39.650266 ValidatorSite:DBG Loading configured validator list sites - 2018-Oct-26 18:21:39.650319 ValidatorSite:DBG Loaded 0 sites - 2018-Oct-26 18:21:39.650829 NodeObject:DBG NodeStore.main target size set to 131072 - 2018-Oct-26 18:21:39.650876 NodeObject:DBG NodeStore.main target age set to 120000000000 - 2018-Oct-26 18:21:39.650931 TaggedCache:DBG LedgerCache target size set to 256 - 2018-Oct-26 18:21:39.650981 TaggedCache:DBG LedgerCache target age set to 180000000000 - 2018-Oct-26 18:21:39.654252 TaggedCache:DBG TreeNodeCache target size set to 512000 - 2018-Oct-26 18:21:39.654336 TaggedCache:DBG TreeNodeCache target age set to 90000000000 - 2018-Oct-26 18:21:39.674131 NetworkOPs:NFO Consensus time for #3 with LCL AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D - 2018-Oct-26 18:21:39.674271 ValidatorList:DBG 5 of 5 listed validators eligible for inclusion in the trusted set - 2018-Oct-26 18:21:39.674334 ValidatorList:DBG Using quorum of 4 for new set of 5 trusted validators (5 added, 0 removed) - 2018-Oct-26 18:21:39.674400 LedgerConsensus:NFO Entering consensus process, watching, synced=no - 2018-Oct-26 18:21:39.674475 LedgerConsensus:NFO Consensus mode change before=observing, after=observing - 2018-Oct-26 18:21:39.674539 NetworkOPs:DBG Initiating consensus engine - 2018-Oct-26 18:21:39.751225 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5005, admin IPs:127.0.0.1, http) - 2018-Oct-26 18:21:39.751515 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) - 2018-Oct-26 18:21:39.751689 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) - 2018-Oct-26 18:21:39.751915 Application:FTL Startup RPC: - { - "command" : "log_level", - "severity" : "warning" - } - 2018-Oct-26 18:21:39.752079 Application:FTL Result: {} - 2018-Oct-26 18:22:33.013409 NetworkOPs:WRN We are not running on the consensus ledger - 2018-Oct-26 18:22:33.013875 LedgerConsensus:WRN Need consensus ledger 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 - 2018-Oct-26 18:22:33.883648 LedgerConsensus:WRN View of consensus changed during open status=open, mode=wrongLedger - 2018-Oct-26 18:22:33.883815 LedgerConsensus:WRN 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 to 9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1 - 2018-Oct-26 18:22:33.884068 LedgerConsensus:WRN {"accepted":true,"account_hash":"BBA0E7273005D42E5548DD6456E5AD1F7C89B6EDCB01881E1EECD393E8545947","close_flags":0,"close_time":593893350,"close_time_human":"2018-Oct-26 18:22:30.000000","close_time_resolution":30,"closed":true,"hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_index":"3","parent_close_time":593893290,"parent_hash":"AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D","seqNum":"3","totalCoins":"100000000000000000","total_coins":"100000000000000000","transaction_hash":"0000000000000000000000000000000000000000000000000000000000000000"} - 2018-Oct-26 18:23:03.034119 InboundLedger:WRN Want: D901E53926E68EFDA33172DDAC74E8C767D280B68EE68E3010AB0E3179D07B1C - 2018-Oct-26 18:23:03.034334 InboundLedger:WRN Want: 1C01EE79083DE5CE76F3634519D6364C589C4D48631CB9CD10FC2408F87684E2 - 2018-Oct-26 18:23:03.034560 InboundLedger:WRN Want: 8CFE3912001BDC5B2C4B2691F3C7811B9F3F193E835D293459D80FBF1C4E684E - 2018-Oct-26 18:23:03.034750 InboundLedger:WRN Want: 8DFAD21AD3090DE5D6F7592B3821C3DA77A72287705B4CF98DC0F84D5DD2BDF8 +```text +2018-Oct-26 18:21:39.593738 JobQueue:NFO Auto-tuning to 6 validation/transaction/proposal threads. +2018-Oct-26 18:21:39.599634 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported. +2018-Oct-26 18:21:39.599874 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported. +2018-Oct-26 18:21:39.599965 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported. +2018-Oct-26 18:21:39.600024 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported. +... +2018-Oct-26 18:21:39.603201 OrderBookDB:DBG Advancing from 0 to 3 +2018-Oct-26 18:21:39.603291 OrderBookDB:DBG OrderBookDB::update> +2018-Oct-26 18:21:39.603480 OrderBookDB:DBG OrderBookDB::update< 0 books found +2018-Oct-26 18:21:39.649617 ValidatorList:DBG Loading configured trusted validator list publisher keys +2018-Oct-26 18:21:39.649709 ValidatorList:DBG Loaded 0 keys +2018-Oct-26 18:21:39.649798 ValidatorList:DBG Loading configured validator keys +2018-Oct-26 18:21:39.650213 ValidatorList:DBG Loaded 5 entries +2018-Oct-26 18:21:39.650266 ValidatorSite:DBG Loading configured validator list sites +2018-Oct-26 18:21:39.650319 ValidatorSite:DBG Loaded 0 sites +2018-Oct-26 18:21:39.650829 NodeObject:DBG NodeStore.main target size set to 131072 +2018-Oct-26 18:21:39.650876 NodeObject:DBG NodeStore.main target age set to 120000000000 +2018-Oct-26 18:21:39.650931 TaggedCache:DBG LedgerCache target size set to 256 +2018-Oct-26 18:21:39.650981 TaggedCache:DBG LedgerCache target age set to 180000000000 +2018-Oct-26 18:21:39.654252 TaggedCache:DBG TreeNodeCache target size set to 512000 +2018-Oct-26 18:21:39.654336 TaggedCache:DBG TreeNodeCache target age set to 90000000000 +2018-Oct-26 18:21:39.674131 NetworkOPs:NFO Consensus time for #3 with LCL AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D +2018-Oct-26 18:21:39.674271 ValidatorList:DBG 5 of 5 listed validators eligible for inclusion in the trusted set +2018-Oct-26 18:21:39.674334 ValidatorList:DBG Using quorum of 4 for new set of 5 trusted validators (5 added, 0 removed) +2018-Oct-26 18:21:39.674400 LedgerConsensus:NFO Entering consensus process, watching, synced=no +2018-Oct-26 18:21:39.674475 LedgerConsensus:NFO Consensus mode change before=observing, after=observing +2018-Oct-26 18:21:39.674539 NetworkOPs:DBG Initiating consensus engine +2018-Oct-26 18:21:39.751225 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5005, admin IPs:127.0.0.1, http) +2018-Oct-26 18:21:39.751515 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) +2018-Oct-26 18:21:39.751689 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) +2018-Oct-26 18:21:39.751915 Application:FTL Startup RPC: +{ + "command" : "log_level", + "severity" : "warning" +} +2018-Oct-26 18:21:39.752079 Application:FTL Result: {} +2018-Oct-26 18:22:33.013409 NetworkOPs:WRN We are not running on the consensus ledger +2018-Oct-26 18:22:33.013875 LedgerConsensus:WRN Need consensus ledger 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 +2018-Oct-26 18:22:33.883648 LedgerConsensus:WRN View of consensus changed during open status=open, mode=wrongLedger +2018-Oct-26 18:22:33.883815 LedgerConsensus:WRN 81804C95ADE119CC874572BAF24DB0C0D240AC58168597951B0CB64C4DA2C628 to 9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1 +2018-Oct-26 18:22:33.884068 LedgerConsensus:WRN {"accepted":true,"account_hash":"BBA0E7273005D42E5548DD6456E5AD1F7C89B6EDCB01881E1EECD393E8545947","close_flags":0,"close_time":593893350,"close_time_human":"2018-Oct-26 18:22:30.000000","close_time_resolution":30,"closed":true,"hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_hash":"9250C6C8326A48C339E6F99167F4E6BFD0DB00C35518027724D7B376340D21A1","ledger_index":"3","parent_close_time":593893290,"parent_hash":"AF8D8984A226AE7099D8A9749B09CE1D84360D5AF9FB86CE2F37500FE1009F9D","seqNum":"3","totalCoins":"100000000000000000","total_coins":"100000000000000000","transaction_hash":"0000000000000000000000000000000000000000000000000000000000000000"} +2018-Oct-26 18:23:03.034119 InboundLedger:WRN Want: D901E53926E68EFDA33172DDAC74E8C767D280B68EE68E3010AB0E3179D07B1C +2018-Oct-26 18:23:03.034334 InboundLedger:WRN Want: 1C01EE79083DE5CE76F3634519D6364C589C4D48631CB9CD10FC2408F87684E2 +2018-Oct-26 18:23:03.034560 InboundLedger:WRN Want: 8CFE3912001BDC5B2C4B2691F3C7811B9F3F193E835D293459D80FBF1C4E684E +2018-Oct-26 18:23:03.034750 InboundLedger:WRN Want: 8DFAD21AD3090DE5D6F7592B3821C3DA77A72287705B4CF98DC0F84D5DD2BDF8 ``` For information about `rippled` log messages, see [Understanding Log Messages](understanding-log-messages.html). diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md index dba0bceb6c..cff743d78a 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md @@ -9,7 +9,7 @@ blurb: Ubuntu Linuxでrippledを自分でコンパイルします。 `rippled`の概要については、[Operating rippled Servers](install-rippled.html)を参照してください。 -次の手順を使用し、16.04以降のUbuntu Linux上で、ソースバージョン1.2.0以上から、`rippled`実行可能ファイルを構築します。これらの手順は、Ubuntu 16.04 LTSでテスト済みです。 +次の手順を使用し、Ubuntu Linux上で、`rippled`実行可能ファイルを構築します。これらの手順は、Ubuntu 18.04 LTSでテスト済みです。 その他のプラットフォームでの`rippled`の構築については、`rippled` GitHubリポジトリの[Builds](https://github.com/ripple/rippled/tree/develop/Builds)を参照してください。 @@ -49,21 +49,21 @@ blurb: Ubuntu Linuxでrippledを自分でコンパイルします。 5. Boostをコンパイルします。 - `rippled`のバージョン1.7.0は、Boostバージョン1.70.0以降を必要とします。Ubuntu 18.04(または16.04)ソフトウェアリポジトリにBoostバージョン1.70.0以降がないため、自分でコンパイルする必要があります。(次の例では、執筆時点の最新バージョンであるBoost 1.71.0を使用しています。) + `rippled`のバージョン1.7.2は、Boostバージョン1.70.0ライブラリを必要とします、Boostバージョン1.70.0から1.75.0と互換性があります。 Ubuntu 18.04(または20.04)ソフトウェアリポジトリに互換性なBoostバージョンがないため、自分でコンパイルする必要があります。(次の例では、執筆時点の最新バージョンであるBoost 1.75.0を使用しています。) - 以前に`rippled`用にBoost 1.71.0をインストールしていて、`BOOST_ROOT`環境変数を構成した場合には、このステップはスキップできます。 + 以前に`rippled`用にBoost 1.75.0をインストールしていて、`BOOST_ROOT`環境変数を構成した場合には、このステップはスキップできます。 - 1. Boost 1.71.0をダウンロードします。 + 1. Boost 1.75.0をダウンロードします。 - wget https://dl.bintray.com/boostorg/release/1.71.0/source/boost_1_71_0.tar.gz + wget https://boostorg.jfrog.io/artifactory/main/release/1.75.0/source/boost_1_75_0.tar.gz - 2. `boost_1_71_0.tar.gz`を抽出します。 + 2. `boost_1_75_0.tar.gz`を抽出します。 - tar xvzf boost_1_71_0.tar.gz + tar xvzf boost_1_75_0.tar.gz - 3. 新しい`boost_1_71_0`ディレクトリーに移動します。 + 3. 新しい`boost_1_75_0`ディレクトリーに移動します。 - cd boost_1_71_0 + cd boost_1_75_0 4. 使用するBoost.Buildシステムを準備します。 @@ -75,9 +75,9 @@ blurb: Ubuntu Linuxでrippledを自分でコンパイルします。 **ヒント:** この例では、4つのプロセスを並行して構築します。使用する最適なプロセス数は、お使いのハードウェアで使用可能なCPUコア数によって異なります。`cat /proc/cpuinfo`を使用して、ハードウェアプロセッサーに関する情報を取得できます。 - 6. `BOOST_ROOT`環境変数を、新しい`boost_1_71_0`ディレクトリーを参照するように設定します。ログイン時に自動的に設定されるようにするため、この環境変数を、シェル用の`.profile`またはそれに相当するファイルに入れることをお勧めします。ファイルに次の行を追加します。 + 6. `BOOST_ROOT`環境変数を、新しい`boost_1_75_0`ディレクトリーを参照するように設定します。ログイン時に自動的に設定されるようにするため、この環境変数を、シェル用の`.profile`またはそれに相当するファイルに入れることをお勧めします。ファイルに次の行を追加します。 - export BOOST_ROOT=/home/my_user/boost_1_71_0 + export BOOST_ROOT=/home/my_user/boost_1_75_0 7. 更新した`.profile`ファイルを読み込みます。例: @@ -144,8 +144,8 @@ blurb: Ubuntu Linuxでrippledを自分でコンパイルします。 ## 3. `rippled`の実行 定義した構成を使用し、構築した実行可能ファイルからストック`rippled`サーバーを実行するには、以下を実行します。 -``` -cd my_build + +```sh ./rippled ``` @@ -154,7 +154,7 @@ cd my_build `rippled`を実行するとターミナルに表示される内容の抜粋を以下に示します。 -``` +```text Loading: "/home/ubuntu/.config/ripple/rippled.cfg" Watchdog: Launching child 1 2018-Jun-06 00:51:35.094331139 JobQueue:NFO Auto-tuning to 4 validation/transaction/proposal threads. diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md index 10e1c9fba0..85423f7ccb 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md @@ -9,7 +9,7 @@ blurb: Compile rippled yourself on Ubuntu Linux. For an overview of `rippled`, see [Operating rippled Servers](install-rippled.html). -Use these instructions to build a `rippled` executable from source version 1.2.0 or higher on Ubuntu Linux 16.04 or higher. These instructions were tested on Ubuntu 16.04 LTS. +Use these instructions to build a `rippled` executable from source. These instructions were tested on Ubuntu 18.04 LTS. For information about building `rippled` for other platforms, see [Builds](https://github.com/ripple/rippled/tree/develop/Builds) in the `rippled` GitHub repository. @@ -20,7 +20,7 @@ Before you compile or install `rippled`, you must meet the [System Requirements] ## 1. Build `rippled` -These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the software prerequisites you need to build and run `rippled`. +These instructions use Ubuntu's APT (Advanced Packaging Tool) to install `rippled`'s build dependencies. 1. Update the list of packages that are available for `apt-get` to install or upgrade. @@ -36,7 +36,7 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof 4. Install CMake. - Version 1.7.0 of `rippled` requires CMake 3.9.0 or higher. For the purposes of this tutorial, we used CMake 3.13.3, which was the latest version available at the time of writing. + Version 1.7.2 of `rippled` requires CMake 3.9.0 or higher. For the purposes of this tutorial, we used CMake 3.13.3. If you have previously installed CMake 3.9.0 or higher, you can skip these steps. @@ -49,12 +49,12 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof 5. Compile Boost. - Version 1.7.0 of `rippled` requires the Boost library and is compatible with Boost versions 1.70.0 to 1.75.0. The Ubuntu 18.04 (or 16.04) software repositories don't have a compatible Boost version, so you must compile it yourself. The following examples use Boost 1.75.0. + Version 1.7.2 of `rippled` requires the Boost library and is compatible with Boost versions 1.70.0 to 1.75.0. The Ubuntu 18.04 (or 20.04) software repositories don't have a compatible Boost version, so you must compile it yourself. The following examples use Boost 1.75.0. If you have previously built Boost 1.75.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps. 1. Download Boost 1.75.0. - + wget https://boostorg.jfrog.io/artifactory/main/release/1.75.0/source/boost_1_75_0.tar.gz 2. Extract `boost_1_75_0.tar.gz`. @@ -142,9 +142,9 @@ Complete the following configurations that are required for `rippled` to start u ## 3. Run `rippled` -To run your stock `rippled` server from the executable you built, using the configurations you defined: -``` -cd my_build +To run your `rippled` server from the executable you built: + +```sh ./rippled ``` @@ -153,7 +153,7 @@ cd my_build Once you've run `rippled`, here are excerpts of what you can expect to see in your terminal. -``` +```text Loading: "/home/ubuntu/.config/ripple/rippled.cfg" Watchdog: Launching child 1 2018-Jun-06 00:51:35.094331139 JobQueue:NFO Auto-tuning to 4 validation/transaction/proposal threads. From a1ffa033ce1851b779e706d7f42f6a3b99647bc6 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Wed, 16 Jun 2021 12:11:55 -0700 Subject: [PATCH 10/10] macOS: update latest tested OS ver. --- .../installation/build-run-rippled-macos.ja.md | 2 +- .../installation/build-run-rippled-macos.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md index ad5ca9d9a3..d04ee3393f 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md @@ -7,7 +7,7 @@ blurb: macOSでrippledを自分でコンパイルします。 [`rippled`](the-rippled-server.html)の本番環境にmacOSプラットフォームを使用することは推奨されていません。本番環境には、最高レベルの品質管理とテストを経た、[Ubuntuプラットフォーム](install-rippled-on-ubuntu-with-alien.html)のご使用をご検討ください。 -しかしながら、macOSは多くの開発やテストの作業に適しています。`rippled`は、10.13 High SierraまでのmacOSでテスト済みです。 +しかしながら、macOSは多くの開発やテストの作業に適しています。`rippled`は、10.15.7 CatalinaまでのmacOSでテスト済みです。 開発目的の場合は、`sudo`を使用するのではなく、非管理者ユーザーとして`rippled`を実行します。 diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md index 612c7696ed..979e570cc6 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md @@ -7,7 +7,7 @@ blurb: Compile rippled yourself on macOS. The macOS platform is not recommended for [`rippled`](the-rippled-server.html) production use. For production, consider using the [Ubuntu platform](install-rippled-on-ubuntu-with-alien.html), which has received the highest level of quality assurance and testing. -That said, macOS is suitable for many development and testing tasks. `rippled` has been tested for use with macOS up to 10.13 High Sierra. +That said, macOS is suitable for many development and testing tasks. `rippled` has been tested for use with macOS up to 10.15.7 Catalina. For development purposes, run `rippled` as a non-admin user, not using `sudo`.