INFO 2020-06-12T06:03:37.300892658+03:00 [src/bin/safe_vault.rs:114]
Running safe-vault v0.24.0
==========================
INFO 2020-06-12T06:03:37.421079055+03:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/igd.rs:117] Fetched IP address from IGD gateway: V4(192.168.1.111)
INFO 2020-06-12T06:03:37.423424205+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/mod.rs:129] f11785.. Bootstrapping a new node.
INFO 2020-06-12T06:03:37.423579561+03:00 [src/vault.rs:128] Initializing new Vault as Adult
INFO 2020-06-12T06:04:07.424083553+03:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:543] Node 167.172.55.70:12000 is unresponsive, removing it from bootstrap contacts; 0 contacts left
INFO 2020-06-12T06:04:07.424421606+03:00 [src/bin/safe_vault.rs:156] Vault connection info: "192.168.1.111:38760"
INFO 2020-06-12T06:04:07.425737352+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/mod.rs:468] f11785..(?) Failed to bootstrap. Terminating.
Iām going to tinker with those parameters too I had just forgotten my password so have to punch in the serial number of the router to login. On the net gear site they imply they donāt have UPnP on by default (was yours?) because it can be used maliciously. The default time for it to be open if on is 30minutes apparently which I thought of increasing as much as possible, apply changes and try. If no joy maybe reboot the router and try again.
Hi @Traktion
Could you share a little more information please? This could fail for different reasons. Could you share the logs a little before that error as well?
Sure! I have a standard Talk Talk freebie router at the moment. I could try setting up one of my others, but this one came with the deal.
It does have uPnP enabled from the web admin UI, so I think it should be working if it was going to.
Running safe-vault v0.24.0
==========================
INFO 2020-06-11T19:19:20.794306313+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/igd.rs:117] Fetched IP address from IGD gateway: V4(192.168.1.16)
INFO 2020-06-11T19:19:20.795493227+01:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/mod.rs:129] f49e25.. Bootstrapping a new node.
INFO 2020-06-11T19:19:20.795808032+01:00 [src/vault.rs:128] Initializing new Vault as Adult
INFO 2020-06-11T19:19:21.139093884+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:335] IGD request failed: Could not use IGD for automatic port forwarding - IgdAddPort(RequestError(InvalidResponse("<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"><s:Body>\n<u:GetExternalIPAddressResponse xmlns:u=\"urn:schemas-upnp-org:service:WANIPConnection:1\">\n<NewExternalIPAddress>88.107.111.115</NewExternalIPAddress>\n</u:GetExternalIPAddressResponse>\n</s:Body></s:Envelope>\u{0}")))
ERROR 2020-06-11T19:19:21.139323554+01:00 [src/bin/safe_vault.rs:169] Cannot start vault due to error: Routing(Network(IgdNotSupported))
ERROR 2020-06-11T19:19:21.139389539+01:00 [src/bin/safe_vault.rs:170] Automatic Port forwarding Failed. Check if UPnP is enabled in your router's settings and try again. Note that not all routers are supported in this testnet. Visit https://forum.autonomi.community for more information.
Last log line for me is: INFO 2020-06-12T00:58:12.514167400+03:00 [src\vault.rs:517] Responded to our data handlers with: Response { response: Response::Mutation(Success), requester: App(PublicKey::Bls(b630d6..), owner: PublicKey::Bls(8bd447..)), message_id: MessageId(82dd4b..), refund: None }
(about 9 hours ago)
Not sure if it is hanged or not. Will wait more time for now.
I am alone with a vault from home that worked at one time and then later not connecting anymore?
What happened to me:
Yesterday I build a vault from source and it worked.
Then I stopped it because it was compiled in debug mode.
I rebuilt it in release mode
Since then all connection attempts failed, both in release mode and debug mode
Errors:
Running safe-vault v0.24.0
==========================
INFO 2020-06-12T09:49:47.751039372+02:00 [/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/mod.rs:129] 9a4152.. Bootstrapping a new node.
INFO 2020-06-12T09:49:47.751440976+02:00 [src/vault.rs:133] Initializing new Vault as Adult
INFO 2020-06-12T09:50:17.753046365+02:00 [/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:543] Node 167.172.55.70:12000 is unresponsive, removing it from bootstrap contacts; 0 contacts left
INFO 2020-06-12T09:50:17.753252041+02:00 [/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:335] IGD request failed: Could not find the gateway device for IGD - IgdSearch(IoError(Custom { kind: TimedOut, error: "search timed out" }))
Cannot start vault due to error: Routing(Network(IgdNotSupported))
ERROR 2020-06-12T09:50:17.753365483+02:00 [src/bin/safe_vault.rs:175] Cannot start vault due to error: Routing(Network(IgdNotSupported))
ERROR 2020-06-12T09:50:17.753401226+02:00 [src/bin/safe_vault.rs:176] Automatic Port forwarding Failed. Check if UPnP is enabled in your router's settings and try again. Note that not all routers are supported in this testnet. Visit https://forum.autonomi.community for more information.
Automatic Port forwarding Failed. Check if UPnP is enabled in your router's settings and try again. Note that not all routers are supported in this testnet. Visit https://forum.autonomi.community for more information.
The testnet was running smoothly until 23:00 GMT. Around that time, there was a series of events which led to a sudden spike in memory usage in the vault process which eventually led to the process being terminated by the operating system. We are investigating the logs and we have a few leads to help identify the source of the bug. We shall keep you updated with more information. The testnet will be restarted once the bug is resolved. We look forward to your continued participation in the upcoming testnets.
Just wondering how the network can resist being flooded with too much too quickly, whether thereās option to refuse new uploads if the network is busy settling existing dataā¦ just a polite, cannot upload - please try again later. Unclear to me how coherent the networkās awareness is but perhaps each section would prioritize and the sum of that is a refuse.
I donāt know if that was the case on this occasion, with no suggestion to be gentleā¦
I think it should be, although I havenāt recently tried any type of cross-compilation, I saw a recent thread about it though: SAFE Network App for ARM?
Thanks, that sounds good enough to give it a go if only can get hold of a musl build for ARM. But I just saw that the test-net will continue when restarted so that gives some time to prepare.
Yes, and just in case you are interested in more fun , you could even run your own section in any server/PC (with safe vault run-baby-fleming), and try to have you vault from the Pi to join it.
Iām not sure if the IGD detection may play a bad role in an scenario the section and the Pi are on the same LAN, but if you try it, share your findings.
That kind of fun I think could be something for maybe @tfa . I have a few years old Intel i5 4.5Ghz with mobo but it lacks psu, ram, cooler and case. Would be fun to get to use that some day, when I get hold of some parts.
@bochaco It seems I am also in interactive mode and was wondering if this may have contributed to the problems I had yesterday? I cant for the life of me work out how to launch the cli not in interactive mode
, you could even run your own section in any server/PC (with 
I have a few years old Intel i5 4.5Ghz with mobo but it lacks psu, ram, cooler and case. Would be fun to get to use that some day, when I get hold of some parts.