Is there a grep @aatonnomicc and I can do on our nodes that died (or got booted) to see why?
I lost only 1 of 75 shortly after starting. Keen to know why.
Is there a grep @aatonnomicc and I can do on our nodes that died (or got booted) to see why?
I lost only 1 of 75 shortly after starting. Keen to know why.
Nope
but I got a Not all chunks were retrieved, expected 1004, retrieved 79
, error
Client download progress 1002/1004
Client download progress 1003/1004
Client download progress 1004/1004
Client downloaded file in 635.757658538s
Error downloading "Neuromancer.mp4": Chunks error Not all chunks were retrieved, expected 1004, retrieved 79, missing [6793a5(01100111).., acbb48(10101100).., 904872(10010000).., 207a4a(00100000).., 4c0f40(01001100).., c5b2a4(11000101).., 2ed6fc(00101110).., c66803(11000110).., f6660d(11110110).., 4c2995(01001100).., e525e7(11100101).., f3cc68(11110011).., 5c761a(01011100).., 045d8c(00000100).., 6bfc1d(01101011).., cee331(11001110).., 2943ef(00101001).., f0da00(11110000).., 425166(01000010).., 1f8af9(00011111).., 2c6c56(00101100).., 89af89(10001001).., 62d7c3(01100010).., fedd1e(11111110).., bd0e18(10111101).., f34e39(11110011).., 78a643(01111000).., 1633b8(00010110).., 993945(10011001).., b56048(10110101).., b4af4e(10110100).., 34f93a(00110100).., 912e72(10010001).., 0572cb(00000101).., 309aa5(00110000).., a7f678(10100111).., a28939(10100010)..
, blah blah for another few screens
I saw it had died from your node checking script and in its logs it was running fine till it just stopped.
Same here I’d be interested to knowhow to figure out the why it stoped
I’d like to know what that message means exactly. What’s stopping them from being retrieved?
It is strange to see error at all after lines like
Client download progress 1004/1004
Client downloaded file in 635.757658538s
It’s like progress bar going up to 100% to show error after that.
It is either 100% or error, it can’t be both.
What should be the final file size for this file?
I get 11M
willie@gagarin:~$ ls -alh .local/share/safe/client/Neuromancer.mp4
-rw-rw-r-- 1 willie willie 11M Sep 23 13:48 .local/share/safe/client/Neuromancer.mp4
and about 5 secs of
I will try again with client logging on this time.
I must have screwed up somehow with the logging…
same(ish) result as before - crapped out after 67 chunks/
My safe.log was empty. What did I do wrong with this command?
willie@gagarin:~$ SN_LOG=ALL safe --log-output-dest=datadir files download -c50 Neuromancer.mp4 0a6b07c380372d1d7f23a5783d97ddbe5c2358db9df38aeb625c38a7c3562aa5
An empty log was written to ~/datadir/safe.log
Maybe data-dir rather than datadir
Have to run now – I’ll try again when I get back if somewhat sober.
Hmpfh… I just found out that my high earning node was disconnected in the morning. NAT status was suddenly deemed private.
How, why? It had been running fine until then.
Can my ISP be a culprit here somehow? Yesterday evening my WiFi halted totally, but after connecting with cable everything was working well again until about eight in the morning.
I checked that my IP has not changed.
I’m AFK now, but I want to ask is it a bad idea to share my logs publicly? There is my IP, open port etc. Are there some risks there?
Silly question: would running a VPN with dedicated fixed IP prevent NAT being an issue for those running behind home routers, or not at all?
I think nat traversal is coming very soon, so we should be ok. VPN etc. can be good but so many options there
I would say there would be some risks there. I think you can trust most of us to not try to hack or ddos or find your identity but who knows?
It’s maybe slightly less of a worry if your IP changes every time your router reconnects but some people are lucky and have the same IP for years. And some pay for that privilege.
I would do this:-
sed -i 's/123.456.789.101/xxx.xxx.xxx.xxx/g' safenode.log
where 123.456.789.101 is your IP.
If you are using an uncommon port someone who is running a node might still be able to find your IP by searching through their logs for your port. So replace that with yyyyy.
sed -i 's/12345/yyyyy/g' safenode.log
They could also still find your IP by looking through their logs for your peer_id, the really long string like ‘12D3KooWAPhXYaEaFc3bdvbZZLGY7Pau2C1EMsxCJVKSEe7j4fQe’
So to make sure your tin foil hat is securely fastened replace that as well.
sed -i 's/12D3KooWAPhXYaEaFc3bdvbZZLGY7Pau2C1EMsxCJVKSEe7j4fQe/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz/g' safenode.log
I don’t think any of this is over the top at all! If I share logs from a node or client running at home I’ll do all that.
Edit:
Those commands just put the output on the screen.
Here is a command line that will do the lot:-
sed --in-place='.bak' 's/123.456.789.101/xxx.xxx.xxx.xxx/g; s/12000/yyyyy/g; ; s/12D3KooWEL5hcYwtfzSApPwQdEfde2KTquGiiYemwPBgPG7Ftdmn/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz/g' safenode.log
and writes the new file over the old one while backing up the old one to safenode.log.bak
Edit:
I forgot that ‘g’ at the end of the last clause!
It should be above 500mb as .mp4
I’ve successfully uploaded many many files of all sizes now … looking pretty good!
I’d say we have a solid FOUNDATION here.
Uploaded Isaac Asimov – Foundation Series.tar.gz to 014aa230723e5597da53aa1d164671f8894fe1874e7d324e5b9df04f62f6618a
no chance - reeeling from my first knockback in 30 years. Couldn’t get into McSorleys (very grungy musuic bar) cos I was wearing joggers.
Bouncer obv hadnt had his hole in months and needed some way to reassert his toxic masculinity - or something like that…
My very first nodes are patiently waiting on my Rpi at home for this blessed day
Added some spit and polish, now that the foundations are in I hope to add some additional metrics.
I have tested uploading files with several computers (Osx and Windows) and it works on all of them.
It even works on an old laptop with windows 7. On this last one PowerShell gave me installation errors but I was able to fix it by downloading the client from Github.
A big step forward…
Straight slanted lines on memory graph looks like sign of memory leak.
Sometimes with more time passed lines begin to curl and start looking more like logarithm.
But if not, then destination is infinity.