Skip to content
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.

Sign up for GitHub

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

Jump to bottom

can not start on windows #100

Closed
lostfile opened this issue Mar 31, 2019 · 9 comments
Closed

can not start on windows #100

lostfile opened this issue Mar 31, 2019 · 9 comments

Comments

@lostfile
Copy link

err
@lostfile
Copy link
Author

pop

@mwarning
Copy link
Owner

Looks like Windows needs some extra handling to get ipv6 local peer discovery going. IPv4 might work.

@mwarning
Copy link
Owner

Is kadnode already running? Try to execute kadnode-ctl and see if you can reach the instance.

@mwarning
Copy link
Owner

Did kadnode exit on its own kadnode -6? That should not happen.

@lostfile
Copy link
Author

kadnode-ctl was missing when i compiled it

@lostfile
Copy link
Author

$ kadnode-ctl status
Failed to connect to '/tmp/kadnode/kadnode_cmd.sock': No such file or directory

@mwarning
Copy link
Owner

ah, on windows kadnode-ctl cannot work (because unix sockets are not supported there)

@mwarning
Copy link
Owner

I will look into it tomorrow.

@mwarning
Copy link
Owner

mwarning commented Nov 3, 2024

Sorry it tool so long (just a few years..), but right now Windows is not tested / supported.

@mwarning mwarning closed this as completed Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mwarning @lostfile