-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
salt-sproxy works with 3004 #260
Comments
Digged a bit further . It works with 3004 if I start the master and than use salt-sproxy to execute command against my sproxy minions. For me it looks like that something it wrong with the ipc, maybe they changed the order of the master startup procedure ? The connect method File "/home/sharky/venv/salt/lib/python3.9/site-packages/salt/utils/event.py", line 423, in connect_pull is not successful , because the file is not there... [DEBUG ] MasterEvent PULL socket URI: /home/sharky/salt/var/run/salt/master/master_event_pull.ipc maybe.... |
The error indicates that connecting to the ipc socket /home/sharky/salt/var/run/salt/master/master_event_pull.ipc is not working. That is true . There is no socket under var/run/master/master.... . From my understanding this has nothing todo with salt-sproxy . salt-sproxy only calls or loads the master , but I can't find it how this is done? Just the import of import salt.loader ? |
I just found this commit on the salt project. Good news , if I just ignore the errors connecting to devices is not a problem. I think this error always occurred , but was never visible. |
Hey @network-shark - thanks for digging into this. I'll reopen this issue, as I'll try to work around that error.. it may not bother you, but it will surely bother me. 🙃 |
Describe the bug
Can't run salt-sproxy
Steps To Reproduce
salt-sproxy -c . -L 'csr1000v' net.cli 'show version'
Expected behavior
Command should return show version
Error
Versions Report
Print the output from
salt-sproxy -V
inside the backticks below:Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: