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.

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] haproxy + saltstack salt '*' test.ping minions(random) not connected #66978

Closed
2 tasks done
iostrovskii1976 opened this issue Oct 18, 2024 · 3 comments
Closed
2 tasks done
Labels
Bug broken, incorrect, or confusing behavior Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged

Comments

@iostrovskii1976
Copy link

Description
In the haproxy + saltstack configuration, some minions (randomly) do not respond the first time with salt ‘’ test.ping, they give out no connection, when repeated, all minions respond. It has been empirically established that when the minions are idle for more than 15 minutes, this behavior manifests itself. If you run salt ‘’ test.ping every 12-15 minutes, then everything works well.
Salt version 3006.9/3007

Setup
haproxy.cfg
global
maxconn 2000
stats socket /var/run/haproxy.stat mode 600 level admin
log 127.0.0.1:514 local2
chroot /var/empty
pidfile /var/run/haproxy.pid
user haproxy
group haproxy
daemon

frontend salt-master-pub
mode tcp
bind X.X.X.X:4505
timeout client 3m
default_backend salt-master-pub-backend

backend salt-master-pub-backend
mode tcp
timeout connect 5m
timeout server 10m
server r1 X.X.X.X:4505

frontend salt-master-req
mode tcp
bind X.X.X.X:4506
timeout client 3m
default_backend salt-master-req-backend

backend salt-master-req-backend
mode tcp
timeout connect 5m
timeout server 10m
server r1 X.X.X.X:4506

master
id: X.X.X.X
interface: X.X.X.X
ret_port: 4506
publish_port: 4505
pki_dir: /etc/salt/pki/master
cachedir: /var/cache/salt/master
file_roots:
base:
- /srv/salt
pillar_roots:
base:
- /srv/pillar
gather_job_timeout: 90
timeout: 60

miniom
id: XXXXXX
master: XXXXX
master_port: 4506
publish_port: 4505
recon_default: 1000
recon_max: 30000
recon_randomize: True

  • VM running on a OpenStack
  • classic packaging
@iostrovskii1976 iostrovskii1976 added Bug broken, incorrect, or confusing behavior needs-triage labels Oct 18, 2024
Copy link

welcome bot commented Oct 18, 2024

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.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

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.
If you have additional questions, email us at [email protected]. We’re glad you’ve joined our community and look forward to doing awesome things with you!

@dwoz
Copy link
Contributor

dwoz commented Oct 21, 2024

frontend salt-master-pub
mode tcp
bind X.X.X.X:4505
timeout client 3m
default_backend salt-master-pub-backend

backend salt-master-pub-backend
mode tcp
timeout connect 5m
timeout server 10m
server r1 X.X.X.X:4505

timeout server and timeout client for the publish port should be equal to the master's publish_session which defaults to 86400 seconds. This is a known issue in our documentation.

@dwoz dwoz added Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged and removed needs-triage labels Oct 21, 2024
@iostrovskii1976
Copy link
Author

Thank you, that was helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged
Projects
None yet
Development

No branches or pull requests

2 participants