https://netmaker.org logo
Powered by
hello, is it possible that netclient has removed h...
# client
h
hello, is it possible that netclient has removed hostname from my /etc/hosts file ? it was like this some-ip fqdn hostname example: 123.123.123.10 hostname.domain.tld hostname now it like this: some-ip fqdn example: 123.123.123.10 hostname.domain.tld below this i get these lines: ################################################################## # Content under this line is handled by hostctl. DO NOT EDIT. ##################################################################
Seems like this is my problem. When hostname is removed from top of my /etc/hosts file after the FQDN, my proxmox server stops working. Proxmox doesn't like a missing hostname after the FQDN after reboot. and if I put hostname manually into the hosts file, after a short time it gone again. Do you have any ideas how to fix this?
b
netmaker doesn't change the part above the lines #content under this line is handled by hostctl DO NOT EDIT. except there was a bug (fixed in 0.14.6) that could result in a corrupted file if multiple copies of netclient were running at the same time.
q
i ran into something similar, no idea why proxmox is so temperamental
it didn't stop it from running, the web interface still accessible
but i ran into problems opening a xterm.js shell
quick edit to the hosts file fixed it
j
We have a switch for turning off dns setting on any node: edit the node in the UI and turn off the switch "Is DNS On"
q
ran into this issue again
proxmox autogenerates a hostfile
strangely, recreating it does not fix the issue
once hostctl modifies it proxmox shells on the web interface display "Connection failed (Error 500: failed to get address info for: hostname: Name or service not known)" errors
i don't get why this happens because netmaker just amends the hostfile and shouldn't make changes to what was already there
currently unable to open the web shells or ssh into my remote server
i would advise caution for proxmox users
the proxmox cluster service failed to restart and my entire host just went down, not responding
proxmox scripts make modifying hostname and hosts file dangerous
j
so it is generating the hosts file even when you turn dns off?
q
I turned it off but was too late
Imo it doesn't seem to be netclients fault
But modifying files with proxmox can be dangerous
This is especially true if you're using it in cluster configurations
Normal Linux distributions wouldn't be affected by this but proxmox configuration has a lot of background scripts or something
Going to drive to my server that went down and bring it home to fix and investigate
As far as I can tell, netclient used hostctl to add it's entries, didn't change the pre-existing ones proxmox had. I know this because I checked before hand since my previous run in
Yet it still caused problems. From what I can tell proxmox is just really sensitive lol
Not a big deal for me as I needed to go get the server before moving it to another town remotely
bunch of anecdotes about this for some reason
what's wild is once the problem occurred last night, not only could i not open an xterm.js shell, i also couldn't reboot from web panel
ssh wasn't configured either otherwise i probably could
restarted a few servers from web panel and one threw errors, making the web panel inaccessible
anyway too much rambling.. just be careful with proxmox people. very fickle it is
s
Yea I tried it on my Proxmox server yesterday and I can only connect to it through tailscale. Even locally only goes through tailscale. Have not had time to look at it to see what it did but I'll never do it again. haha
q
i have two proxmox machines connected by netmaker
they both had the issue but was easily resolved with a simple edit
dunno why the third one didn't behave the same. been too busy yet to go get it and bring it home for inspection
j
was the issue again with /etc/hosts?
q
yep
it's still a mystery to me because this third time it happened i KNOW netmaker didn't erase anything proxmox had there already
it just amended the dns entries for nodes
you'd think that would not affect anything
but there's anecdotes and people asking for help on proxmox forums and subreddit asking why proxmox failed to fully boot after making changes to hosts file
i do know that if running a proxmox cluster instead of standalone, this is even more dangerous to make edits to
s
Yea I was able to solve it by fixing the hosts file as well. Originally had it in it's own container but was having errors on that node for connectivity. Turns out my CGNAT and double NAT issues are too crazy for netmaker to work for my home network. I've tried wireguard by itself and netmaker but neither work well. Tailscale or headscale works great though. 🤷‍♂️
Yea if I still had my cluster running, I wouldn't of even attempted to install anything directly on the host. They are amazing when they work as long as you don't mess with it.
q
yeah i use proxmox as an alternative to esxi or hyper-v, etc
love it personally. very very stable in my experience
but they do advise being careful as a lot of it's behavior is scripted behind the web interface
j
you should be able to start a netclient without it setting dns using the --dns=off flag, though I haven't tested in a while to make sure it still works
we should maybe note that for users using proxmox somewhere
s
Yea I would note that in the documentation about installing it directly on the host. Proxmox is popular enough with the self hosting community that it wouldn't be the last time this issue came up.
You guys have amazing documentation compared to many products out there. When I first started using traefik, it was a nightmare getting it up from their documentation alone. Especially when they changed so much from v1 to v2.
q
yeah i like the docs
6 Views
PreviousNext
Powered by