# Pending actions over 2 days

**URL:** <https://forums.suse.com/t/pending-actions-over-2-days/32312>\
**Category:** SUSE Multi Linux Manager\
**Created:** [April 19, 2018, 7:20pm UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312 "2018-04-19T19:20:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\
**Post date:** [April 19, 2018, 7:20pm UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312/1 "2018-04-19T19:20:04Z")

</div>

I am trying to bootstrap two servers with SUMA 3.1.4. I bootstrapped the systems by installing the requisite salt packages and then accepting the new entries that appeared in under the Salt menu. However, the following actions have been pending for two days now:

How can I find out why the actions are still pending?

---

<div class="post-metadata">

**Author:** ![kwk](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kwk/32/11997_2.png) [@kwk](https://forums.suse.com/u/kwk)\
**Post date:** [April 20, 2018, 9:28am UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312/2 "2018-04-20T09:28:11Z")

</div>

You did accept the minion key, didn’t you ?

---

<div class="post-metadata">

**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\
**Post date:** [April 20, 2018, 6:01pm UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312/3 "2018-04-20T18:01:13Z")

</div>

> [@kwk;52267](#):
>
> You did accept the minion key, didn’t you ?

Yes, under the salt menu, I accepted the key.

---

<div class="post-metadata">

**Author:** ![kwk](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kwk/32/11997_2.png) [@kwk](https://forums.suse.com/u/kwk)\
**Post date:** [April 21, 2018, 9:21am UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312/4 "2018-04-21T09:21:15Z")

</div>

Is the minion running and reachable ? Try ‘salt \<fqdn.of.minion\> test.ping’.  
If test.ping doesn’t work, can you ping it via network (‘ping \<fqdn.of.minion\>’) ?  
If the network ping succeeds, ssh to the client and restart salt-minion via systemctl.

---

<div class="post-metadata">

**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\
**Post date:** [April 24, 2018, 6:34pm UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312/5 "2018-04-24T18:34:18Z")

</div>

[QUOTE=kwk;52290]Is the minion running and reachable ? Try ‘salt \<fqdn.of.minion\> test.ping’.  
If test.ping doesn’t work, can you ping it via network (‘ping \<fqdn.of.minion\>’) ?  
If the network ping succeeds, ssh to the client and restart salt-minion via systemctl.[/QUOTE]

All of the above was done. No change. I upgraded the salt-minion client to the latest, still no change. I rebooted the SUMA server and that fixed the issue. Not really the way I would have liked to solve the problem though.

---

<div class="post-metadata">

**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\
**Post date:** [April 24, 2018, 6:35pm UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312/6 "2018-04-24T18:35:58Z")

</div>

However, regardless of the reason for the failure, how is it even possible to determine what the communication failure is? If SUMA cannot talk to the salt minion on the client, how do you find this out? Is it logged somewhere? Nothing eventful is in /var/log/salt/master.

---

<div class="post-metadata">

**Author:** ![kwk](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kwk/32/11997_2.png) [@kwk](https://forums.suse.com/u/kwk)\
**Post date:** [April 25, 2018, 9:31am UTC](https://forums.suse.com/t/pending-actions-over-2-days/32312/7 "2018-04-25T09:31:28Z")

</div>

> [@achinayoung\_waubonsee;52330](#):
>
> All of the above was done. No change. I upgraded the salt-minion client to the latest, still no change. I rebooted the SUMA server and that fixed the issue. Not really the way I would have liked to solve the problem though.

Good that your system is running again.

Next time, please open a support request and provide a ‘supportconfig’. Then we can hopefully determine the root cause.
