This works out great, the sun is not up yet and the wind only starts in a few hours. Who said a man cannot have it all 
5 Likes
I get an error when trying to check my balance:
PS C:\Users\gggg> safe wallet balance --peer-id=12D3KooWKfCFmruR1eVFpApexCb9XJgUpUAxsy7qmmv4saZbM87T
safe : The term 'safe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check 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
+ safe wallet balance --peer-id=12D3KooWKfCFmruR1eVFpApexCb9XJgUpUAxsy7 ...
Anyone know what this is about?
No Safe, no wave.
Safe command is not in your path. Don’t know how fix that in windows.
2 Likes
I’ll need to check out your suddoers when I get back to a keyboard.
just sudo visudo then update default secure_path to include .local/bin
1 Like
Anyone started nodes yet? I just started mine in the usual fashion and apart from 100 errors none of them is showing any activity. Never seen this before:
I don’t have a peer set in the environment so not sure what might cause this. I’m leaving this to go code now.
I’ve retried with same result. Looks healthy until it tries to dial. Here’s the log for one node: safnode.zip (6.1 KB)
6 Likes
I have records.
5 Likes
Hmm, I started up 200 nodes, only about 12 records on average per node so far:
I always set a SAFE_PEERS environment for now prior to running safenode-manager (though I am not passing in --peer to it), but it is adding the peer automatically to the /etc/init.d/safenodeX on alpine service definition as part of the command line args).
2 Likes
That’s great news, 2x more nodes per machine from last testnet. Great progress, team! 
7 Likes
I started one. Vdash says I have 18 PUTs but zero records. My record folder has 18 items.
2 Likes
Guessing the aim here is to see how many they can safely run per droplet for beta.
1 Like
The same problem occurs when trying to retrieve tokens from tap:
PS C:\Users\gggg> safe wallet get-faucet 188.166.171.13:8000
safe : The term 'safe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check 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
+ safe wallet get-faucet 188.166.171.13:8000
Anyone else having the same problem on Windows?
No Safe, no wave.
1 Like
Worked for me on Windows.
I only have 25 nodes and just got my first rewards Rewards balance: 0.000000010 has your fortune changed?
1 Like
Noting similar behavior across multiple node’s log files so far (uptime for about 90 minutes now):
Overall Summary (Single Node):
- 1008 unique Peer Ids encountered or logged on disk
- 2764 unique udp IPv4 IP/Port combination encountered or logged on disk
Bad Peer Summary:
- 0 unique Peer Ids blocked
→ 0% of all unique Peer IDs encountered were blocked - 0 unique Peer IDs were marked as cleaning out bad_peer
→ 0% of all unique Peer IDs encountered were marked as ‘cleaning out bad_peer’ - 961 unique Peer IDs were marked as cleaning out peer
→ 95% of all unique Peer IDs encountered were marked as ‘cleaning out peer’
Incoming Connection Errors Summary:
- 8 unique IP/Port with IncomingConnectionError
→ .28% of all unique IP/Port encountered had an IncomingConnectionError - 6 unique IP/Port with IncomingConnectionError + HandshakeTimedOut
→ .21% of all unique IP/Port encountered had an IncomingConnectionError + HandshakeTimedOut - 2 unique IP/Port with IncomingConnectionError + APPLICATION_ERROR
→ 0.07% of all unique IP/Port encountered had an IncomingConnectionError + APPLICATION_ERROR
Outgoing Connection Errors Summary:
- 961 unique Peer Ids with OutgoingConnectionError
→ 95% of all unique Peer IDs encountered had a OutgoingConnectionError - 961 unique Peer IDs with OutgoingConnection Error + HandshakeTimedOut
→ 95% of all unique Peer IDs encountered had an OutgoingConnectionError + HandshakeTimedOut
Replication Fetcher Summary:
- 0 Unique Peer IDs with ‘Incoming record_key is out of range, do not fetch it from PeerId’
→ 0% of all unique Peer IDs encountered were marked as ‘incoming record_key is out of range’
Initial Observations:
-
Bad Peer blocked is basically near a very low level, I saw raw counts of 0 or 1 so far, but as a percentage (really low so far) (reduced significantly from prior testnet)
-
Incoming Connection error with and without HandshakeTimedOut is near 0% (reduced significantly from prior testnet)
-
Somehow the outgoing connection error is very high rate (increased signficantly) at least for me
-
Replication Fetcher logging is not showing up for now in the logs (reduced significantly) (expected)
-
FWIW, its interesting to note that “cleaning out peer” count is 961, which also matches “OutgoingConnectionError” with HandshakeTimedOut count. These # were a different number, but the same number for both metrics on another node’s log files too (1:1 ratio).
Note: Too early in the testnet phase yet, but I will be away from computer for next few hrs, I will check back later. I am glad I got to participate in the testnet as an early node provider in terms of the time frame, as oppose to way late in the testnet. Lets see how the rewards and earning tokens pan out… 
.
5 Likes
I sent some money to my node’s public key. Does not show up in the node wallet, or when checking a balance for that wallet. Maybe it’s not even supposed to, just making a not for the record.
Not yet, will take a look in a few hours. Currently, all nodes have 0 balance still.
Are you guys uploading? If you are like you used to in the previous testnets, I think we have a vast number of nodes online.
EDIT: Or the data does not get replicated… 
1 Like
Not uploading yet unfortunately! Got some work to do before playtime.
I’ve started my traditional 1 node in AWS and 5 from home though. Most of them have a small amount of earnings already.
1 Like
Started 11 nodes. First time doing it “manually” without the community scripts and stuff. 1 created with safenode manually, another 10 with node-manager. Vdash shows the first one already earning.
EDIT:
All but 2 earning already. Starting uploads.
4 Likes