Skip to content
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

[2016.3.0] state.event doesn't stop after ctrl+c #33616

Closed
syphernl opened this issue May 30, 2016 · 4 comments
Closed

[2016.3.0] state.event doesn't stop after ctrl+c #33616

syphernl opened this issue May 30, 2016 · 4 comments
Labels
Bug broken, incorrect, or confusing behavior Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Core relates to code central or existential to Salt P2 Priority 2 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around stale
Milestone

Comments

@syphernl
Copy link
Contributor

Description of Issue/Question

If I stop the following:

salt-run state.event pretty=True

using CTRL+C, in the past it stopped immediately but now it starts spamming:

[DEBUG   ] Remaining event matches: -13
^Csalt/event/exit   {}
[DEBUG   ] Remaining event matches: -14
salt/event/exit {}
[DEBUG   ] Remaining event matches: -15
salt/event/exit {}
[DEBUG   ] Remaining event matches: -16
salt/event/exit {}
[DEBUG   ] Remaining event matches: -17
salt/event/exit {}
[DEBUG   ] Remaining event matches: -18
salt/event/exit {}
[DEBUG   ] Remaining event matches: -19
salt/event/exit {}
[DEBUG   ] Remaining event matches: -20
salt/event/exit {}

This goes on until I CTRL+C it again:

[DEBUG   ] Remaining event matches: -3174
salt/event/exit {}
[DEBUG   ] Remaining event matches: -3175
salt/event/exit {}
^C
Exiting gracefully on Ctrl-c

Versions Report

Salt Version:
           Salt: 2016.3.0

Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: 1.5
          gitdb: 0.5.4
      gitpython: 0.3.2 RC1
          ioflo: Not Installed
         Jinja2: 2.7.2
        libgit2: Not Installed
        libnacl: 1.4.3
       M2Crypto: Not Installed
           Mako: 0.9.1
   msgpack-pure: Not Installed
 msgpack-python: 0.3.0
   mysql-python: 1.2.3
      pycparser: Not Installed
       pycrypto: 2.6.1
         pygit2: Not Installed
         Python: 2.7.6 (default, Jun 22 2015, 17:58:13)
   python-gnupg: Not Installed
         PyYAML: 3.10
          PyZMQ: 14.0.1
           RAET: Not Installed
          smmap: 0.8.2
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.0.4

System Versions:
           dist: Ubuntu 14.04 trusty
        machine: x86_64
        release: 3.13.0-83-generic
         system: Linux
        version: Ubuntu 14.04 trusty
@Ch3LL
Copy link
Contributor

Ch3LL commented May 31, 2016

@syphernl I am seeing the same behavior. Here is the git bisect:

➜  salt git:(cf17699) git bisect bad                                              
cf176994f89a06b48f7cc256c8868cb2396b255f is the first bad commit
commit cf176994f89a06b48f7cc256c8868cb2396b255f
Author: Pedro Algarvio <pedro@algarvio.me>
Date:   Sun Aug 2 17:57:43 2015 +0100

    A more graceful salt-master exit

:040000 040000 e835332ccc091a41b76f62c6c78461cfd68a79fd ffa80a54c5e1c296e8048b55784c2cc6e28d18e9 M      salt   

@Ch3LL Ch3LL added Bug broken, incorrect, or confusing behavior P2 Priority 2 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around Core relates to code central or existential to Salt labels May 31, 2016
@Ch3LL Ch3LL added this to the Approved milestone May 31, 2016
@Ch3LL Ch3LL added the Confirmed Salt engineer has confirmed bug/feature - often including a MCVE label May 31, 2016
@cachedout
Copy link
Contributor

Well done, @Ch3LL

What say you, @s0undt3ch ? :]

@s0undt3ch
Copy link
Collaborator

I say, dam you signals! 😄

I'll try to tackle this tomorrow morning.

@stale
Copy link

stale bot commented May 12, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label May 12, 2018
@stale stale bot closed this as completed May 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Core relates to code central or existential to Salt P2 Priority 2 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around stale
Projects
None yet
Development

No branches or pull requests

4 participants