We are reaching out to the community in the hope that someone may have encountered a similar issue or could provide guidance on how to resolve it. We greatly appreciate any insights, suggestions, or support you can offer to help us address this probl

139 views
Skip to first unread message

WS1 assist

unread,
Sep 20, 2023, 2:36:31 PM9/20/23
to Salt-users

Dear Salt-Users,

I am writing to seek assistance with an issue we encountered after updating our Salt Master and Minion from version 3001.1 to 3005.1 and enabling failover master functionality.

After the update and configuration change, we observed that the Minions became disconnected from the Master, and upon investigating the Minion logs, we discovered the following exception:

 [tornado.general  :450 ][WARNING ][103715] Got events for closed stream None
[salt.utils.parsers:1060][WARNING ][103715] Minion received a SIGTERM. Exiting.
[tornado.general  :450 ][WARNING ][103981] Got events for closed stream None


We are reaching out to the community in the hope that someone may have encountered a similar issue or could provide guidance on how to resolve it. We greatly appreciate any insights, suggestions, or support you can offer to help us address this problem.

Our goal is to ensure a smooth transition to the updated SaltStack version while maintaining the stability of our infrastructure. Your expertise and assistance would be invaluable in achieving this.

Thank you in advance for your time and support. We look forward to your response and working together to resolve this issue.

Thanks,
Venkat

Rodrigo Moutinho (rcmoutinho)

unread,
Sep 25, 2023, 12:26:57 PM9/25/23
to Salt-users
Hello!

Here are some insights about your issue that you can try:
1 - I would understand if you use the new onedir approach or the "legacy" one. There are some interesting differences there. Version 3006 only allows onedir but 3005 still supports both. You can find more about it here: https://docs.saltproject.io/salt/install-guide/en/latest/topics/upgrade-to-onedir.html
2 - Review how you did the upgrade. Salt has a bootstrap project that is useful for setting up any minion with your desired version. Docs here: https://github.com/saltstack/salt-bootstrap
3 - Restart master and minions services after the upgrade if you didn't. If there is any failure, it will be visible under the logs. You can check more about logging here: https://docs.saltproject.io/en/latest/ref/configuration/logging/index.html

At first look, these warnings are mostly related to a service that was stopped. So you can start it again or restart checking the logs to look for any inconsistency.

I would also take a look at all major release notes, looking for removed features in case you are using any of them. In your case, starting from 3002: https://docs.saltproject.io/en/latest/topics/releases/3002.html

Good luck with the investigations.
Cheers!
Reply all
Reply to author
Forward
0 new messages