"Minion did not return" but syslog shows salt-minion activity

[ke...@understoryweather.com]

I issued "state.sls" from my master to a single minion. After a few minutes it returned

Minion did not return. [No response]

I can see plenty of what looks like healthy behavior in the syslog.

Without a job ID or any other information how would I know when this task is done and what its results are?

This is running 2016.11.4.

Thanks. 

[Viet Hung Nguyen]

Without a job ID, it is quite impossible to know when it is done and what its result are.

But why without a job ID? 

You can “reverse engineering” by looking at log of minion as no response return back to master.

If you didn’t set log in minion to info/debug, seems you will have nothing.

I suggest to look at issues on GitHub to see more on the problem https://github.com/saltstack/salt/search?q=minion+did+not+return&type=Issues&utf8=%E2%9C%93

—

Viet Hung Nguyen

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/salt-users/83240dfd-458e-4f65-a7e3-59ae99ccc397%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robert Callicotte]

In cases like these I suggest that you run a salt-call from the minion with the "-l debug" flag.  This depends upon your setup of course (salt-ssh or not).  All rendering and execution info can easily be seen with this method.

-Robby