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

logstash_zmq: not working properly (un-handled exception) #8635

Closed
PierreR opened this issue Nov 19, 2013 · 4 comments
Closed

logstash_zmq: not working properly (un-handled exception) #8635

PierreR opened this issue Nov 19, 2013 · 4 comments
Assignees
Labels
Bug broken, incorrect, or confusing behavior severity-low 4th level, cosemtic problems, work around exists

Comments

@PierreR
Copy link
Contributor

PierreR commented Nov 19, 2013

When using the new logstash_zmq_handler (from 0.17)

On Salt side, running a simple salt command such as salt '*' test.ping will display the following error:

@arch-dev-vbox ~/projects/jules/halite:G:v0.17.2 > salt '*' test.ping
localdev:
    True
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib64/python2.7/logging/__init__.py", line 1651, in shutdown
    h.close()
  File "/media/sf_shared/jules/salt/salt/log/handlers/logstash_mod.py", line 323, in close
    self._context.destroy(1 * 1000)
AttributeError: 'NoneType' object has no attribute 'destroy'
Error in sys.exitfunc:
[ERROR   ] An un-handled exception was caught by salt's global exception handler:
AttributeError: 'NoneType' object has no attribute 'destroy'
Traceback (most recent call last):
  File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib64/python2.7/logging/__init__.py", line 1651, in shutdown
    h.close()
  File "/media/sf_shared/jules/salt/salt/log/handlers/logstash_mod.py", line 323, in close
    self._context.destroy(1 * 1000)
AttributeError: 'NoneType' object has no attribute 'destroy'

Version info:

salt --versions-report
           Salt: 0.17.2
         Python: 2.7.5 (default, Sep  6 2013, 09:55:21)
         Jinja2: 2.7.1
       M2Crypto: 0.21.1
 msgpack-python: 0.4.0
   msgpack-pure: Not Installed
       pycrypto: 2.6.1
         PyYAML: 3.10
          PyZMQ: 14.0.0
            ZMQ: 3.2.3
@PierreR
Copy link
Contributor Author

PierreR commented Nov 19, 2013

On the logstash side, I have got some messages from the Salt master but then this error message:

[2013-11-19T16:50:03.924]  WARN: org.elasticsearch.transport.netty: [Lodestone] exception caught on transport layer [[id: 0x647b83bb, /0:0:0:0:0:0:0:1:35695 => /0:0:0:0:0:0:0:1:9300]], closing connection
java.io.StreamCorruptedException: invalid internal transport message format
    at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:27)
    at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
    at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)

@basepi
Copy link
Contributor

basepi commented Nov 19, 2013

@s0undt3ch Pretty sure you were the author of this handler. Any ideas?

@ghost ghost assigned s0undt3ch Nov 20, 2013
@s0undt3ch
Copy link
Member

I'm debugging this...

@s0undt3ch
Copy link
Member

I was able to reproduce this issue.

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 severity-low 4th level, cosemtic problems, work around exists
Projects
None yet
Development

No branches or pull requests

3 participants