From strong and steady to BAD (Last contact increasing since v0.21.1 >> Expected behavior)

[bigdadboom]

Hi,

As a newcomer to this community I have been trying to find a solution for my issue, however nothing have answered my question so far.

After updating my node to 0.21.1 from 0.20.1 I see that “Last Contact” happens to hit more than 2 minutes at time. Before update I was surprised if it came over 7s.

Running Windows 10, newest docker 19.03.2 with 300/300 connection.

examples of my timer.

Then for a periode of time it runs normally.

Please advice how to make it steady again as I dont want to loose reputation because of this.

[mike]

Welcome to the forum

This is expected behavior. You can see more info here:

Higher "last contact" time in v0.21.1

Since the upgrade to v0.21.1, it looks like the last contact time tends to grow higher than it used to (30min history): [image] On v0.20.1, I feel like this value was rarely over 10 seconds and now it’s growing to over 3 minutes on a regular basis. Is this an issue introduced by the update, or is it some kind of optimization that I shouldn’t worry about? I’m seeing this same trend on both of my nodes (different networks).

[nerdatwork]

You should add --color to your dashboard command and thank me later

[bigdadboom]

Thanks.

I did read that post but I don’t see it strictly connected to what I experience.
Another thing is that I wish there would be a much more clear answer to this.

It might be expected now that there is 2 posts about it, but I haven’t been able to read about it anywhere in the documentation or in the release notes.
So question is “Is it a bug ? and what effect does it have on my earnings”

[bigdadboom]

Hi nerdatwork,

I’ll try that thanks.
The web dashboard is still missing some informations that the CLI gives

[BrightSilence]

@bigdadboom

I haven’t been able to read about it anywhere in the documentation or in the release notes.

Changelog v0.21.1

I feel like this time I have to write a bit more about the changes. Audit failures: We believe that we have identified the root cause. I can’t go into the details as long as the issues is not fixed. This release contains part 1 of the fix and as soon as part 1 is working we can go on and deploy part 2. If we are lucky that might be possible today. In this special case I don’t want to deploy part 2 on a Friday and I am not sure if we will have time for it around the town hall next week. I will …

@littleskunk

As a side effect you might see that the last_contact value on the CLI dashboard is not updated frequently. Especially on unvetted nodes.

[nerdatwork]

I agree web dashboard is missing many features but it’s first iteration so subsequent ones will make it awesome(r).

You should try this too to fix your Last contact.

Run powershell as admin

New-NetFirewallRule -DisplayName “Storj v3” -Direction Inbound –Protocol TCP –LocalPort 28967 -Action allow

[bigdadboom]

Thanks BrightSilence,

Seem like i missed that part.
Thanks for informing.