-
Notifications
You must be signed in to change notification settings - Fork 94
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
Something about this box causes Salt to be extremely slow #9
Comments
Thanks for the report. Unfortunately, I'm not familiar with Salt. Is it perhaps a missing dependency that takes time to download? Another route that might be worth testing would the 6.4 box and seeing if you have the same problem. Does Salt have high memory requirements? Perhaps GH-8 might be related in that case. |
As it takes 60 seconds every run (not just the first) it's probably not some dependency like a first-run would have. Plus, as noted on another centos box it runs super fast, every on the first run. It could be memory, but I give the VM 2GB of ram at boot, so probably not. I mean, it shouldn't be swapping by that point anyway. ...and I just tried the older box image your linked to, and we have a winner: it's not having the same problem. With |
It's worth noting that, from the 6.4 image, I could do a |
Seems like your problem might be related to CentOS 6.5? Just to be sure you could try the older releases of 6.5 on the release page or perhaps vagrantbox.es has some 6.5 boxes too (might have to look in the pull requests as the repo isn't updated often). |
Missed this. That is interesting... Does it still go fast if you |
So I've tried a few of the older 6.5 boxes:
I...can't replicate this now. Damn hiesenbugs. Thanks for giving me some pointers anyway. If I can produce a reliable replication, I'll send over some better instructions. |
D'oh! Good luck with it! |
I was experiencing the same issues with your 6.5 box. I switched to the puppetlabs 6.5 box and the issues went away. During the salt runs it would sit in wait for a long time before actually executing any of the python code from what I saw, but I'm not certain what is different between the box builds. |
What's the date on the centos65 box are you using? Could you try some of the other dated releases off of the releases page and see if that helps? |
That would make sense, I look forward to the latest draft... |
Might also be related to IPv6. hashicorp/vagrant/issues/1172 |
From resolv.conf(5): single-request-reopen (since glibc 2.9) The resolver uses the same socket for the A and AAAA requests. Some hardware mistakenly sends back only one reply. When that happens the client system will sit and wait for the second reply. Turning this option on changes this behavior so that if two requests from the same port are not handled correctly it will close the socket and open a new one before sending the second request. GH-9
From resolv.conf(5): single-request-reopen (since glibc 2.9) The resolver uses the same socket for the A and AAAA requests. Some hardware mistakenly sends back only one reply. When that happens the client system will sit and wait for the second reply. Turning this option on changes this behavior so that if two requests from the same port are not handled correctly it will close the socket and open a new one before sending the second request. 2creativesGH-9
I was attempting to use Salt to provision a machine based on this box, but as you can see in this gist a basic salt state with nothing in it takes over 60 seconds to run.
If I spin up the same salt provision, but with this box:
the salt highstate takes about 2 seconds
The text was updated successfully, but these errors were encountered: