where is the logfile?
thanks! 208896021
how long is that piece of string?
where is the logfile?
thanks! 208896021
how long is that piece of string?
The one youāre loading into vdash - presumably you gave it the path on the command line?
Thank you everyone for the feedback and testing!
I hope you can all see the baby steps progress with these testnets - as the version numbers go up we squash bugs, but as expected in these early testnet stages, uncover 2 more! You have helped us immeasurably again in uncovering these lurking bugs in v4.2, weāll be going through all issues reported further in the next few days.
Thatās the team taking a well deserved break for the weekend now.
We will leave v4.2 up and running for as long as it remains usable, and we expect to iterate again around the middle of next week.
![]()
Thanks everyone at MaidSafe, have a well deserved break. ![]()
So, itās the only logfile and now works⦠cutting it back randomly, I canāt replicate it but will watch out for it.
If it now works I doubt there any point chopping it up. Maybe just some memory corruption as itās not reproducible. Hard to say if this is a bug or something else. Thanks for the update.
@Southside you can still be first!
cancelled the folder upload. Single pic upload works fine
safe://hygoygyqfqxdzco6498p87jkx1qwxjrhtw1dhfgtuhfiqn5ijh95ffes8to
Just random idea: was it possible for tool to read only part of log line?
Only by creating a separate file. It will parse whatever file you give it.
Just opened a
there, I went to open one on Tuesday then Friday came and went
What a week, thanks, everyone. That present should come soon too! As soon as I wake it will resume. Again we will have less code, more features and something a wee bit special. So simple everyone will understand. It will slot in nicely with these iterations and @Josh I think yer onto something ![]()
Well done everyone. What a team.
Loving the excitement here, fair play to all.
Could anyone clear up the āsafe keys create --test-coins --for-cliā mystery for me, what is going on there, what is that command supposed to be doing? Maybe 4 or 5 times Iāve been at that stage today, and it hung each time.
Except this time (after all sorts of messing around in the background, jumping around systems chasing unicorns and such) I waited and got:
[sn_client::connection_manager] ERROR 2021-04-23T20:14:09.963486267 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.16/src/connection_manager.rs:927] Error handling network info message: InsufficientElderConnections(4)
I imagine Iām making a silly mistake, anyone got tips? So hungry for chunkz. There just isnāt enough elders around to sort me out with the write access Iām dreaming of?
No more action there, Iām killing it.
Good night everyone, and huge thanks to team once again!
Itās not you, itās network flakiness. The bumps are being ironed out but there still seem to be erratic behaviour for various reasons.
Thanks, Iāll keep firing commands away and hoping for the best so. Got a new error message this time:
Error: Failed to connect: ConnectionError: Failed to connect to the SAFE Network: QuicP2p(Connection(TimedOut))
Ah Iāve a more solid question maybe - if getting write access with that command doesnāt work, can I still join as a node?
Iāve been trying alongside, and am getting āthe network is not accepting nodes right nowā. Which is fine, but Iām wondering if what Iām doing makes any sense, I was guessing the network would allow me to operate as a node even if I couldnāt write data?
That command connects to the network trying to generate some testcoins, so what you were seeing is just the same as we were all seeing with issues connecting to Elders on the network.
This particular command needs the Elders of a section to agree on giving it some free testcoins (this is a temporary feature as you can imagine), once the testcoins were given and assigned to a public key the CLI provided, the CLI then stores the key pair in ~/.safe/cli/credentials which is where CLI will look it up each time it needs to pay for storage, it uses the keypair stored there to sign all payment messages.
I hope that helps, but in summary, your issue is just the same as others not able to connect to enough Elders on the network to operate as a client.
Thereās no harm trying to connect but it might take a while and may not work at all. My cloud node ran fine for a few hours but then stopped seeing any messages. My laptop node didnāt get in at all so Iāve shut it down now. I think T4.2 might be struggling from now on but you might be lucky.