No longer receiving rewards

[KC-evernode]

Hi,

I'm running v0.12 and my reputation is at 250
However, I'm not receiving any rewards any more??

Kevin

[du1ana]

Hi, right now the rewards are paused due to a bug in Xahau. While rewards are paused, please opt out of reputationd until further notice.

[KC-evernode]

Thank you for your feedback!

[du1ana]

Since rewards have been resumed, I will close this issue. Reputationd will be functional again after opting in.

[KC-evernode]

Hi, still not able to receive any rewards, furthermore, I'm getting errors in my VPS since last wednesday....

Your current resource allocation is:
Memory: 4.85 GB
Swap: 3.35 GB
Disk space: 70.15 GB
Instance count: 2

root@vmi1708052:~# evernode config resources 0 0 0 4
Downloading setup support files...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 922k 100 922k 0 0 1464k 0 --:--:-- --:--:-- --:--:-- 1464k
Done.

Using allocation
Distributed among 4 contract instances

Starting the reconfiguration...

Stopping the message board...
Stopping the sashimono...
configuring sashimono...

CPU per instance should be greater than 400000 Micro Sec.
There was an error in updating sashimono configuration.
Starting the sashimono...
Starting the message board...

Changing the configuration exited with an error.

[du1ana]

"CPU per instance should be greater than 400000 Micro Sec." <- you are violating the minimum CPU requirement when increasing the number of contract instances.

Regarding the rewards error, please run the following commands and send the logs you get:

Reputation log :
sudo -u sashireputationd bash -c 'journalctl --user -u sashimono-reputationd | tail -n 250'

MB-XRPL log :
sudo -u sashimbxrpl bash -c journalctl --user -u sashimono-mb-xrpl | tail -n 250

Evernode Status:
evernode status

Evernode Reputationd Status:
evernode reputationd status

[KC-evernode]

Thank you for your prompt reply!

• Regarding the CPU requirements: untill 4 weeks ago, I had been running 6 instances without any issue... Now, I'm not even able to adjust the number of instances...
• Reputation log :
  sudo -u sashireputationd bash -c 'journalctl --user -u sashimono-reputationd | tail -n 250'
  -> No journal files were opened due to insufficient permissions.

MB-XRPL log :
sudo -u sashimbxrpl bash -c journalctl --user -u sashimono-mb-xrpl | tail -n 250
-> No journal files were opened due to insufficient permissions.

Evernode Status:
evernode status
**Version: 0.12.0

Governor address: rBvKgF3jSZWdJcwSsmoJspoXLLDVLDp6jg
Registry address: rmv53yu8Wid6kj6AC6NvmiwSXNxRa8vTH
Heartbeat address: rHktfGUbjqzU4GsYCMc1pDjdHXb5CJamto
Registration URIToken: 633FBE393D3AD0F0C3646A7AD14A01E04B7B06D023344031DA33914FDB5D043C
EVR balance: 757.8573820840069
Available Lease offers: 1 out of 2
Reputation: 0
Accumulated rewards: 0

Host status: active

Country code: DE
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:
evernode reputationd status
**Version: 0.12.0
Evernode Reputation Hook address: rsfTBRAbD2bYjVuXhJ2RReQXxR4K5birVW
Host reputation-delegate account address: r3kZKZQ2P48FttE1AqdQstEHf75nRnqXEC
{
"hostAddress": "rEX5ojnub3wEeiMUEZGRnMZ49jJFzqR8qE",
"lastRegisteredMoment": 6820,
"scoreNumerator": 4117,
"scoreDenominator": 55,
"score": 77,
"lastResetMoment": 6819,
"lastScoredMoment": 6819,
"lastUniverseSize": 63,
"valid": true,
"moment": 6820,
"orderedId": 1746,
"contract": {
"domain": "kc-evernode.be",
"pubkey": "eddef1d90b42b984af758c496f82a8e0a47b585b9708f9cff39dedb6e4bd08a726",
"peerPort": 22862
},
"reportedHostCount": 5870
}
REPUTATIOND_SUCCESS

Evernode reputationd status: active

Your reputationd account details are stored in /etc/sashimono/reputationd/reputationd.cfg**

[du1ana]

The issue with accessing journals is a known issue we noticed in Contabo-based hosts which does not have a fix yet. Please refer to this documentation to diagnose reward/reputationD related issues in your hosts.