question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

salt command does not respect timeout parameter

See original GitHub issue

salt -vt1 '*' cmd.run 'sleep 50' does not result in “Minion did not return”.

Expected:

Executing job with jid 20140304202635840445
-------------------------------------------
some-minion:
Minion did not return

Actual:

Executing job with jid 20140304202635840445
-------------------------------------------
Execution is still running on ...
Execution is still running on ...
Execution is still running on ...
Execution is still running on ... 
[Ctrl+c] after ~ 10s

I noticed this because one of my minions was down and the command waited for it…

Issue Analytics

  • State:closed
  • Created 10 years ago
  • Comments:13 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
basepicommented, Mar 5, 2014

This is a common misconception on what purpose the timeout serves.

The timeout is the time the master waits until it checks in with minions to see if they’re still running the job.

When that timeout expires, the master fires a find_job to all minions who have still not returned. A secondary timeout is then triggered which defines how long the master waits for the minions to respond to that find_job query. If they don’t respond within that secondary timeout, or return information that says the job is finished, then and only then will the master return “Minion did not return”.

Currently there is no “hard timeout” to force the master to stop listening after a certain amount of time.

Does that make sense?

0reactions
basepicommented, Jun 22, 2015

@alberts Could you give us more detail? There’s a lot of confusion around the timeout parameter. Read my first couple of comments above to make sure you’re on the same page.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Salt timeouts :: SUSE Manager Documentation
Salt features two timeout parameters called timeout and gather_job_timeout that are relevant during the execution of Salt commands and jobs—​it does not ......
Read more >
Troubleshooting the Salt Master - Salt Project Documentation
Salt Master Doesn't Return Anything While Running jobs · -t option to set a longer timeout when running commands (by default it is...
Read more >
Salt command takes about 5 Seconds to finish - Stack Overflow
One of my Saltstack Installations always has a 5 Second Delay on every salt command i run on it, i.e this Command takes...
Read more >
Mirantis Documentation: Troubleshoot DriveTrain - Docs
[32334] The Glusterd service does not restart automatically after its child processes ... parameter to the Salt API endpoint http://<cfg_node_ip>:6969 .
Read more >
Service Architecture Leveraging Tuxedo (SALT)
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all ... Configuring SALT Applications Using Command-Line Utilities .
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found