New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues creating Infinit volumes #46
Comments
Hi @aligg73.
This is just a warning. We have some unresolved bugs triggered by nodes using the UTP protocol so it has been deprecated. You can ignore that message.
It's also just a warning. Our default port for Prometheus (monitoring system) is 8080 with no fallback. You can also ignore this warning. However, if you cannot mount your two volumes, there is an issue elsewhere... Can you access the first mountpoint? If not, can you copy/paste the last ~5 lines of logs here please? |
Will do, how do I get these last few lines please? |
I could export here the result of infinit doctor all, but it includes messages for the root user, which i am not using. |
Just copy/paste from your terminal. By default, we send logs to the standard error channel.
You can use |
I got a different message the first time around, but now after I deleted the volume, created the volume again and then mount it, I get: Here's the order of command I have just issued: The first 2 commands worked without issue. |
Can you try elsewhere pls? Like Edit: You probably have a dead mountpoint because the previous instance of infinit wasn't shutdown correctly. You can unmount by using |
edit: [Dimrok] Markdown. |
In this case, you misspelled |
Ehhhh yes, not very smart, thanks for pointing that out. Thanks a lot! |
I might have cheered too early, after continuing with your Debian tutorial (https://infinit.sh/get-started) I now get this on machine B: This happens after I issue: |
Hi. This means the second node didn't find the first running instance of Infinit (nor listed by Did you specify You can check https://beyond.infinit.sh/networks/turtle2017/dishcupboard (key |
Yes, I did specify --publish upon mounting the first volumes on node A. |
Are your nodes on two different machines? Do you know if they can see each others (through a public ip or a local subnetwork ip)? You can try by pinging IPs listed on https://beyond.infinit.sh/networks/turtle2017/dishcupboard. |
The nodes are on 2 different machines indeed and their respective IP addresses can be pinged either way. Thanks |
Please let me know if I should open port 34649 or the problem is caused by something else, thanks. |
Hi. Yes you should. You can even force its value by using |
Thanks. When I do infinit volume list I get to see both volumes. But when I try to: I get this when running infinit doctor all --as turtle2017:
edit: [Dimrok] Markdown. |
Hmm... you should at least have the basic messages (like you said Can you run your command with logs activated |
Not sure this is what you meant: ..so only a background process, nothing else. |
It should write more logs in your terminal, weird. Can you run |
yes a few too many were running, i killed all those processes. |
Cool. At least, you have some output. Now, you need to unmout this folder by running |
Thanks, that got me a step closer. Unmounting the folder now lead to this output:
edit: [Dimrok] Markdown. |
Probably because the other peer was killed or is not accessible (anymore). Can you kill every single instance of Infinit running on your nodes and restart them with |
Ok I killed every instance node B and node A, then I started it from node A, all good. Then from node B, I got this output:
I wanna save you from having to apply Markdown all the time to my output, how do I do this? |
Use the triple backquotes formatting:
I'm pretty upset about this line... The Can you try to find the IP of both nodes and on each run: This should show you something like
Can you follow the instruction and run the line on the other machine (with the right IP address filled). And do also the procedure on the other machine too pls? |
from Node B, using Node A IP:
from Node A, using Node B IP:
Could it be because all these ports sound new to me, and they are not allowed on the firewall? At least I don't see them opened when I do: edit: [Dimrok] Markdown (Do not forget to jump a line after opening and before closing triple backquotes). |
Arf... segfaults. I'll check why. By the way you can force the port and the protocol. Try with: |
Yes that works beautifully both ways, I get feedback like this from both ends, picking a port that is open on both sides:
So now that that is cleared up, does it mean I have to run this command again: but append it with --port and --protocol, like you suggested in the doctor networking example. |
Hi, Hope you can quickly review my last question and give me the heads up (or not). |
Oh I missed this one. So you should:
Can you try that pls. |
I managed to run the first one from Node A, although with some warnings:
Then when I run the second one on node B with this command (masked the IP here, but changed it to IP of Node A:
I can confirm port 4001 is open on both Nodes. |
Hi,
I followed the steps as listed here, for Debian, as I am on Ubuntu 16.04 LTS.
All the steps complete normally, until I mount 2 volumes. For each individual command, Infinit gives me this notice:
[infinit.model.doughnut.Doughnut] [main] Not using UTP although network configuration selects 'all' protocols. UTP has been temporarily deprecated. Force with INFINIT_UTP=1.
[ infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7f7ee487b410): creation failed, metrics will not be exposed: null context when constructing CivetServer. Possible problem binding to port.
Additionally I get this notice upon mounting the 2nd volume:
[ infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7f7ee487b410): creation failed, metrics will not be exposed: null context when constructing CivetServer. Possible problem binding to port.
What should I do to prevent or fix this?
Thank you,
Alex
The text was updated successfully, but these errors were encountered: