-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no active instances or receiving awards #435
Comments
Hi, please run the following commands and share the output you get: |
evernode status
Host account address: rwf4Uv3TGkhpUzDrP819eWeeCzaPwHoB6V
█████████████████████████████████████
█████████████████████████████████████
████ ▄▄▄▄▄ █ ██▀▀ ▀▄▀█ ██ ▄▄▄▄▄ ████
████ █ █ █ ▀█ █▄█▀▄ █▄█ █ █ ████
████ █▄▄▄█ █▀ █▄█████▄▀██ █▄▄▄█ ████
████▄▄▄▄▄▄▄█▄█ ▀▄▀▄█▄▀ █▄█▄▄▄▄▄▄▄████
████▄▄██ ▄▀▀█▄█▄ ▀█ ▄▀█▀▀▀ ▀▄ ▄ ████
█████▀▄█▄▀▄▀▀ ▄█▀█▀▄▄ █▄ ▀█▄█▄████
████ █▄▄█▄▄▀█▀▄▀▄▄▀▄█▀▄▀ █▀▀█▀ ▀████
█████▀ ▄██▄▄▀ █ ▄ ▄▄ ▀▀███ ▀ ▀█▀▄████
████▀▀▀▄██▄▄▄▀ █▄ ▀█▀ ██▀ ▀▀▀█ ▀▀████
██████ ███▄ ▄███▀█▀▄█▀███ ██▄ █▀ ████
████▄▄▄▄██▄▄▀▀▄▄▀▄▄ ▀▄▀▄ ▄▄▄ █▀█▀████
████ ▄▄▄▄▄ █▀▀▀ ▄ ▄ ▀▀ █▄█ █▄▄▄████
████ █ █ █▄ ██▄ ▀▄▀██ ▄ ▄▄ ▀▀█▀████
████ █▄▄▄█ █▀▀▄█▀█▀▄█ █▀▀▄ ▀█ ▄ ████
████▄▄▄▄▄▄▄█▄▄▄▄█▄▄█▄▄██▄██▄▄█▄▄█████
█████████████████████████████████████
█████████████████████████████████████
Version: 0.12.0
Governor address: rBvKgF3jSZWdJcwSsmoJspoXLLDVLDp6jg
Registry address: rmv53yu8Wid6kj6AC6NvmiwSXNxRa8vTH
Heartbeat address: rHktfGUbjqzU4GsYCMc1pDjdHXb5CJamto
Registration URIToken:
F2F742D511CCD222673FDCA4A04E292CD87999BC405E08C2D8FD85B174EFB1D9
EVR balance: 21.07602407225668
Available Lease offers: 9 out of 9
Reputation: 0
Accumulated rewards: 0
Host status: active
Country code: US
NOTE: If the Host status is shown as inactive it will be marked as active
after sending the next heartbeat.
Sashimono agent status: active
Sashimono message board status: active
Your registration account details are stored in
/etc/sashimono/mb-xrpl/mb-xrpl.cfg
Evernode reputationd status: active
Your reputationd account details are stored in
/etc/sashimono/reputationd/reputationd.cfg
***@***.***:~#
Evernode reputationd status
Version: 0.12.0
Evernode Reputation Hook address: rsfTBRAbD2bYjVuXhJ2RReQXxR4K5birVW
Host reputation-delegate account address: rhma6f7Xb8M8QUGhesJDYMYtKdirF1yFEp
{
"hostAddress": "rwf4Uv3TGkhpUzDrP819eWeeCzaPwHoB6V",
"lastRegisteredMoment": 6561,
"scoreNumerator": 843,
"scoreDenominator": 33,
"score": 39,
"lastResetMoment": 6561,
"lastScoredMoment": 6561,
"lastUniverseSize": 53,
"valid": false,
"moment": 6859,
"reportedHostCount": 5684
}
REPUTATIOND_SUCCESS
Evernode reputationd status: active
Your reputationd account details are stored in
/etc/sashimono/reputationd/reputationd.cfg
NOTE: To participate in this reputation assessment process continuously,
you need to ensure that your reputation account
has a sufficient EVR balance to perform the instance acquisitions.
***@***.***:~#
…On Mon, Sep 23, 2024 at 5:18 AM Dulana ***@***.***> wrote:
Hi, please run the following commands and share the output you get:
evernode status
evernode reputationd status
—
Reply to this email directly, view it on GitHub
<#435 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKJAOTHLQM4YSPHKOUTPZPTZX7MF5AVCNFSM6AAAAABOT77EQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRXGY2TCNZYHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Please refer to this documentation and check if your host has any issues related to prerequisite checks. Instance creation might be skipped because of this. |
how can i withdraw the ever/xah out of the reputation address ?
…On Wed, Sep 25, 2024 at 12:08 AM Dulana ***@***.***> wrote:
Please refer to this documentation
<https://docs.evernode.org/en/latest/hosts/evernode-diagnostics.html#f-no-relevant-reputation-instance>
and check if your host has any issues related to prerequisite checks.
Instance creation might be skipped because of this.
—
Reply to this email directly, view it on GitHub
<#435 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKJAOTD4D3USMMFCVJSG2VDZYIZKTAVCNFSM6AAAAABOT77EQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZSHA3TGMBSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
To get your account secret, run |
Not getting any active instances or getting rewards
ran 2 commands
sudo -u sashireputationd bash -c 'journalctl --user -u sashimono-reputationd | tail -n 250'
sudo -u sashimbxrpl bash -c journalctl --user -u sashimono-mb-xrpl | tail -n 250
got the same message for both........"No journal files were opened due to insufficient permissions."
please advise
The text was updated successfully, but these errors were encountered: