Everything looks fine, just wait.
There is currently around 40k nodes which means with 6 nodes your chance to earn nanos is only 6/40000 for every chunk uploaded, and not many chunks are being uploaded now. In next few days the upload rate should go up, so you should start seeing some nanos coming.
It’s not so much about the nano’s more the fact I never see records in vdash despite there being data in the safenode data folders
So far the new nodes are humming along for me. All connected, no shuns, way less errors, almost equal puts and gets. Memory usage at a good 69 mb. Ill keep an eye on this and update later.
Is it wise to update the node software if my nanos haven’t been picked up yet? I keep reading the DAG bot has had updates but still not picking up my nanos. Can I check another way if my nanos have been send?
It won’t matter, either way is fine.
With the new nodes, after 2 hours, records and nanos in coming. Before thst it took days. Awsome!
My nodes haven’t received any nanos yet, will they be credited after the reset?
Also, the items:
show this status all the time.
How can I check if I have nanos or if they will be delayed? I’m checking ‘/rank’ on Discord, but the bot says I haven’t received any rewards for the nodes I’ve run.
Do you know how I can check it?
Thanks for sharing.
Notice there is a restart of node about 2 hrs before you collect the logs.
This might explain why your screen shot showing there is no record stored.
As I do see there are many succeeded record read from disk.
Meanwhile, seems your node is lucky (or unluckily) be a host of some critical stone spend, that there is certain amount of check/query/attempt-of-reput against it.
We have some on-going work might ease that, but need to wait to see.
Thanks again for your alert and sharing.
really appreciated
Did you use the Launchpad to do the reset? Or node manager?
The upgrade command generates an error in the CLI:
PS C:\Users\gggg> upgrade
upgrade : The term 'upgrade' is not recognized as the name of a cmdlet, function, script file, or operable program. Che
ck the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ upgrade
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (upgrade:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
In Launchpad I did reset nodes but Crtl+G still does not work, I can not change the number of nodes ie I can not add and launch nodes:
Can you give me some pointers?
I was keeping an eye on the zero record nodes for the past day at least so it wasn’t the restart. They’ve not suddenly been reset to zero. Also, the restart was due to a safenode-manager upgrade of all nodes which doesn’t seem to affect that.
but I do see 1765 Wrote record, last one is at 2024-06-11T19:17:15,
and 367412 Retrieved record from disk, last one is at 2024-06-12T16:57:02
which means records are really there
I’m a bit concerned, as after stopping nodes, updating via safenode-manager, and then starting nodes again, CPU usage is a tiny fraction of what it was before the update.
I assume that this means the nodes aren’t functioning, but vdash seems to show them as active.
Using TOP in Ubuntu, many safenode services are using 0 memory, and 0 CPU.
Obviously it’s fantastic if the update slashed resource requirements for CPU & memory dramatically, but I expect that’s not the case?
Any ideas what the issue could be, or how it might be resolved?
Edit: I got the update process wrong… retrying without adding peer worked.
I used the launchpad. Node manager is beyond me. Mine are all still stuck on ‘added’
Since the Beta launch I have been running nodes almost continuously on win 10 and win 11 machines. I never see any records appear in vdash for my nodes, despite my logs showing records. e.g
[2024-06-12T20:21:09.879633Z INFO sn_networking::record_store] Wrote record 22316a(7824027bc530c5371b04558587d5e49026eaf450240b1689e47308006d74bc2d) to disk! filename: 22316a86da2d7cc40d1b309ea9fffd9e05cf9b41a0827fc630dcb951ca6d7e8d
[2024-06-12T20:21:09.881169Z INFO sn_networking::cmd] Adding Record locally, for 22316a(7824027bc530c5371b04558587d5e49026eaf450240b1689e47308006d74bc2d) and NonChunk(ead970(11101010)…)
I think vdash counts those as PUTS.
From memory, the records figure comes from a message that says how many active records.
checked the code, I think vdash count Storage::Records by checking our Marker::CloseRecordsLen
but the calculation of that marker is currently disabled as node are supposed to accept ALL records in this round.
vdash uses the figures from the cost calculation message:
Ah, not aware of that.
I still see
/// Close records held (Used in VDash)
CloseRecordsLen(&'a usize),
in our code, hence think this is the one being checked.
if no longer used, could you raise a PR to remove it ?
(also, I think will be better to put a comment of used in VDash at the place of struct QuotingMetrics ?)
Checked the log of that node, it does never received a quote query .
bit unlucky ?
On the instructions for upgrading nodes, Jim mentions the following for safenode-manager users:
Note: Please don’t use the upgrade command this time around, as your nodes may not restart.
I had already done this for some VPS’, and wonder if there’s a fix, or if everything needs to be removed and reinstalled?
Nodes aren’t starting properly, even after re-trying the correct reset procedure.
Edit: Figured the problem - I was specifying a peer, which was messing things up. All good now with no peer specified.