Closed siasiab1 closed 5 months ago
chalith
commented
6 months ago Have you manually updated any config files? Try again transferring using the command starting with curl here https://docs.evernode.org/en/latest/hosts/maintenance.html#transfer-the-host-registration. Do not install the older version over new version.
siasiab1
commented
6 months ago I followed your instruction when I want to transfer it gives the following error:
Do you want to set the current host account as the transferee's account? [Y/n] y
Transferring host...
SyntaxError: Unexpected end of JSON input
at JSON.parse (
what shall I do? Shall I uninstall anyway?
siasiab1
commented
6 months ago Kindly my node is down for 1 day and I appreciate your assistance
Evernode transfer initiation was failed but is asking if i want to continue installation. What shall i do?
chalith
commented
6 months ago Can you try above transfer command on a separate machine and check if it succeeds If so do a evernode uninstall.
Before you do, make sure to backup both your host and reputation secrets
JULIEN9159
commented
6 months ago Hello guys,
Same issue here : My host where reputation contract is running is not properly working anymore.
Since some days no issue at all, rep contract working fine (except not at every moment, but still was showing active), and now it's on "activating" with this display when running status :
Evernode reputationd status: activating
Your reputationd account details are stored in /etc/sashimono/reputationd/reputationd.cfg
SyntaxError: Unexpected end of JSON input
at JSON.parse (
From now, even Evernode status is not working properly and my node became offline :
Evernode reputationd status: activating
Your reputationd account details are stored in /etc/sashimono/reputationd/reputationd.cfg
SyntaxError: Unexpected end of JSON input
at JSON.parse (
You can also find the log (Evernode log) here :
May 23 07:35:09 evernode101 node[4104]: at JSON.parse (
JULIEN9159
commented
6 months ago It seems the configuration file is totally missing : /etc/sashimono/reputationd/reputationd.cfg is empty.....
How to recover? Someone has an example ?
JULIEN9159
commented
6 months ago Ok. I opted out and then opted in --> reputation contracts working back.
However, it seems my previous lease has not end properly, leading to having 2 lease used and only 1 available
1st was initial RC 2nd is new RC 3rd is available
JULIEN9159
commented
6 months ago Trying to opt out, then delete the instances, but evernode list is giving no information, only [].
I tried to delete the txn hash that seems to be linked to the URI token create selloffer, but getting error :
JULIEN9159
commented
5 months ago Update : it seems since the instance not available since rep contract crash, even if opt out and opt in, with a new lease intake, the command "Evernode list" is not showing the new rep contract instance name (only showing [])
chalith
commented
5 months ago @JULIEN9159 it seems your reputationd is still inactive, Have you opted in again?
And also to fix leases try running evernode offerlease command and it'll create missing lease offers. If it doesn't not fix the lease problem. Try changing the instance count to a different value (probably 4) using evernode config resources command and then again change it back to original size (in your case 3)
JULIEN9159
commented
5 months ago My reputation was active. But through another instance.
I followed your advice.: offerlease not Working, I tried with config ressources, ans it worked. I put 0 0 0 4 and then back to 0 0 0 3. Thank for the update. I will monitor if any trouble as I opted-in again.
Also, I hope the team will be able to identify the concern and fix it in future update.
Again thank you @chalith
JULIEN9159
commented
5 months ago Hello,
Again this morning, after 1 day running well, I got below failure : ![Uploading Screenshot_2024-05-28-11-44-09-974_com.server.auditor.ssh.client.png…]()
JULIEN9159
commented
5 months ago My disk seems full but I don't understand why
chalith
commented
5 months ago Hi @JULIEN9159 what's the latest status of the issue after the patch?
JULIEN9159
commented
5 months ago Hello,
After changing my VM I didn't get any issue (5 days running ol with opt-in). Now I patched it but can't see the difference as no concern anymore.
Have a good day
chalith
commented
5 months ago Thank you @JULIEN9159. We are closing the issue
I updated my host to 0.8.3 and averything was ok. I even opt-in for reputation and evernoed status was active.
upon my second login I ran evernode status and got the following error
node01@node01:~$ evernode status SyntaxError: Unexpected end of JSON input at JSON.parse ()
at ConfigHelper.readConfig (/usr/bin/sashimono/mb-xrpl/index.js:1:3760)
at #F (/usr/bin/sashimono/mb-xrpl/index.js:1:40008)
at Setup.regInfo (/usr/bin/sashimono/mb-xrpl/index.js:1:48723)
at main (/usr/bin/sashimono/mb-xrpl/index.js:64:476978)
at /usr/bin/sashimono/mb-xrpl/index.js:64:480577
at /usr/bin/sashimono/mb-xrpl/index.js:64:480869
at Object. (/usr/bin/sashimono/mb-xrpl/index.js:64:480908)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
MB_CLI_EXITED
I installed previous version again and then tryed to install the latest version but got error again and the log is as follow:
2024-05-19 21:47:40 ---Sashimono installer (upgrade)--- 2024-05-19 21:47:40 Failed to connect to bus: No such file or directory 2024-05-19 21:47:40 [STAGE] Installing docker packages 2024-05-19 21:47:40 Private docker registry installation skipped 2024-05-19 21:47:40 configuring host setup on Evernode... 2024-05-19 21:47:40 cp: cannot stat '/tmp/tmp.IhLU6DkqO7/reputation-contract': No such file or directory 2024-05-19 21:47:40 [STAGE] Configuring Sashimono services 2024-05-19 21:47:40 Creating cgroup rules... 2024-05-19 21:47:40 Configuring sashimono agent service... 2024-05-19 21:47:40 Existing Sashimono data directory found. Updating... 2024-05-19 21:47:40 SyntaxError: Unexpected end of JSON input 2024-05-19 21:47:40 at JSON.parse ()
2024-05-19 21:47:40 at ConfigHelper.readConfig (/usr/bin/sashimono/mb-xrpl/index.js:1:3760)
2024-05-19 21:47:40 at #F (/usr/bin/sashimono/mb-xrpl/index.js:1:40008)
2024-05-19 21:47:40 at Setup.upgrade (/usr/bin/sashimono/mb-xrpl/index.js:1:50135)
2024-05-19 21:47:40 at main (/usr/bin/sashimono/mb-xrpl/index.js:64:477155)
2024-05-19 21:47:40 at /usr/bin/sashimono/mb-xrpl/index.js:64:480577
2024-05-19 21:47:40 at /usr/bin/sashimono/mb-xrpl/index.js:64:480869
2024-05-19 21:47:40 at Object. (/usr/bin/sashimono/mb-xrpl/index.js:64:480908)
2024-05-19 21:47:40 at Module._compile (node:internal/modules/cjs/loader:1376:14)
2024-05-19 21:47:40 at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
2024-05-19 21:47:40 MB_CLI_EXITED
I tried to Transfer my account but got the following error:
Transferring host... SyntaxError: Unexpected end of JSON input at JSON.parse ()
at ConfigHelper.readConfig (/usr/bin/sashimono/mb-xrpl/index.js:1:3760)
at #F (/usr/bin/sashimono/mb-xrpl/index.js:1:40008)
at Setup.transfer (/usr/bin/sashimono/mb-xrpl/index.js:1:52166)
at main (/usr/bin/sashimono/mb-xrpl/index.js:64:476815)
at /usr/bin/sashimono/mb-xrpl/index.js:64:480577
at /usr/bin/sashimono/mb-xrpl/index.js:64:480869
at Object. (/usr/bin/sashimono/mb-xrpl/index.js:64:480908)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
MB_CLI_EXITED
Evernode transfer initiation was failed. Still do you want to continue the unistallation? [Y/n] n
Aborting unistallation. Try again later.
I kindly appreciate your assistance