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
[BUG] Unable to connect minion to master - strange timeout #62646
Comments
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
We have about 20 minions in a test setup. And while saltstack was running pretty stable at the beginning, we now see more and more minions being unreachable from the salt master and report the same error mentioned by @GeraldHOST1 when running Master is running saltstack v3005 and minions are running v3004.2 and v3005. When (re-)starting the salt-master, we see these errors related to zeromq:
While I was checking for a last time whether my master and minion were up to date, I spotted the update to saltstack v3005.1. Quickly gave it a try but the issue persists. |
We're seeing the exact same problem on 3005.1, even with a configuration file as minimal as the following (and starting the salt master with an empty
|
I seeing what I believe is the same issue, just setup a dual masters and a few clients in a test lab. salt --versionsalt 3005.1 Happen to be on Debian 11.6 |
Seeing very similary issue with salt 3005.1 on rhel9.1 |
Same happen on salt 3005.1 Ubuntu 18.x Workaround : is downgrade to 3004.2 |
Same problem with 3005.1 classic on Debian 11 |
Seems like I stumbled upon same issue with Salt 3007.0
Minion was suceffsull authenticated with master, key was accepted. When minion runs it contacts master and I see this in master log:
When I set log_level to debug I see some communication going on:
And I see that pillars are processed on master:
But then I see also lots of these repeatedly:
And then nothing else logged on master and minion timeouts. |
Found a cause and solution: We use OpenVPN to connect servers with minions to server with master. It worked just fine with our old server but stopped working after recent upgrade of master server to latest Debian. It seems that for some reason OpenVPN connection over UDP caused salt conenction to lose packets. After switching to TCP in OpenVPN it works |
Interesting... understandable UDP vs TCP... but then the question is, should even UDP have reasonable chance of success? All depends on where the issue originates from I guess. |
I'm having the same issue. Can it be related to MTU settings? |
@nagylzs That was one possible cause we investigated and tested and in our case it was not the cause. |
Same issue with salt 3005.5 / debian 10.13. I see that when I start jobs from master (ie. I'm getting similar error logs:
Version report:
|
Hi everyone,
I've been dealing with a strange problem for a few weeks now, communication problem between a minion and the master. Communication timeout, while with a similar server it goes through ! Let me explain:
What I've done so far:
From Minion2 :
From minion2 and
/var/log/salt/minion
file :Again from minion2
From master log, nothing.
I don't know where to turn to correct this :(
If anyone has an idea, I'm interested!
Thanks !
The text was updated successfully, but these errors were encountered: