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

panic: runtime error: integer divide by zero #471

Closed
xaqq opened this issue Jun 6, 2015 · 3 comments
Closed

panic: runtime error: integer divide by zero #471

xaqq opened this issue Jun 6, 2015 · 3 comments

Comments

@xaqq
Copy link

xaqq commented Jun 6, 2015

Hello,

I'm setting up a logstash-forwarder instance. However the software badly crashes by dividing by zero.
This is on Debian Jessie.

For reference, is here the configuration file:

{
  # The network section covers network configuration :)                                        
  "network": {
    # A list of downstream servers listening for our messages.                                 
    # logstash-forwarder will pick one at random and only switch if                            
    # the selected one appears to be dead or unresponsive                                      
    #"servers": [ "localhost:5043" ],                                                          

    # The path to your client ssl certificate (optional)                                       
    #"ssl certificate": "./logstash-forwarder.crt",                                            
    # The path to your client ssl key (optional)                                               
    #"ssl key": "./logstash-forwarder.key",                                                    

    # The path to your trusted ssl CA file. This is used                                       
    # to authenticate your downstream server.                                                  
    "ssl ca": "/etc/lumberjack.crt"

    # Network timeout in seconds. This is most important for                                   
    # logstash-forwarder determining whether to stop waiting for an                            
    # acknowledgement from the downstream server. If an timeout is reached,                    
    # logstash-forwarder will assume the connection or server is bad and                       
    # will connect to a server chosen at random from the servers list.                         
    #"timeout": 15                                                                             
  },
 # The list of files configurations                                                            
  "files": [
    # An array of hashes. Each hash tells what paths to watch and                              
    # what fields to annotate on events from those paths.                                      
    {
      "paths": [
        # single paths are fine                                                                
        "/var/log/messages",
        # globs are fine too, they will be periodically evaluated                              
        # to see if any new files match the wildcard.                                          
        "/var/log/*.log"
      ],
      # A dictionary of fields to annotate on each event.                                      
      "fields": { "type": "syslog" }
    }
  ]
}
@driskell
Copy link
Contributor

driskell commented Jun 6, 2015

Try uncommenting servers. Could be as it seeing empty server list.

@xaqq
Copy link
Author

xaqq commented Jun 6, 2015

Yes this is indeed the case. But a crash by divide by zero is not nice, an error message would preferred.

@ruflin
Copy link
Member

ruflin commented Nov 16, 2016

Closing as this issue should be solved in filebeat.

@ruflin ruflin closed this as completed Nov 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants