Trying to restart the daemon as suggested doesn't work and restarting salt-minion gives a warning:router cli # systemctl daemon-reloadrouter cli #router cli # sudo systemctl restart salt-minionWarning: salt-minion.service changed on disk. Run 'systemctl daemon-reload' to reload units.
In further investigation, the connection seems broken to the conductor.
Ports 930, 4505 and 4506 are open to the conductor.
'systemctl status salt-minion' shows the service is loaded and active, however we see the following in the output. These are benign.:
salt-minion[12686]: [ERROR ] Got response for message_id None that we are not tracking
[12686]: [WARNING ] The function "module.run" is using its deprecated version and will expire in version "Phosphorus".
From the conductor, the 'show assets router <router name>' output we see the following:
show assets router <router name>
Tue 2024-09-03 17:04:29 UTC
✔ Retrieving assets...
===========================================
<asset ID>
Router: <router name>
Node: <node name>
Current Version: 6.1.5-14.lts.el7
Status: Running
First Connection Date: Not connected
The router is not connected, but running
From the conductor, run the following command to check what the conductor knows about the router:
# t128-salt-key -L
If the asset ID of the router shows up in the output, then try the following:
1) Stop salt on minion on router
# systemctl stop salt-minion
2) On the conductor:
# t128-salt-key -d <router asset ID from output>
3) On the router:
# rm -rf /etc/salt/pki/minion/minion*
4) On the router: Start salt minion on router
# systemctl start salt-minion
Then check the asset ID status from the conductor again and ensure we see the following in the output:
# show assets router <router name>
First Connection Date: 2024-09-06 18:14:38