Error occurs when using s3 as sole input

Description

I had a working configuration using file and s3 inputs.

When I removed the file input, I began receiving this message when starting logstash :

Using milestone 1 input plugin 's3'. 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.1/plugin-milestones {:level=>:warn}
---------------------------------------------------------

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:
uninitialized constant Digest::MD5

The error did not occur when I restored my file input back to the configuration.

I stripped down the configs to the minimum set that trigger the same error condition :

The s3 bucket and credentials provided are invalid, but they produce the same MD5 error that I produced with valid credentials / bucket.

Adding a file input to the configuration before the s3 definition in the above config results an AWS authentication error, as expected. Adding it after the s3 definition results in the original MD5 error.

I have a workaround to this bug - keeping a no-op file input in my configuration.

Gliffy Diagrams

Activity

Show:

Richard Pijnenburg September 16, 2013 at 8:40 AM

This has been merged and will be in the next release.

Richard Pijnenburg September 12, 2013 at 1:11 PM

Fix is in https://github.com/logstash/logstash/pull/636 awaiting validation from Jordan

Richard Pijnenburg September 12, 2013 at 12:48 PM

Seems that the library isnt included while loading the plugin.

Should fix the issue. im trying this out now.

Richard Pijnenburg September 12, 2013 at 12:44 PM

I can confirm the bug.
Will try to find out why this is happening.

Fixed

Details

Assignee

Reporter

Fix versions

Affects versions

Created September 10, 2013 at 3:47 PM
Updated September 16, 2013 at 8:40 AM
Resolved September 16, 2013 at 8:40 AM