Looks like data loss is not fixed in this iteration of testnet 
1 Like
For those having issues with Windows running authd, please stay tuned we will have a new command on CLI in the next hour or so which would allow you to get testcoins for CLI without needing authd, we’ll be notifying here.
3 Likes
Hey @Vort, can you that confirm that uploading the same file once more gives a data already exists error?
Cool.
I can’t get by this command on Windows: $ safe auth create --test-coins
It just hangs with no response… 
1 Like
Might be something else going on. We’ve had both fails and succeeds from different users on same data.
1 Like
1 Like
hey @oetyng, getting some now:
MacBook-Pro-2:~ Home$ grep paid /Users/Home/.safe/node/local-node/sn_node.log
[sn_node] INFO 2021-04-16T00:20:02.424516+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000000575, paid amount: 0.000000575.)
[sn_node] INFO 2021-04-16T00:20:10.302486+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000000733, paid amount: 0.000000733.)
[sn_node] INFO 2021-04-16T00:20:15.110465+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000000314, paid amount: 0.000000314.)
[sn_node] INFO 2021-04-16T00:20:39.138459+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000000575, paid amount: 0.000000575.)
[sn_node] INFO 2021-04-16T00:21:50.330294+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000088244, paid amount: 0.000088244.)
[sn_node] INFO 2021-04-16T00:22:21.105174+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000089039, paid amount: 0.000089039.)
[sn_node] INFO 2021-04-16T00:22:27.721095+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000089039, paid amount: 0.000089039.)
[sn_node] INFO 2021-04-16T00:22:33.735420+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000000915, paid amount: 0.000000915.)
[sn_node] INFO 2021-04-16T00:22:39.765436+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000000965, paid amount: 0.000000965.)
[sn_node] INFO 2021-04-16T00:22:45.800256+10:00 [src/transfers/mod.rs:212] Payment: registration and propagation succeeded. (Store cost: 0.000002330, paid amount: 0.000002330.)
17 Likes
Nice man! That’s payments for data you’re seeing. Good! 
16 Likes
I am not sure if it worth to lose glitch state.
Can anyone else try to download my file?
This is good! You seem to be on track with the OP now, the hang issue is mentioned in there a couple of times. The important thing there is just to leave that window as is - do not kill it because it’s hanging. If you kill that or close that terminal window then that will kill the sn_authd process. So I’m hoping you are able to continue now with the proceeding steps.
PS your safe networks result looks good as well
3 Likes
In the meantime, this is the solution: Fleming Testnet v3 Release - * NOW OFFLINE - v4 RELEASED* - #154 by StephenC
I have better glitch example:
>safe cat safe://hygoyeymasmcyc86iehubpywh81eroedagqto1q1yfpthwwdbt8qb1qzw7o > test.png
Error: NetDataError: Failed to GET Public Blob: ErrorMessage(NoSuchData)
(~1MB file was there)
1 Like
Am trying but have had intermittent results all along with file dls. Not getting anything (not error either) from this one yet.
Edit: (trying the above as well)
uh oh… I’m seeing /home/runner/ errors from uploading as below
barf
[sn_client::connection_manager] ERROR 2021-04-15T15:26:49.397447455 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.10/src/connection_manager.rs:609] MessageId MessageId(2135ec…) was interrupted due to infrastructure updates. This will most likely need to be sent again. Update was : ErrorResponse { correlation_id: MessageId(2135ec…), error: TargetSectionInfoOutdated(SectionInfo { prefix: Prefix(10), pk_set: PkSet { public_key: PublicKey(0855…389f) }, elders: {91b2f2…: 138.68.182.161:34595, 9666a8…: 165.227.229.33:12000, a8ab5a…: 165.227.229.70:48326, aa4a60…: 95.216.206.201:54502, aee52d…: 139.59.162.138:52910, b6fb60…: 178.62.32.210:39347, ba9a09…: 188.166.175.92:33968}, joins_allowed: true}) }
[sn_client::connection_manager] ERROR 2021-04-15T15:26:49.579669586 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.10/src/connection_manager.rs:609] MessageId MessageId(2135ec…) was interrupted due to infrastructure updates. This will most likely need to be sent again. Update was : ErrorResponse { correlation_id: MessageId(2135ec…), error: DkgInProgress }
[sn_client::connection_manager] ERROR 2021-04-15T15:26:49.591263100 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.10/src/connection_manager.rs:609] MessageId MessageId(2135ec…) was interrupted due to infrastructure updates. This will most likely need to be sent again. Update was : ErrorResponse { correlation_id: MessageId(2135ec…), error: DkgInProgress }
[sn_client::connection_manager] ERROR 2021-04-15T15:26:49.614205396 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.10/src/connection_manager.rs:609] MessageId MessageId(2135ec…) was interrupted due to infrastructure updates. This will most likely need to be sent again. Update was : ErrorResponse { correlation_id: MessageId(2135ec…), error: DkgInProgress }
[sn_client::connection_manager] ERROR 2021-04-15T15:26:49.663847141 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.10/src/connection_manager.rs:609] MessageId MessageId(2135ec…) was interrupted due to infrastructure updates. This will most likely need to be sent again. Update was : ErrorResponse { correlation_id: MessageId(2135ec…), error: TargetSectionInfoOutdated(SectionInfo { prefix: Prefix(10), pk_set: PkSet { public_key: PublicKey(0855…389f) }, elders: {91b2f2…: 138.68.182.161:34595, 9666a8…: 165.227.229.33:12000, a8ab5a…: 165.227.229.70:48326, aa4a60…: 95.216.206.201:54502, aee52d…: 139.59.162.138:52910, b6fb60…: 178.62.32.210:39347, ba9a09…: 188.166.175.92:33968}, joins_allowed: true}) }
[sn_client::connection_manager] ERROR 2021-04-15T15:26:49.711494828 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.10/src/connection_manager.rs:609] MessageId MessageId(2135ec…) was interrupted due to infrastructure updates. This will most likely need to be sent again. Update was : ErrorResponse { correlation_id: MessageId(2135ec…), error: DkgInProgress }
[sn_client::connection_manager] ERROR 2021-04-15T15:27:04.038807722 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.10/src/connection_manager.rs:609] MessageId MessageId(2135ec…) was interrupted due to infrastructure updates. This will most likely need to be sent again. Update was : ErrorResponse { correlation_id: MessageId(2135ec…), error: DkgInProgress }
I guess that noone with old nodes can be joining; so, everyone has refreshed… rather surprised then to see those again.
@oetyng, reward_secret_key balance still at 0 though; is that normal?
SafeKey’s current balance: 0.000000000
There is a chance, next iter will include a version check on all apps/nodes and will error out on wrong version. We could be seeing old nodes doing some weird things here.
3 Likes
Another split, but no promotion for me! 
[sn_node] INFO 2021-04-15T15:26:36.321715171+01:00 [src/event_mapping/mod.rs:44] Handling RoutingEvent: EldersChanged { prefix: Prefix(11), key: PublicKey(1501..dc5e), sibling_key: None, elders: {c8716e.., d6f7d6.., dd263d.., e210b2.., ee6e97.., f77f5c.., fc41f7..}, self_status_change: None }
[sn_node] INFO 2021-04-15T15:26:36.331822049+01:00 [src/node/handle.rs:27] Handling NodeDuty: No op.
[sn_node] INFO 2021-04-15T15:27:02.537697129+01:00 [src/event_mapping/mod.rs:44] Handling RoutingEvent: EldersChanged { prefix: Prefix(110), key: PublicKey(0d5f..f718), sibling_key: None, elders: {c621ad.., c6ee1e.., c8716e.., cfeb37.., d6f7d6.., dd263d..}, self_status_change: None }
[sn_node] INFO 2021-04-15T15:27:02.537926514+01:00 [src/node/handle.rs:27] Handling NodeDuty: No op.
I’m trying to check the balance on my reward_secret_key, but it is very slow to respond.
5 Likes
Now data directory also contains immutable_data.db, holder_data.db, full_adults.db and new directory transfers with a lots of .db files!
[tokio-runtime-worker] INFO 2021-04-15T17:27:05.061692900+03:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\sn_routing-0.60.3\src\routing\core.rs:1808] Split
[tokio-runtime-worker] INFO 2021-04-15T17:27:05.061692900+03:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\sn_routing-0.60.3\src\routing\core.rs:1815] Section updated: prefix: (110), key: PublicKey(0d5f..f718), elders: c621ad.. at 138.68.167.124:43149, c6ee1e.. at 109.87.25.148:56059, c8716e.. at 178.62.10.198:51741, cfeb37.. at 46.101.17.63:46664, d6f7d6.. at 165.227.229.71:54735, dd263d.. at 165.227.229.142:60960
[tokio-runtime-worker] INFO 2021-04-15T17:27:05.118704300+03:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\sn_routing-0.60.3\src\network\stats.rs:18] *** Exact total network elders: 41 ***
[tokio-runtime-worker] INFO 2021-04-15T17:27:05.119704500+03:00 [C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\sn_routing-0.60.3\src\routing\core.rs:1843] Promoted to elder
[sn_node] INFO 2021-04-15T17:27:05.124705500+03:00 [src\event_mapping\mod.rs:44] Handling RoutingEvent: EldersChanged { prefix: Prefix(110), key: PublicKey(0d5f..f718), sibling_key: Some(PublicKey(011f..d353)), elders: {c621ad.., c6ee1e.., c8716e.., cfeb37.., d6f7d6.., dd263d..}, self_status_change: Promoted }
3 Likes
OP url
safe cat safe://hygoygyx69nhu8c3b4xcqgi54dibt1rpewz8qg3eq7tx5chb587gj6tst9e
hanging there for a long while for me, with no errors…
You guys rolled out v3 at lightning speed 
10 Likes