search

EvernodeXRPL / evernode-host

Evernode host installer
Other
54 stars 9 forks source link

reputationd set to 0 (3 nodes out of 4) #401

Open luigiubezio opened 3 months ago

luigiubezio commented 3 months ago

I have 4 for nodes (version 0.11.0 - opt-in enabled), ut on 3 of them reputation is set to 0. Looking into logs with journalctl command: sudo -u sashireputationd bash -c 'journalctl --user -u sashimono-reputationd | tail -n 200' I found the following error: (error: 'ACQUIRE_ERR', reason: 'TIMEOUT'). All details are below. Is there a way to resolve this error?

Thanks Luigi

Aug 07 07:29:28 evernode.cloud.instance node[3685773]: 20240807 07:29:28 [dbg] Checking IPV4 support... Aug 07 07:29:31 evernode.cloud.instance node[3685773]: 20240807 07:29:29 [dbg] Checking version compatibility... Aug 07 07:29:31 evernode.cloud.instance node[3685773]: 20240807 07:29:29 [dbg] Checking SSL certificate validity... Aug 07 07:29:32 evernode.cloud.instance node[3685773]: 20240807 07:29:32 [dbg] All requirement checks passed. Aug 07 07:29:32 evernode.cloud.instance node[3685773]: 20240807 07:29:32 [dbg] Preparing reputation contract for the Moment 5690... Aug 07 07:29:34 evernode.cloud.instance node[3685773]: 20240807 07:29:34 [dbg] Acquiring the reputation contract instance... Aug 07 07:29:50 evernode.cloud.instance node[3685773]: 20240807 07:29:50 [dbg] Skipping reputation contract deployment since there's no universe info for the moment 5690. Aug 07 07:30:16 evernode.cloud.instance node[3685773]: 20240807 07:30:16 [dbg] Transaction result: tesSUCCESS Aug 07 07:30:16 evernode.cloud.instance node[3685773]: 20240807 07:30:16 [dbg] Waiting for acquire response... (txHash: A85C672B1FD6396AAD6D99645F7A8EE2D5DC11A631F261CCA49DC88894C12B42) Aug 07 07:35:16 evernode.cloud.instance node[3685773]: 20240807 07:35:16 [err] { error: 'ACQUIRE_ERR', reason: 'TIMEOUT' } Aug 07 07:35:16 evernode.cloud.instance node[3685773]: 20240807 07:35:16 [dbg] Retry attempt 1 Aug 07 07:35:16 evernode.cloud.instance node[3685773]: 20240807 07:35:16 [dbg] Skipping reputation sender since no instance created in the moment 5690. Aug 07 07:35:19 evernode.cloud.instance node[3685773]: 20240807 07:35:19 [dbg] Checking IPV4 support... Aug 07 07:35:19 evernode.cloud.instance node[3685773]: 20240807 07:35:19 [dbg] Checking version compatibility... Aug 07 07:35:19 evernode.cloud.instance node[3685773]: 20240807 07:35:19 [dbg] Checking SSL certificate validity... Aug 07 07:35:19 evernode.cloud.instance node[3685773]: 20240807 07:35:19 [dbg] All requirement checks passed. Aug 07 07:35:19 evernode.cloud.instance node[3685773]: 20240807 07:35:19 [dbg] Skipping since scheduled moment has passed. Scheduled in 5689, Current moment 5690.

Zamolxis969 commented 3 months ago

I do have same issue as you do!

du1ana commented 2 months ago

hi, this could be due to issues in your host's specs or connection. 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'

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

luigiubezio commented 2 months ago

sashi_mb.log Hello Dulana, the fist command returned no rows (on my server 3 213.136.83.146), but the following error message: No journal files were found. The second command on the same server succeeded. Results are attached (file: sashi_mb.log). In the mean time I updated to version 0.12, if I launch the command evernode config status, suggested on the github site I receive parse error: Invalid numeric literal at line 1, column 4I

Thanks Regards

Luigi

du1ana commented 2 months ago

The command evernode config status is not valid in the Evernode CLI. Did you mean to run evernode status instead? Also, are you still encountering the (error: 'ACQUIRE_ERR', reason: 'TIMEOUT') errors after updating to v0.12.0?