When trying to create a few new “domain names” it made the first few in my list, then started giving me RESP BODY {"errorCode":-24,"description":"Unexpected error"} RESP BODY {"errorCode":-1502,"description":"FfiError::PathNotFound"}
errors no matter what I tried to give it. Is there a limit to how many I can have? I tried re-extracting the launcher to see if I had screwed with a config file too much… I know there are some pretty strict limits in place while the testing is in place, is this one of them?
Edit for clarity: the first line is me creating a file in my own NFS setup. The second is me creating that same name with the network:
Calling POST http://localhost:8100/nfs/directory
REQ BODY {"dirPath":"/domain","isPrivate":false,"isPathShared":true}
Calling POST http://localhost:8100/dns
REQ BODY {"longName":"domain","serviceName":"www","serviceHomeDirPath":"/domain
,"isPathShared":true}
My vault ran fine for a few hours but the logs didn’t look very good so I restarted the vault using keyboard interrupt and this is what I saw
INFO 22:04:38.941196700 [safe_vault safe_vault.rs:95]
Running safe_vault v0.8.0
=========================
INFO 22:04:41.791794600 [routing::core core.rs:1198] Running listener.
INFO 22:04:41.915628400 [routing::core core.rs:1768] Sending GetNetworkName request with: PublicId(name: 8846..). This can take a while.
ERROR 22:05:11.915947800 [routing::core core.rs:2187] Failed to get GetNetworkName response.
WARN 22:05:11.915947800 [safe_vault::vault vault.rs:134] Received Event::GetNetworkNameFailed. Restarting Vault
INFO 22:05:13.368818300 [routing::core core.rs:1198] Running listener.
INFO 22:05:13.478221800 [routing::core core.rs:1768] Sending GetNetworkName request with: PublicId(name: 7464..). This can take a while.
ERROR 22:05:43.479743300 [routing::core core.rs:2187] Failed to get GetNetworkName response.
WARN 22:05:43.479743300 [safe_vault::vault vault.rs:134] Received Event::GetNetworkNameFailed. Restarting Vault
INFO 22:05:44.880594500 [routing::core core.rs:1198] Running listener.
INFO 22:05:44.995183600 [routing::core core.rs:1768] Sending GetNetworkName request with: PublicId(name: 783b..). This can take a while.
ERROR 22:06:14.996345600 [routing::core core.rs:2187] Failed to get GetNetworkName response.
WARN 22:06:14.996345600 [safe_vault::vault vault.rs:134] Received Event::GetNetworkNameFailed. Restarting Vault
INFO 22:06:16.437215800 [routing::core core.rs:1198] Running listener.
INFO 22:06:16.549517100 [routing::core core.rs:1768] Sending GetNetworkName request with: PublicId(name: 4364..). This can take a while.
I ran vault at the start of this thread. It worked.
I finally started using both Launcher AND Demo App for the first time in my life, making a successful website.
I took a 3 hour nap. Now awake; Launcher disconnected/froze during sleep. (Demo App also disconnected.)
After closing Demo App and Launcher, restarting Launcher, it connects to the Network
But my account information/login fails after several minutes. The information should be correct.
Tried restarting Launcher multiple times, inputting my information multiple times.
Maybe I need to create a new Launcher account?
(I notice when starting Launcher that 2 Launcher EXEs run. One takes up half the memory of the other.
Not sure what that’s about.)
Tried creating a new Launcher account, with the same information. “Error in registration! Try Again.”
Tried again, with different information. Taking the usual several minutes. Even this says “Error in registration!”
Tried logging in Launcher again with my first once-successful (pre-nap) information. Still no go.
Conclusion: something’s up with Launcher .
Win7 64, router.
Able to login with launcher and connect to network but unable to authorize the demo app, it just hangs on the “Waiting on authorisation request” screen forever. Have tried restarting, same outcome. After about 5 minutes it gives up and says “could not connect to launcher, please leave it running” then closes the demo app.
OS X Yosemite 10.10.5, trying to run from Hong Kong
Running safe_vault v0.8.0
=========================
INFO 12:05:38.628810000 [routing::core core.rs:1198] Running listener.
INFO 12:05:39.070041000 [routing::core core.rs:1768] Sending GetNetworkName request with: PublicId(name: fc03..). This can take a while.
ERROR 12:06:09.074666000 [routing::core core.rs:2187] Failed to get GetNetworkName response.
WARN 12:06:09.074801000 [safe_vault::vault vault.rs:134] Received Event::GetNetworkNameFailed. Restarting Vault
INFO 12:06:26.046676000 [routing::core core.rs:1198] Running listener.
INFO 12:06:28.508463000 [routing::core core.rs:1768] Sending GetNetworkName request with: PublicId(name: 06bc..). This can take a while.
ERROR 12:06:58.511830000 [routing::core core.rs:2187] Failed to get GetNetworkName response.
WARN 12:06:58.511919000 [safe_vault::vault vault.rs:134] Received Event::GetNetworkNameFailed. Restarting Vault
So it’s been a little over 12 hours and almost 150 comments on the OP. This is really great you guys. And I’m sure it’s only getting started!
If you have an outstanding question/issue that has not been answered/figured out/hacked around yet, feel free to create a thread in the #support category to request the help of the community. Otherwise, you also have the option to create a bug report at the Maidsafe Jira Bug Tracker. You may do so with or without starting a thread in #support, however it is highly encouraged to do so first.
We don’t have a support information template yet, but please include anything that may be relevant in your report, such as Operating System, Network Architecture (e.g. directly connected or going through a router), host firewall settings (if any), and a step-by-step recreation of what led to the issue. Keep in mind that we’re still figuring all of this out at the same time that you are, but we’d be glad to lend an extra set of eyes to any issues that may arise.
These are exciting times.
NOTE: Please do not use the #bugs category. It is being deprecated in favor of #support and will be migrated to other appropriate categories (most likely #support) shortly.
Can confirm, network does not allow joining anymore.
When it worked it took ~30% of one i5 desktop core in virtualbox. Any kind of upload limiting seemed to cause the participation to malfunction. Upload limiting should be built into the vault if manually limiting it won’t work.
For now the network is out of consensus, so we will need to restart it. Give us a day or two to gather the logs now though before we do. Nice work folks. The Tcp traversal has been well tested and for sure seems to work now very well.
Not sure yet, we need to get the logs of all our machines, I suspect there is a subtle bug somewhere though. The network would recover from a lot of churn at the routing level. We did introduce a flag to prevent older nodes joining at the last minute. There may be an error there, so we have several hundred log files to sift through now I am sure we will find that one pretty quickly. It’s what the tests are fo so nice one.
Observations: The linux vault stayed at about 50% all the time, some win x64 vault pretty much immediately dwindled down to a few percents or even lower.
No harm in continuing to run, vaults are taking a while to start. Maybe best if we let it settle to get more log info. As long as nobody minds keeping going. We are looking just now at possible data loss, seems you can create new accounts etc. but there was a pretty large amount of nodes came in and went off, so we need to confirm that load as well.
If anyone is interested, here are the logs of the droplet nodes form last night. We are working through just now to map out the process.
[edit - fixed link]
There are 200 nodes there so it’s a lot of data, but should be worthwhile. We did not include GetNetworkName in stats count which is an error. Also we have a 30 sec timer to start a vault which may be too much in periods of high churn. We can check this now though, so good.
I have some constructive criticism and want to point out that upon every lunch of the luncher app 3 Firewall notifications appear and they seem very simillar. Maybe there is a way to reduce this to one?
Also, these messages pop up at every lunch of the app, even though I accepted everything yesterday.
My impression was that the vault was the most stable element, the launcher then the weaker link.
I don’t know, if the GUI launcher is set apart from the state of the connection it’s presenting but two improvements would be:
to have the launcher acknowledge when the connection to network has fallen over/reset, atm the GUI doesn’t change although the terminal notes the error and looks stalled. It’s seems only the app that suggests that launcher can’t be found that alerts user to the problem.
to have the launcher popup, rather than having to find it but perhaps that’s hard to do cross platform.
Visibility of the state of network and user’s interest in upload, will help with any frustrations or uncertainty.
I also wonder the browsing of SAFE websites isn’t necessarily safe for all, where a website links beyond SAFE content. I haven’t tried that but since it’s a normal browser, I’d expect clearnet content can be mixed. I don’t know if SAFE software can limit this or if users need to be wise about strict proxy setting that requires only SAFE content? Mixed websites might cause a problem, if the user is unaware of the limits they are working with??
network coming down again?
.
I am sure we will find that one pretty quickly. It’s what the tests are fo so nice one.