-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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] Un-closed transports while starting up minion #65932
Comments
@dwoz Can clarify what constitutes a "master misbehaving" in this case? Do you just mean a master that is very busy and maybe not keeping up with workload? |
Does this have to do with #61565 ? |
@doesitblend The master in question here was not overloaded but something was wrong with it's network causing minions to continually re-connect. At least, that was my understanding. |
This went into |
Morning all, I'm seeing this exact same error, but with salt 3006.9. Sep 11 11:33:28 server-syndic salt-syndic[2504609]: [CRITICAL] Unable to call _fire_master on any masters! Salt MoM & Syndics both running 3006.9 |
I can't seem to edit my posts, it's not quite the same stack trace, but the error does appear to be very similar. |
facing exactly the same issue on salt 3006.9 as well. Targetting minions running 3005 is working fine while minions in 3006.9 always return this issue. @wibbit did you fix your issue ? |
Unfortunately not. |
Description
If a master is mis-behaving it may cause and exception which can leave the minion with un-closed transports.
Versions Report
This was observed on
3006.5
The text was updated successfully, but these errors were encountered: