[BUG] Unable to connect pusher: Stream is closed

See original GitHub issue

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:

[ERROR   ] Unable to connect pusher: Stream is closed

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.

# salt-call cp.list_master
[ERROR   ] Unable to connect pusher: Stream is closed
local:
    - test.sls

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.)

Salt Version:
          Salt: 3005+0na.b18281e
 
Dependency Versions:
          cffi: Not Installed
      cherrypy: Not Installed
      dateutil: Not Installed
     docker-py: Not Installed
         gitdb: Not Installed
     gitpython: Not Installed
        Jinja2: 3.1.2
       libgit2: Not Installed
      M2Crypto: Not Installed
          Mako: Not Installed
       msgpack: 1.0.3
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     pycparser: Not Installed
      pycrypto: 2.6.1
  pycryptodome: 3.14.1
        pygit2: Not Installed
        Python: 3.7.3 (default, Jan 22 2021, 20:04:44)
  python-gnupg: Not Installed
        PyYAML: 6.0
         PyZMQ: 23.0.0
         smmap: Not Installed
       timelib: Not Installed
       Tornado: 4.5.3
           ZMQ: 4.3.4
 
System Versions:
          dist: debian 10 buster
        locale: UTF-8
       machine: x86_64
       release: 4.19.0-21-amd64
        system: Linux
       version: Debian GNU/Linux 10 buster

Additional context Versions report is from recent pre-3005 master clone, but is reproducible on previous versions.

Issue Analytics

State:
Created a year ago
Reactions:8
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

bdrx312commented, Sep 7, 2022

I also get this error message when using salt-call --local with saltutil sync methods like salt-call --local saltutil.sync_all

1reaction

leon0306commented, Oct 20, 2022

I also get this error message. any solution for this?

salt-call --local status.ping_master localhost
[ERROR   ] Unable to connect pusher: Stream is closed
local:
    True

Top Results From Across the Web

Troubleshooting the Salt Minion - Salt Project Documentation

No ports need to be opened on the minion, as it makes outbound connections to the master. If you've put both your Salt...

Pusher not able to establish connection - Stack Overflow

The error comes from tcpsocket.new (Ruby https://ruby-doc.org/stdlib-2.5.1/libdoc/socket/rdoc/TCPSocket.html) in websocket line 17: ...

Pusher Channels Protocol

Old WebSocket drafts: Some errors result in the WebSocket connection being closed by Pusher Channels. If the WebSocket connection does not support close...

SaltStack: salt/utils/event.py - Fossies

1 """ 2 Manage events 3 4 Events are all fired off via a zeromq 'pub' socket ... 430 log.error( 431 "Unable to...

Release 2.3 - Security Onion Documentation

0 results, or a query failure error, but source.geo.ip.keyword* may work as ... during setup - [ERROR ] Unable to connect pusher: Stream...