SQS input throws an exception: uninitialized constant Digest::SHA256

Description

Starting logstash throws an uninitialized constant Digest::SHA256 exception when you have sqs defined as an input.

Config:
input {
sqs {
access_key_id => "zzzzz"
secret_access_key => "xxxxx"
region => "us-west-2"
queue => "ops_logstash_dev"
debug => true
}
}

output {
elasticsearch {
host => "127.0.0.1"
cluster => "ops_logstash_dev"
}
}

Output:
Using milestone 1 input plugin 'sqs'. This plugin should work, but would benefit from use by folks like you. Please let us know if you find bugs or have suggestions on how to improve this plugin. For more information on plugin milestones, see http://logstash.net/docs/1.2.2/plugin-milestones {:level=>:warn}
Using milestone 1 codec plugin 'json'. This plugin should work, but would benefit from use by folks like you. Please let us know if you find bugs or have suggestions on how to improve this plugin. For more information on plugin milestones, see http://logstash.net/docs/1.2.2/plugin-milestones {:level=>:warn}
Registering SQS input {:queue=>"ops_logstash_dev", :level=>:info}
Unable to access SQS queue. {:error=>"uninitialized constant Digest::SHA256", :queue=>"ops_logstash_dev", :level=>:error}
---------------------------------------------------------

An unexpected error occurred. This is probably a bug.

You can find help with this problem in a few places:

 

  • chat: #logstash IRC channel on freenode irc.

IRC via the web: http://goo.gl/TI4Ro

  • email: logstash-users@googlegroups.com

 

---------------------------------------------------------
The error reported is:
uncaught throw uninitialized constant Digest::SHA256 in thread 0x7e0

Gliffy Diagrams

Activity

Show:

Philippe Weber March 10, 2015 at 1:16 PM

Mentioned PR was merged in logstash codebase

Former user November 15, 2013 at 9:02 PM

We've got a pull request for this here: https://github.com/logstash/logstash/pull/775

I hope it's the right fix and it gets applied soon.

Zeph Harben October 30, 2013 at 8:19 PM

I reported a very similar bug for inputs/s3.rb here :
https://logstash.jira.com/browse/LOGSTASH-1321

A fix for s3 was applied in 1.2.2 - here's the diff : https://github.com/logstash/logstash/pull/636/files

Lance O'Connor October 24, 2013 at 9:26 PM

When running from source tree, all is happy:
require("aws/rails")
require("aws-sdk")
require("bigdecimal")
Unconditional log call {:location=>"/data/projects/logstash-master/lib/logstash/inputs/sqs.rb:92:in `register'", :level=>:warn}
require("base64")
require("digest/sha2.so")
require("isorelax.jar")

When running from jar:
require("aws-sdk")
require("bigdecimal")
Connecting to AWS SQS queue {:queue=>"ops_logstash_dev", :level=>:debug, :file=>"logstash/runner.rb", :line=>"35"}
require("base64")
Unable to access SQS queue. {:error=>"uninitialized constant Digest::SHA256", :queue=>"ops_logstash_dev", :level=>:error, :file=>"logstash/runner.rb", :line=>"35"}
---------------------------------------------------------

An unexpected error occurred. This is probably a bug.

You can find help with this problem in a few places:

 

  • chat: #logstash IRC channel on freenode irc.

IRC via the web: http://goo.gl/TI4Ro

  • email: logstash-users@googlegroups.com

 

---------------------------------------------------------
The error reported is:
uncaught throw uninitialized constant Digest::SHA256 in thread 0x7e0
org/jruby/RubyKernel.java:1323:in `throw'
file:/data/projects/logstash/logstash-lgoc-flatjar.jar!/logstash/inputs/sqs.rb:97:in `register'
file:/data/projects/logstash/logstash-lgoc-flatjar.jar!/logstash/pipeline.rb:126:in `start_inputs'
org/jruby/RubyArray.java:1613:in `each'
file:/data/projects/logstash/logstash-lgoc-flatjar.jar!/logstash/pipeline.rb:125:in `start_inputs'
file:/data/projects/logstash/logstash-lgoc-flatjar.jar!/logstash/pipeline.rb:63:in `run'
file:/data/projects/logstash/logstash-lgoc-flatjar.jar!/logstash/agent.rb:132:in `execute'
logstash/runner.rb:194:in `run'
org/jruby/RubyProc.java:271:in `call'
file:/data/projects/logstash/logstash-lgoc-flatjar.jar!/stud/task.rb:12:in `initialize'
[ec2-user@ip-172-31-41-215 logstash]$ vi ../logstash-master/lib/logstash/runner.rb

Ian Neubert October 24, 2013 at 5:50 PM

Might be a dup of LOGSTASH-1294?

Fixed

Details

Assignee

Reporter

Fix versions

Affects versions

Created October 23, 2013 at 7:22 PM
Updated March 10, 2015 at 1:16 PM
Resolved March 10, 2015 at 1:16 PM