-
Notifications
You must be signed in to change notification settings - Fork 27
Installation issues #17
Comments
having the same issue, I tried installing logstash-core and picked an arbitrary version that fell in the <2.0.0, >=1.4.0 category (i.e. 1.5.6) and that still is not working. Here's what I'm getting now: ubuntu@ip-172-31-15-36:~/logstash-input-dynamodb$ jruby -S gem install --local logstash-input-dynamodb-1.0.0-java.gem Conflicting dependency chains: versus: Gems matching logstash-core (< 3.0.0, >= 2.0.0.beta2): I'm not quite sure how dependencies are getting resolved but there's clearly some issues with the way dependencies are defined, that'd be my guess anyway. |
I have the same problem. If this isn't solved soon I'm turning to DocumentDB from MS. |
@devnullnor can't you use the docker container? |
How can I use docker for this task? Will it cost me anything? Thank you. |
@devnullnor Docker is free, I tried with docker and now its working perfectly. Check link https://hub.docker.com/r/mantika/logstash-dynamodb-streams/ 1> Step 1 - Install docker if you don't have already 2> Step 2 - Pull image Hope this help you to get started. |
Docker seems to have fixed it. Thank you! Question: Do I need to run |
No, logstash will automatically propagate the changes to elasticsearch, you don't need to run it periodically. |
I get an error: Which connection is refused? |
I'm having the same issue on Windows 7. Any updates?
|
@mwahidje #21 |
Thanks. It seems to be working now. |
Hi,
During setup I can across below issues, using logstash 1.5
1>
jruby -S gem install --local logstash-input-dynamodb-1.0.0-java.gem
ERROR: Could not find a valid gem 'logstash-core' (< 2.0.0, >= 1.4.0) in any repository
2>
sudo bin/plugin install –no-verify logstash-input-dynamodb
Validating –no-verify
Plugin –no-verify does not exist
ERROR: Installation aborted, verification failed for –no-verify
3>
sudo bin/plugin install –no-verify logstash-input-dynamodb-1.0.0.gem
ERROR: Mixed source of plugins, you can't mix local
.gem
and remote gemsSee: 'bin/plugin install --help'
The text was updated successfully, but these errors were encountered: