-
Notifications
You must be signed in to change notification settings - Fork 34
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
Proxy times out when calling function from Salt Engine #58
Comments
From looking at the command history, I can see when executing the above command via the engine, the following appears on the router:
|
|
|
Note this also does not work if I call the module directly:
|
Hey @TheBirdsNest. Have you looked at the Scheduler: https://docs.saltstack.com/en/latest/topics/jobs/. Unless you need to dynamically change the targets, you can schedule the example you shared in #58 (comment), as follows: schedule:
run_pings:
function: net.ping
args:
- 8.8.8.8
seconds: 10 Alternatively, if you need to run towards various targets, you can indeed have an Engine (although you can equally have a scheduled custom Execution Module, or Runner on the Master). I'd recommend you to use test = __salt__['net.ping'](
params['opts']['target'],
timeout=2,
size=100,
count=5
) |
Hi,
I'm trying to use a Salt Engine running within a Proxy Minion process to periodically execute remote commands. Every 10 seconds the engine attempts to call net.ping on the router as follows:
When executing, it causes the connection to end and the proxy restarts.. Looking at the debug, I see in the write_channel the command is issued but a reply is not ready for 60 seconds at which point the keepalive function is called and assumes the proxy is down.
The text was updated successfully, but these errors were encountered: