Skip to content
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.

Networking broken on clean VPS ISO install #154

Open
pirate opened this issue Aug 12, 2019 · 3 comments
Open

Networking broken on clean VPS ISO install #154

pirate opened this issue Aug 12, 2019 · 3 comments

Comments

@pirate
Copy link

pirate commented Aug 12, 2019

Tried both the latest pre-release and stable version with no luck. Mounted the ISO in a Vultr droplet, used the recommended os-config install with no special options, and it worked fine both times. (no wifi setup)

I usually manage to ssh into the fresh system, but before I can do anything this happens:

Screen Shot 2019-08-12 at 6 11 17 AM

The host loses internet connectivity entirely, both for outgoing and incoming traffic from any source. It also cant even ping the gateway, it seems to be totally disconnected, and yet ifconfig and connmanctl report the interface is still online and the routes look fine.

image
If I leave a ping running I get about 10 packets through every few minutes, but everyting else is "no route to host" or "destination unreachable".

I tried multiple cloud regions, and my other servers in those regions are working fine, so I don't think it's a Vultr networking issue. I'm left having to configure the server via VNC through the VPS admin panel, but I think I'm going to stop trying to set it up for now until I'm sure this can be fixed.

@dweomer
Copy link
Contributor

dweomer commented Sep 9, 2019

@pirate can you share your /var/log/k3s-service.log?

@dweomer
Copy link
Contributor

dweomer commented Sep 9, 2019

related to #141 ?

@pirate
Copy link
Author

pirate commented Sep 9, 2019

Indeed it looks very similar. Unfortunately I destroyed the VPS a while ago so I don't have the logs, but it's consistently reproducible, so running the v0.2.1 iso on any standard Vultr droplet will yield the same behavior.

I'm traveling and ramping up with a new client project this month so I likely wont have time to spin up a new droplet to get the logs, but #141 does indeed look similar. I'd definitely try and compare the logs with the ones generated from Vultr if ya'll get a chance to set up a droplet yourselves and are able to reproduce it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants