Use Hetzner 
@Toivo - apologies for the noise, that loud humming you may hear is me battering the bejasus out of a datacentre near you
No, I can’t remember why I named that server slimming-aid Im sure I thought it was funny at the time…
Faucet down before I could test…
Spare change, please?
83cc0239208a2ebc30741f1e1801eb0cc936a35b5f0ccae287b34779fb971b235ee50a25fb56f018606c6d978f9c1d68
Wallet address
1 Like
I tried but…
safe wallet send 20 83cc0239208a2ebc30741f1e1801eb0cc936a35b5f0ccae287b34779fb971b235ee50a25fb56f018606c6d978f9c1d68
[snip]
Connected to the Network
Failed to send NanoTokens(20000000000) to MainPubkey(PublicKey(03cc..42d8)) due to Transfers(CouldNotSendMoney("The transfer was not successfully registered in the network: CouldNotSendMoney(\"Network Error Could not retrieve the record after storing it:
a4bb9a9ce1ca4a7db83c6f5e50a97df3892408b0bbbe46180d5ca51d17cbd1b1(3e205d1bf578f76bdab6b95d35dffbb5f506656ecc626c8ef9638584b81df005).\")")).
Error:
0: Transfer Error Failed to send tokens due to The transfer was not successfully registered in the network: CouldNotSendMoney("Network Error Could not retrieve the record after storing it:
a4bb9a9ce1ca4a7db83c6f5e50a97df3892408b0bbbe46180d5ca51d17cbd1b1(3e205d1bf578f76bdab6b95d35dffbb5f506656ecc626c8ef9638584b81df005).").
1: Failed to send tokens due to The transfer was not successfully registered in the network: CouldNotSendMoney("Network Error Could not retrieve the record after storing it:
a4bb9a9ce1ca4a7db83c6f5e50a97df3892408b0bbbe46180d5ca51d17cbd1b1(3e205d1bf578f76bdab6b95d35dffbb5f506656ecc626c8ef9638584b81df005).")
Location:
/rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/convert/mod.rs:716
2 Likes
This is what I should have expected after my question was ignored 
Normally I’d agree but I think what we need is more nodes! I think we’re getting mass extinctions due to RAM usage and that is making the remaining ones really busy with replication. Mass uploading will be making it worse.
7 Likes
Thanks for trying, let me check if I got my wallet address wrong…
1 Like
Client downloaded file in 35.781483207s
Saved BegBlagAndSteal.mp3 at /home/ubuntu/.local/share/saf
e/client/BegBlagAndSteal.mp3
2 Likes
M, correct it was 
try this one @stout77
e5e38ab313a6ee8138a5562f54a0a0ff97af86814f011b53c5d39cc58be720d115be5d5559a40b919156d39d0ed1551951f69151a3b176006b41f4991900eb88c33c735f2331e082e61e16bf9a8b84ffd62ca75be2f947e463f52994ff734da94271542e77aefda08a45e4e8e7eba8662a8a04c95cd6218053477ac12ccf6221f761b336f4343c34c415e671dd8f6bb80cdaec789c10a1ca528400b45c27259af7a242b35007081d15f2fbc9353ae56cc62cc2c2dc7e79fb4de57b22ff000000000000005d94b20fb83fcc7eae9424bf95b4d9b8104236391822bb276754489b9183c3b024acd37c31f311d825f4d174b82e7a3192000000000000000100000000
3 Likes
@happybeing vdash died in a most ungraceful manner after I tried to send some tokens to @stout
I got a faceful of this…
and hammering ctrl-C is not helping
EDIT: had to kill the terminal - the beeping was getting on my tits
I don’t know how much of it is replication and how much is gossip, but I am running only 22 nodes and my 200/200 Mbit connection is maxed out most of the time.
4 Likes
Hi, @JPL,
Could you please send me the client log of the dead lock looping of 15 chunks you encountered?
Thank you very much.
6 Likes
My latency went from a usual 9ms to ~50ms it is hungry.
3 Likes
@stout77
try this as well
ef2576ed71c910354fa2bb28a5ddca285996e0c5799fd2e9891511fea2328b9b25dc34141133c830d6915e51f42b8610c44c2962ebf05e3614fc6fa4e85af169b574fcded4d7983a6e4b899dc1a5927d5e8a328b03e90b45f5e9c81b3311028dbeab44fbc8f7b28fd77354375f6ab84460ad38cfa30c9c85c896a5aa6ae66e6508d9c875113f3494a0b480ca5ba6fff889f3dfd9735e1d8968005c2ad340ef51cbdf6e0e5b6597e41553efaaa71107fa96950cfef0581ff7357213d0b43693633479610000000000000063b5ebad0b9318d5a397b092af6a8e9cd7134622d6d62be457c152e1c6d54d85eb2d1451217ce3d161a01affffaca57d95000000000000000100000000
3 Likes
How dare you, that’s just the matrix being revealed by the secret sauce of Rust.
What that actually is is your mouse moving over the window after the crash. I doubt it is to do with sending tokens in another terminal so we don’t know the cause 
.
One poss is that it was killed due to lack of system RAM. vdash doesn’t seem to be using too much RAM here so it may really be those naughty nodes you’re running. I show 678MB virtual memory and 1.2% of RAM being used by vdash with my 6/20 nodes still running.
4 Likes
My wallet skills are a bit rusty…but I believe the command was correct?
safe
wallet deposit --cash-note e5e38ab313a6ee8138a5562f54a0a0ff97af86814f011b53c5d39cc58be720d115be5d5559a40b919156d39d0ed1551951f69151a3b176006b41f4991900eb88c33c735f2331e082e61e16bf9a8b84ffd62ca75be2f947e463f52994ff734da94271542e77aefda08a45e4e8e7eba8662a8a04c95cd6218053477ac12ccf6221f761b336f4343c34c415e671dd8f6bb8000000000000005d94b20fb83fcc7eae9424bf95b4d9b8104236391822bb276754489b9183c3b024acd37c31f311d825f4d174b82e7a3192000000000000000100000000
Logging to directory: "/home/ubuntu/.local/sh
are/safe/client/logs/log_2023-11-13_17-23-08"
Built with git version: de52073 / main / de52
073
Error:
0: Could not deserialize specified hex str
ing to a CashNote: deserialized bytes don't e
ncode a group element
Location:
sn_cli/src/subcommands/wallet.rs:250
Backtrace omitted. Run with RUST_BACKTRACE=1
environment variable to display it.
Run with RUST_BACKTRACE=full to include sourc
e snippets.
receive
deposit is gone
2 Likes
We can certainly agree on that - the send tokens command was likely just the straw that broke the camels back here. All I saw was “killed” at the bottom of the vdash window which indicates an OOM event to me. Then it moved too fast for me to screengrab it.
I often see a couple of random chars after closing vdash but never mentioned it as it was no biggie. - This however seemed distinctly different and worthy of comment.
Thank you for the consistent improvements in vdash
1 Like
2 Likes
2 of 4
clientlogs-2.zip (99.9 KB)