SQS output failure


I have a new collector array for rsyslog traffic top be placed directly into an SQS queue.

I know from TCPdump and logstash STDout that the message is being recieved correctly at logstash. However the message never gets put into SQS.

After doing a load of debugging. the debug logs show this.


john Phan
January 14, 2014, 10:03 AM

I apologize if I wasn't clear. However I have performed this test on both 1.3.2 and 1.2.2

I have also added use_ssl => False to see if it resolves the issue. IT still comes up with an error. I am going to rebuild the server using the following cookbook.


It's the same cookbook I used to produce the error.

john Phan
January 14, 2014, 11:13 AM

Gaaa more confusing messages.

Why is 1.2.2 now showing up in my -vv logout put. As I recall unlike a tomcat container the war is not exploded into a work directory when performing a command line start of a jar file.

Unless I am wrong and someone can tell me where it's exploding the jar file in a working directory on the system by default.

john Phan
January 14, 2014, 11:19 AM

Ahhh this reared it's ugly head again.

However this is extremely confusing. This suggests that require "digest/sha2" was removed or there is something wrong with the 1.3.2 build that is currently available for download. Maybe it's something to do with my local system trying to use 1.3.2 jar but some reminiscent of 1.2.2 is some where. GRrrr I rebuilt the server several times.

I can't see how this could possible be the case.

Adam Peck
January 14, 2014, 8:54 PM

1.3.x is still affected by which will prevent the SQS output from working.

Jordan Sissel
January 17, 2014, 10:25 PM

https://github.com/logstash/logstash/pull/924 should fix this (the patch is in both master and 1.3.x branches)


Adam Peck


john Phan



Fix versions

Affects versions