-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[BUG] Unable to connect pusher: Stream is closed #62334
Comments
I also get this error message when using |
I have the same errors here:
|
root@test13:~# salt-minion --versions-report Dependency Versions: System Versions: root@test13:~#
SaltReqTimeoutError: Message timed out |
I also get this error message. any solution for this?
|
Here's the actual traceback that is being caught:
|
|
Why is it necessary to connect to the minion/pusher when doing a local |
Description
For a certain configuration where a master is configured on minion in order to host SLS and other files but the long-running minion service is stopped, the following error is thrown when the
salt-call
command is run on the minion:It seems that this configuration, where
salt-call
is run manually or via scheduled (cron) job, should be valid. Everything seems to work just fine, but the errors cause user confusion and the perception that something critical has failed.Setup
Normal master/minion setup, but stop the
salt-minion
service.Steps to Reproduce the behavior
Run any command and view the error message as the minion code spins up.
Expected behavior
It would be nice to suppress this error message in certain scenarios where the connection to a master is desired without the configuration of long-running minion service.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Additional context
Versions report is from recent pre-3005 master clone, but is reproducible on previous versions.
The text was updated successfully, but these errors were encountered: