Unable to opt-in (reputation) #409
Comments
|
Are you running sudo in front of command?
*Otto Burroughs* | Web3.0 Consultant | Linkedin
<https://www.linkedin.com/in/oburroughs> | MWorks
<https://www.mworks.design>
99 Wall Street #2582 New York, NY 10005 | ( 917 ) 437-8893
…On Sun, Aug 18, 2024 at 2:10 AM Name023 ***@***.***> wrote:
Hello,
I have tried to opt in with my 2 nodes, and every time I saw a QR code
(reputation address) . And then the message
" node: OpenSSL configuration error:
40D8139B0B7F0000:error:8000000D:system library:BIO_new_file:Permission
denied:.. /deps/openssl/openssl/crypto/bio/bss_file.c:67:calling
fopen(/etc/ssl/openssl.cn f, rb)
Error creating configs
Error occured configuring ReputationD. Retry with the same command again."
It's clear that I cannot opt-in now. The server has lost its name after
opt-in ("I have no name") . And I see in VNC -bash: /etc/profile:
Permission denied.
The deadline for opt-in is tomorrow. Nobody from Discord community can
help me. I hope, there is a solution for this.
—
Reply to this email directly, view it on GitHub
<#409>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASVZGDRCCR3HNOE4GE7LRS3ZSBQGRAVCNFSM6AAAAABMWF3ZC2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TCOBXGA4TAOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Yes |
|
Start here
#70
*Otto Burroughs* | Web3.0 Consultant | Linkedin
<https://www.linkedin.com/in/oburroughs> | MWorks
<https://www.mworks.design>
99 Wall Street #2582 New York, NY 10005 | ( 917 ) 437-8893
…On Sun, Aug 18, 2024 at 2:12 AM Name023 ***@***.***> wrote:
Yes
—
Reply to this email directly, view it on GitHub
<#409 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASVZGDX4LKEBWSYQQEHGAYDZSBQQNAVCNFSM6AAAAABMWF3ZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGE4DQNRSGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I read it. I just updated hosts recently. I didn't run ReputationD bundle update, Sashimono Agent binary update and |
|
If your current host is giving you trouble, it might be best to start
fresh. Here's a step-by-step guide to help you transition smoothly:
1. **Backup Your Skey**: Begin by securely backing up your skey.
2. **Set Up a New Node Environment**: Create a new environment for your
node. Before installing or transferring host registration, make sure to add
the path and skey. You can do this by running `mkdir ...` and `touch ...`
commands; these details can be found by checking the Evernode status on
your current node.
3. **Transfer Host Registration**: Return to your current host and
initiate the transfer process to same host.
4. **Install/Transfer on New Host**: Log in or SSH into your new host. Use
the latest install/transfer link provided in the GitHub issue to get the
most recent version of Evernode installed fresh.
**** Additionally, Xahau has released an update that supports increased
reputation transactions. If you’re managing your own Xahd submission node,
it’s advisable to update it first for optimal performance.
…On Sun, Aug 18, 2024 at 4:34 AM Name023 ***@***.***> wrote:
Start here #70 <#70> *Otto
Burroughs* | Web3.0 Consultant | Linkedin
https://www.linkedin.com/in/oburroughs | MWorks https://www.mworks.design 99
Wall Street #2582 New York, NY 10005
<https://www.google.com/maps/search/99+Wall+Street+%232582+New+York,+NY+10005?entry=gmail&source=g>
| ( 917 ) 437-8893
… <#m_-2052420437808437772_>
On Sun, Aug 18, 2024 at 2:12 AM Name023 *@*.*> wrote: Yes — Reply to this
email directly, view it on GitHub <#409 (comment)
<#409 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASVZGDX4LKEBWSYQQEHGAYDZSBQQNAVCNFSM6AAAAABMWF3ZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGE4DQNRSGM
<https://github.com/notifications/unsubscribe-auth/ASVZGDX4LKEBWSYQQEHGAYDZSBQQNAVCNFSM6AAAAABMWF3ZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGE4DQNRSGM>
. You are receiving this because you commented.Message ID: @.*>
I read it. I just updated hosts recently. I didn't run ReputationD bundle
update, Sashimono Agent binary update and
Sashimono Agent binary update three weeks ago, as I thought that they were
covered with the most recent updates. Could it be the problem? What can be
done now. I have a couple of recently updated hosts that I haven't opted in
yet. How can I opt-in them?
—
Reply to this email directly, view it on GitHub
<#409 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASVZGDXUAJSBKBD3KDQ45ETZSCBFJAVCNFSM6AAAAABMWF3ZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGIZDSMBRGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Thank you. I'll try that and (https://docs.evernode.org/en/latest/hosts/maintenance.html). |
|
You can definitely run the reputation opt-in on your updated hosts, but
it's important to note that the exact cause of the previous error remains
uncertain.
I would recommend first reviewing the logs on the affected Evernode to
ensure that the issue is fully resolved. From my experience, the errors
during the update were largely due to Xahaud WSS being overloaded.
You're on the right path with your approach—starting with thorough
maintenance is crucial.
Here’s what I suggest:
1. Run `apt-get update` to ensure your system packages are up to date.
2. Verify that your SSL certificates are valid. Additionally, consider
creating a new Xah reputation wallet for each node.
Before opting in, make sure you have sufficient $EVR and $XAH in your Xaman
account. Activating each Xah reputation wallet automatically for every
Evernode instance can add an extra layer of reliability and help avoid
similar issues in the future.
This approach may be more detailed, but it should minimize the risk of
encountering the same problem again.
…On Sun, Aug 18, 2024 at 5:39 AM Name023 ***@***.***> wrote:
Thank you. I'll try that and (
https://docs.evernode.org/en/latest/hosts/maintenance.html).
My question is: I have a couple updated Evernode hosts. What should I do
to avoid the same error? Is it possible to opt-in without the problem I
encountered? Could it be that if I run ReputationD bundle update, Sashimono
Agent binary update and
Sashimono Agent binary update on my other hosts now, the problem with
opt-in won't appear?
—
Reply to this email directly, view it on GitHub
<#409 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASVZGDUGDRWX5DMTH4EHPMLZSCIZXAVCNFSM6AAAAABMWF3ZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGI2DONZRHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I post here the log of the even (opt-in). I hope you can find the reason for the problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have tried to opt in with my 2 nodes, and every time I saw a QR code (reputation address) . And then the message
" node: OpenSSL configuration error:
40D8139B0B7F0000:error:8000000D:system library:BIO_new_file:Permission denied:.. /deps/openssl/openssl/crypto/bio/bss_file.c:67:calling fopen(/etc/ssl/openssl.cn f, rb)
Error creating configs
Error occured configuring ReputationD. Retry with the same command again."
I have updated the Evernode hosts and Xahau node before opt-in. SSL certificates and ports were also alright.
It's clear that I cannot opt-in now. The server has lost its name after opt-in ("I have no name") . And I see in VNC -bash: /etc/profile: Permission denied.
The deadline for opt-in is tomorrow. Nobody from Discord community can help me. I hope, there is a solution for this.
The text was updated successfully, but these errors were encountered: