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

Unable to post on the queue #17

Open
gspavansai opened this issue Oct 20, 2016 · 3 comments
Open

Unable to post on the queue #17

gspavansai opened this issue Oct 20, 2016 · 3 comments

Comments

@gspavansai
Copy link

gspavansai commented Oct 20, 2016

Unable to access SQS queue '': The specified queue does not exist for this wsdl version. {:level=>:error}

I'm currently running logstash 2.4. I tried even by replacing aws-java-sdk-1.11.21.jar. I did not work. When we did our initial evaluation with 2.2 it was working and that is why we chose this approach.

sqs {
queue => "queuename"
region => "us-east-1"
access_key_id => "key"
secret_access_key => "secret"
}

I'm currently blocked with my implementation.

There is no connectivity issue. Using awscli I'm able to publish the queue.

console error says
Failed to flush outgoing items {:outgoing_count=>10, :exception=>"NoMethodError", :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-sqs-2.0.4/lib/logstash/outputs/sqs.rb:129:in flush'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:219:inbuffer_flush'", "org/jruby/RubyHash.java:1342:in each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:216:inbuffer_flush'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:159:in buffer_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-sqs-2.0.4/lib/logstash/outputs/sqs.rb:121:inreceive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/outputs/base.rb:83:in multi_receive'", "org/jruby/RubyArray.java:1613:ineach'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/outputs/base.rb:83:in multi_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/output_delegator.rb:130:inworker_multi_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/output_delegator.rb:114:in multi_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:293:inoutput_batch'", "org/jruby/RubyHash.java:1342:in each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:293:inoutput_batch'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:224:in worker_loop'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:193:instart_workers'"], :level=>:warn}

We have complete access to queue in AWS
"Action": [
"sqs:SendMessage",
"sqs:SendMessageBatch"
]

@kori0129
Copy link

Same problem here. Can someone look into this please?

@joshuaspence
Copy link
Contributor

I think that you need to add permissions for sqs:GetQueueUrl.

@jrgns
Copy link
Collaborator

jrgns commented Jan 10, 2017

@gspavansai Can you confirm if adding permissions for sqs:GetQueueUrl fixes the problem?

Also, @joshuaspence pretty much rewrote the plugin, and it's been released. Maybe give it a try?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants