New errors…
Looks like v6.1 did not survived split.
Yes I think we have killed it again. Logs collecting and analysing now
same here…
Home$ safe cat safe://hygoyeyx768nkst7qqjjk8khjm67tr1n4otbctcts5j7dten43zae3ga83y > ~/safe-the-planet.png
Error: NetDataError: Failed to GET Public Blob: SelfEncryption(Storage("Generic error(Error received from the network: DataNotFound(Chunk(Public(c0189e(11000000)..))) MessageId: 5abc09c8..)"))
Not having much luck with these v6.x iterations…by the time I wake up here down under the net is usually down…
¯_(ツ)_/¯
Yip it’s failing way to fast as well.
ah, bummer … should have zipped to the end of the thread first! lol … I’d launch it and then it would stop …
Just crazy speculation, but is it possible the test-network is coming under attack - even in these early days? Obviously wouldn’t take much horsepower to attack a small testnet, just a fair bit of technical expertise and there are some three-letter agencies that maybe don’t want a safe network to exist as their jobs might just go out the window.
If someone doesn’t want SAFE to succeed in the long run, then why attack it now and make battle hardened against their attacks?
Assuming attacks are happening yet remain silent (there is no evidence of an attack), then the motive could be simple discouragement. As if such discouragement continues over and over again, it could drive away hodlers and cause problems long term for Maidsafe being able to keep going forward financially – as Maidsafe is a hodler and using Maid to pay for development.
Much speculation of course.
This is why I brought it up really - I want to know if such a silent attack would even be possible.
If it is, then I’d suggest taking the testnets to invite only participation. If not, then my worry is about nothing.
Crude attacks should be visible in logs and in monitoring software (excess usage of resources like CPU, RAM, etc.).
More complex attacks implies that someone knows how Safe Network works better than developers.
Which is not much realistic considering how fast code changes now.
gettin this
safe files put ./Safe_Nugget_catted.png
Error: NetDataError: Failed to PUT Public Blob: ErrorMessage { source: InvalidOperation("Not enough storage available on the network"), msg_id: d7340a83.. }
So I can put small <1MB files OK and I can also put larger files
willie@leonov:~$ safe files put 50MB.zip
FilesContainer created at: "safe://hyryyrbjq55xa3d4j1w5f4xty3hesgugssr435j171efcxzpiw3dknkyn7ynra"
+ 50MB.zip safe://hyfenrypeas11rj15cf3bxd9wopek14kk175d6665yadjoy8gphe6utp5er
willie@leonov:~$ safe cat "safe://hyryyrbjq55xa3d4j1w5f4xty3hesgugssr435j171efcxzpiw3dknkyn7ynra"
Files of FilesContainer (version 0) at "safe://hyryyrbjq55xa3d4j1w5f4xty3hesgugssr435j171efcxzpiw3dknkyn7ynra":
+-----------+-----------------+----------+----------------------+----------------------+--------------------------------------------------------------------+
| Name | Type | Size | Created | Modified | Link |
+-----------+-----------------+----------+----------------------+----------------------+--------------------------------------------------------------------+
| /50MB.zip | application/zip | 52428800 | 2021-06-25T08:17:04Z | 2021-06-25T08:17:04Z | safe://hyfenrypeas11rj15cf3bxd9wopek14kk175d6665yadjoy8gphe6utp5er |
+-----------+-----------------+----------+----------------------+----------------------+--------------------------------------------------------------------+
But when I try to retrieve it I get a zero length file…
willie@leonov:~$ safe files get "safe://hyryyrbjq55xa3d4j1w5f4xty3hesgugssr435j171efcxzpiw3dknkyn7ynra" T61gets/
File [1 of 1]: 50MB.zip
⠁ [00:00:00] [----------------------------------------] 0B/50.00MB (0B/s, 0s) Transfer
Done. Retrieved 1 files to T61gets/
willie@leonov:~$ cd T61gets/
willie@leonov:~/T61gets$ ll
total 8
drwxrwxr-x 2 willie willie 4096 Jun 25 09:25 ./
drwxr-xr-x 59 willie willie 4096 Jun 25 09:24 ../
-rw-rw-r-- 1 willie willie 0 Jun 25 09:25 50MB.zip
EDIT: on a second attempt at retreiving I get nearly a minute of download action but again a zero-length file
EDIT: If anyone does manage to retreive that file, it will not unzip but the md5 is
willie@leonov:~$ cat md5-50MB.txt
2699c63cb6699b2272f78989b09e88b1 50MB.zip
Looks like part of your file is lost.
d:\SN>safe cat safe://hyfenrypeas11rj15cf3bxd9wopek14kk175d6665yadjoy8gphe6utp5e
r > 50MB.zip
Error: NetDataError: Failed to GET Public Blob: SelfEncryption(Storage("Generic
error(Error received from the network: DataNotFound(Chunk(Public(6a2ed0(01101010
)..))) MessageId: ae1e6389..)"))
683 MB of incoming traffic are used by the way. More than 10 times file size.
yes I get the exact same message - at least we know which node is failing with what. Dunno if its any further use to the devs though.
I expect that some sections may work fine, some are not.
When you upload large file and get random chunk ids, there are too much chance of hitting problematic section.
With small file you have better chances.
I have wasn’t able to put anything… I wondered if those running a node have their requests normally put through that… in which case only those running a node perhaps uploaded?.. too much unclear on this one. Look forward to next.
same as @SmoothOperatorGR I have this message :
Error: NetDataError: Failed to PUT Public Blob: ErrorMessage { source: InvalidOperation(“Not enough storage available on the network”), msg_id: xxx… }
why do I still get not enough space in network?
any help?
Did you tried to create different safe keys?
It may be that problem is related to “old” keys.
Just a guess.
Because testnet v6.1 is having problems right now.
Most likely, you need to wait until testnet v6.2 or v7.
With present bugs it means nothing.
You should collect 10-20 such errors to be sure.
And even in that case it may be just because of bad testnet state now.
I tried many times last night, sometimes I got a network timeout, other times I get told to wait for 3 mins but mostly I got the IGD error. I will run from an AWS instance for the next testnet or I may be back at my own house where I have a fixed IP. Right now I am at my mothers house wit fast but non-fixed BT connection as I am looking after her for a few weeks at least.

