[BUG]Communication problem between salt-master and minion under redhat8.6 of Azure #63945
Comments
|
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
|
Why are you using 3003.3 and not at least 3003.5? The latest version is 3005.1. |
garethgreenaway
added
Pending-Discussion
|
[root@test-saltclient minion]# salt-master --version [DEBUG ] Closing IPCMessageSubscriber instance |
|
What do the minions logs say? |
|
the minions logs content is empty |
|
Even when set to debug there's nothing at all, not even startup logging? |
|
I mean the log was not generated when the instruction was sent.
| |
15280396970
|
|
***@***.***
|
…---- Replied Message ----
| From | James ***@***.***> |
| Date | 03/28/2023 18:21 |
| To | ***@***.***> |
| Cc | ***@***.***>***@***.***> |
| Subject | Re: [saltstack/salt] [BUG]Communication problem between salt-master and minion under redhat8.6 of Azure (Issue #63945) |
Even when set to debug there's nothing at all, not even startup logging?
That probably means you're looking in the wrong place.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Before you execute this ‘’slat XXX test.ping‘’ The minion‘s log as follows： |
We deployed salt-master3003.3 and salt-minion3003.3 on the same virtual machine redhat8.6 system on Azure, and the communication is often interrupted automatically. I want to know the reason and how to fix this problem. The specific situation is as follows:
Both master and minion have debug logs enabled. We named the minion: serverip-redhattest.
The configuration of the master:
The configuration of the minion:
Try to test whether the communication is normal through "salt serverip-redhattest test.ping", everything is normal at the beginning, and this command can get normal return information:
However, after a period of time, if the test is carried out again, the normal communication will not be possible, and the returned information is as follows:
At this time, the minion does not have any logs, and the log of the master shows:
Executing “salt-call test.ping” can get the return normally:
Executing “salt-call test.ping” time, the minion's log is as follows：
And the master's log is as follows：
We also asked Microsoft Azure engineers for help, and basically ruled out system and network problems. How to solve this problem?
The text was updated successfully, but these errors were encountered: