SQS output plugin cannot access queue


We are trying to connect to an SQS queue but are encountering an error I am providing the Stack Trace Below, this is running with a configuration file consisting of a basic standard input and then outputting to sqs, we are including a configuration file:

←[33mUsing milestone 1 output plugin 'sqs'. This plugin should work, but would b
enefit from use by folks like you. Please let us know if you find bugs or have s
uggestions on how to improve this plugin. For more information on plugin milest
ones, see http://logstash.net/docs/1.2.0/plugin-milestones {:level=>:warn}←[0m

←[31mUnable to access SQS queue 'logstash': uninitialized constant Digest::SHA25
6 {:level=>:error}←[0m

We are replicating this bug on Windows 2003 Server with Java Run Time Environment version 1.6.0_22


john Phan
October 16, 2013, 10:47 AM

Because I was emailed 3 times in one day about how to get around this. Please refer to below.

There is a flag called "--pluginpath" which you feed into the start up command.

For example /usr/bin/java -Xms256m -Xmx1g -jar /opt/logstash/logstash.jar agent -f /opt/logstash/logstash.conf --log /opt/logstash/logstash.log --pluginpath /opt --debug

Where in the folder opt. The logstash expects to find a folder structure similar to the kit repo. in my example, I have the following folder structure. /opt/logstash/outputs. Inside I put a file called sqswork.rb and checked out the output rb script from the git repo for 1.2.1. Inside the script I added the line mentioned above and changed the config name to sqswork.

This then magically works. I can already see someone has added in the git repo for the newer version of sqs input/output that someone has added a requirement for this module.

For more information on how to do this go to the following link.




Hans van Beek
October 22, 2013, 12:03 AM

HI John,

I tried, but ran into even more errors:

The error reported is:
nil is not a string
org/jruby/RubyModule.java:2546:in `const_get'
file:/etc/logstash/logstash.jar!/logstash/plugin.rb:140:in `lookup'
file:/etc/logstash/logstash.jar!/logstash/pipeline.rb:238:in `plugin'
(eval):7:in `initialize'
org/jruby/RubyKernel.java:1093:in `eval'
file:/etc/logstash/logstash.jar!/logstash/pipeline.rb:26:in `initialize'
file:/etc/logstash/logstash.jar!/logstash/agent.rb:105:in `execute'
logstash/runner.rb:194:in `run'
org/jruby/RubyProc.java:255:in `call'
file:/etc/logstash/logstash.jar!/stud/task.rb:12:in `initialize'

Any help resolving this issue is really appreciated!



john Phan
October 22, 2013, 1:13 PM

Hi Hans,

The issue is because in the checked out code. You did not change the config_name section to the value your calling in your logstash.conf file.



Former user
November 15, 2013, 9:05 PM

Added a pull request for the missing digest/sha2 here: https://github.com/logstash/logstash/pull/775

Just noticed John had the solution all this time (on Oct 1) after spending quite a bit of troubleshooting my colleague Zach

Jordan Sissel
December 11, 2013, 11:57 PM

Fixed by Toby in #775. Will show up in next release!



Former user


Marvin Vazquez

Fix versions

Affects versions