-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guardian Node synch issue with log file error message #127
Comments
no, it downloads the snapshot but does not synch.
…On Fri, Jul 9, 2021 at 8:09 AM Jieyi Long (THETA Network) < ***@***.***> wrote:
@tkburke2000 <https://github.com/tkburke2000> Has your node issue been
resolved ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#127>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWIRNUZ3ZZSR3OQ6ZUPT4TTW3RGJANCNFSM5ACUTVYQ>
.
--
_______________
Tom Burke
|
What’s your email address ? |
use ***@***.***
…On Fri, Jul 9, 2021 at 8:26 AM Jieyi Long (THETA Network) < ***@***.***> wrote:
What’s your email address ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWIRNT7QYV7TCXM7UYNLHTTW3TILANCNFSM5ACUTVYQ>
.
--
_______________
Tom Burke
|
It’s not showing up here. It’s hidden. |
@tkburke2000 What’s your email address ? write like this xxxxxx-yyyyy.com |
tkburke-gmail.com
…On Fri, Jul 9, 2021 at 9:14 AM Jieyi Long (THETA Network) < ***@***.***> wrote:
@tkburke2000 <https://github.com/tkburke2000> What’s your email address ?
write like this xxxxxx-yyyyy.com
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWIRNUCMPOGDDLA2AOKWEDTW3Y4RANCNFSM5ACUTVYQ>
.
--
_______________
Tom Burke
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@tkburke2000 Has your node issue been resolved ?
The text was updated successfully, but these errors were encountered: