EvernodeXRPL/evernode-host

Error during update - yet again

Closed this issue · 4 comments

root@evernode-host:/home/chris# curl -fsSL https://raw.githubusercontent.com/EvernodeXRPL/evernode-resources/main/sashimono/installer/evernode.sh | sudo bash -s update
Found Sashimono v0.8.3...
Checking for updates...
New Evernode update available. Setup will re-install Evernode with updated software. Your account and contract instances will be preserved.

Do you want to install the update? [Y/n] y

Starting upgrade...
Installing Sashimono...
Installing docker packages
Configuring Sashimono services
Aborting the installation..
There was an error during installation.
Please provide the file /tmp/evernode/installer-1715896234.log to the Evernode team by visiting this link: https://github.com/EvernodeXRPL/evernode-host/issues.
Thank you.

Log

2024-05-16 21:50:42 ---Sashimono installer (upgrade)---
2024-05-16 21:50:42 Failed to connect to bus: No such file or directory
2024-05-16 21:50:42 [STAGE] Installing docker packages
2024-05-16 21:50:42 Private docker registry installation skipped
2024-05-16 21:50:42 configuring host setup on Evernode...
2024-05-16 21:50:42 cp: cannot stat '/tmp/tmp.Ly00lofPs8/reputation-contract': No such file or directory
2024-05-16 21:50:42 [STAGE] Configuring Sashimono services
2024-05-16 21:50:42 Creating cgroup rules...
2024-05-16 21:50:42 Configuring sashimono agent service...
2024-05-16 21:50:42 Existing Sashimono data directory found. Updating...
2024-05-16 21:50:42 MB_CLI_SUCCESS
2024-05-16 21:50:42 Installing Evernode Xahau message board...
2024-05-16 21:50:42 Updated mb user .bashrc.
2024-05-16 21:50:42 NO_MB_USER_SYSTEMD

Hmm, interesting catch. NO_MB_USER_SYSTEMD will show up if the user setup had failed or delayed. Is it the same if you run the update again?

Interesting indeed.

It said v 0.8.3 was already installed however much wasn't working.

I could send heartbeats, but I couldn't activate the reputationd command as it didn't exist. It showed part of the install as not functioning.

GNv4wQFaAAAzFsq

Anyway, I transferred my account, and reinstalled. All is working again.

Таж проблема
Screenshot_3
Screenshot_4

resolved with Ext4 partition use, host transferred successfully and contract lease now working