MaidSafe Dev Update - February 2, 2017 - Test 12

Back on safe_vault on the NFS, I checked if it had the quarantine attribute with xattr -p and it had none.
Anyways, I deleted the quarantine flag, and attempted to execute it again:

➜  safe_vault-v0.13.0-osx-x64 xattr -d com.apple.quarantine safe_vault
➜  safe_vault-v0.13.0-osx-x64 ./safe_vault
log4rs: Error deserializing component: Could not establish log file path: Io(Error { repr: Os { code: 45, message: "Operation not supported" } })
log4rs: Error creating config: Reference to nonexistent appender: `async_file`
log4rs: Error creating config: Reference to nonexistent appender: `async_file`
INFO 14:10:16.295700000 [safe_vault safe_vault.rs:95] 

Running safe_vault v0.13.0
==========================
Cannot start vault due to error: FileHandler(Io(Error { repr: Os { code: 45, message: "Operation not supported" } }))
ERROR 14:10:16.296823000 [safe_vault::vault vault.rs:51] Config file could not be parsed: Io(Error { repr: Os { code: 45, message: "Operation not supported" } })

Still the same error.

On the safe_vault on /tmp:

➜  safe_vault-v0.13.0-osx-x64 cd /tmp/safe_vault-v0.13.0-osx-x64 
➜  safe_vault-v0.13.0-osx-x64 ./safe_vault
INFO 14:12:51.714337000 [safe_vault safe_vault.rs:95] 

Running safe_vault v0.13.0
==========================
INFO 14:12:55.349420000 [routing::states::node node.rs:1268] Node(f6bf10..) Requesting a relocated name from the network. This can take a while.
INFO 14:13:55.385985000 [routing::states::node node.rs:2322] Node(f6bf10..) Failed to get relocated name from the network, so restarting.
WARN 14:13:55.396090000 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 14:13:59.088821000 [routing::states::node node.rs:1268] Node(645e50..) Requesting a relocated name from the network. This can take a while.

So there is something about being on a nfs that it doesn’t like.

1 Like

Willie, the Scottish bard’s talent for words lives on in you. “Bored” it is then, to watch so many English triumphs :laughing:

2 Likes

How will the dynamic performance monitoring be implemented? Seems wasteful to profile the performance for so long when joining especially since it offers no guarantees the vault actually delivers bandwidth to nodes once joined.

Currently i have been trying to reach resource check for an hour without luck.

Last time I had an english triumph it leaked oil, vibrated like a pneumatic drill and was considerably slower than my mates Honda.
Also spent more time on it with a spanner in my hand than on the handlebars.

English triumphs – we laff.

PS are we far enough off-topic yet?

4 Likes

Lol, :laughing:

Well that’s the Midlands for you, hardly England old friend. We built a fence around London (called the M25) for similar reasons but we never got around to the Midlands.

What do you drive now? I inherited a Mondeo from my almost famous dad.

PS are we far enough off-topic yet?

Don’t worry, moderation has become a bit lax since the good old days, don’t you think? :wink: I blame the foreigners. Only this week we’ve got “foreign” all over the shop, Chinese to Spanish, even bloody French. They’ll add Gaelic next, you see.

1 Like

Its just for now, because the network isn’t optimised yet, so they want to make sure it runs decently in this test. Later on, even slow bandwidth nodes will be able to join, they just might not be able to store chunks, or only archived ones that are barely used. Thats a rough explanation though.

Happily for this being, it is now over a decade since I owned any english manufactured vehicles.
My varied collection of French stuff with the superbly reliable XUD and HDi engines from PSA/Citroen just keep rolling along - often on recycled chip fat in the summer.
When MAID hits 50k satoshi, I’ll maybe have enough to start thinking about restoring my 1985 Merc coupe - last of the "real " W123 Mercs

A mate has spent £15k+ and 10 years restoring a Triumph TR6 - £800 second-hand Mazda MX5s run rings round it every time he takes down to the track at Kames.
His blood pressure is often far higher than the oil pressure in that heap (very nicely polished though)
Absolutely hates when I say “All show, no go” - cos its true :smiling_imp:

1 Like

Is anyone else having trouble loggin in? The launcher keeps rejecting me due to timeout.

Like this ?

INFO 14:48:13.352147762 [routing::states::node node.rs:2322] Node(ffcca3..) Failed to get relocated name from the network, so restarting.

WARN 14:48:13.352393682 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 14:48:16.594952639 [routing::states::node node.rs:1268] Node(6d6494…) Requesting a relocated name from the network. This can take a while.

Been a couple of hours now – can’t get connected at all. Same set up just danced in last night around midnight… :frowning:

No, that’s the vault. It’s trying to find a free space in the network → see this.
Although I must say that sounds very long…

I’m talking about the launcher to access the safenet.

1 Like

No luck connecting with a vault for hours now.

Are we DDoSing ourselves?
INFO 15:21:54.419186293 [routing::states::node node.rs:2322] Node(4b9944…) Failed to get relocated name from the network, so restarting.
WARN 15:21:54.419368851 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 15:21:57.561906948 [routing::states::node node.rs:1268] Node(91e728…) Requesting a relocated name from the network. This can take a while.

I had the same problem or so it appears, as many of you with launching and establishing a running vault. I just closed the launcher and restarted it. Then after about 15 mins of vault reconnects it was up and running.

Something no right - it finally goes through the resource performance check then chucks it.
Just to stress - this is exactly the same set up that worked flawlessly last night - only stopped it cos I screwed up with a daft 5am mistake.

    INFO 15:35:35.178524392 [routing::states::node node.rs:2322] Node(9fe3f5..) Failed to get relocated name from the network, so restarting.
WARN 15:35:35.178733008 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 15:35:38.220622758 [routing::states::node node.rs:1268] Node(5f605f..) Requesting a relocated name from the network. This can take a while.
INFO 15:35:59.126052522 [routing::states::node node.rs:1913] Node(d7ed9b..) Received relocated name. Establishing connections to 12 peers.
INFO 15:35:59.153141149 [routing::states::node node.rs:1045] Node(d7ed9b..) Starting approval process to test this node's resources. This will take at least 300 seconds.
INFO 15:36:29.126097488 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 380/410 seconds remaining.
INFO 15:36:59.126189342 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 350/410 seconds remaining.
INFO 15:36:59.639742767 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped d4d397.. from the routing table.
INFO 15:36:59.945282492 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped d4d397.. from the routing table.
INFO 15:36:59.999086268 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped cc3c25.. from the routing table.
INFO 15:37:00.403856487 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped d8b212.. from the routing table.
INFO 15:37:00.755870305 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped d8b212.. from the routing table.
INFO 15:37:02.858340275 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped cca738.. from the routing table.
INFO 15:37:29.126303129 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 320/410 seconds remaining.
INFO 15:37:59.126417458 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 290/410 seconds remaining.
INFO 15:38:29.126509440 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 260/410 seconds remaining.
INFO 15:38:59.126612172 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 230/410 seconds remaining.
INFO 15:39:29.126701901 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 200/410 seconds remaining.
INFO 15:39:59.126811984 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 170/410 seconds remaining.
INFO 15:40:29.126893508 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 140/410 seconds remaining.
INFO 15:40:59.127006695 [routing::states::node node.rs:2304] Node(d7ed9b..) All 7 resource proof responses fully sent. 110/410 seconds remaining.
INFO 15:41:10.301283203 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped cc56fe.. from the routing table.
INFO 15:41:10.304598832 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped c13323.. from the routing table.
INFO 15:41:10.307571987 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped dca966.. from the routing table.
INFO 15:41:10.309011734 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped c6b7a5.. from the routing table.
INFO 15:41:10.309773147 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped d14835.. from the routing table.
INFO 15:41:10.310587285 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped d33b14.. from the routing table.
INFO 15:41:10.311382037 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped dfda3a.. from the routing table.
INFO 15:41:10.328425274 [routing::states::node node.rs:2750] Node(d7ed9b..) Dropped d9889c.. from the routing table.
WARN 15:41:10.329054808 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 15:41:13.572698731 [routing::states::node node.rs:1268] Node(bec637..) Requesting a relocated name from the network. This can take a while.

Mines been running OK since this morning, but it seems to be rejecting a lot of connections

“Rejecting 12345… as a new candidate still handling previous one”

Not sure if that’s relevant but I don’t remember it doing that last night.

Yes I saw that msg a few times last night. THe reason my vault went down at 5am was I hit Ctrl-C instead of Shift-Ctrl-C to try to copy that msg from the terminal.
Felt stupid and then went to bed…

The network become very slow compared to yesterday. Seems that the network joining eat too many resources.
And this is very frustrating…

1 Like

Would say that was probably one of the most common things last night also

I’m excited others are able to join the vaults, but I haven’t been able to join yet. I checked my upload speed prior which was about 3mb/s so I am not completely surprised was not able to join. I will have a faster connection speed in less than a week so will re-try then.

On the flip side, was able to connect to the launcher effortlessly and started browsing various sites without any hiccups. I’m ecstatic for the progress currently being made and the upcoming updates. I think we will all be pleasantly surprised in the upcoming months. Thanks @maidsafe team for all of your hard work.

5 Likes

Same problem for me.