Comments (4)
If you throw --debug on the end of the startup for logstash, you'll get quite a bit more information. Also for the enumeration issues, I am 90% done with moving this plugin from aws-sdk v1 to v2 which should increase speeds quite a bit. Just waiting on testing
from logstash-input-s3.
@DanielRedOak Thanks for following up. Here is what I get with the debug flag turned on. It just sits there, does it mean it is processing? The bucket is pretty huge.
sing version 0.1.x input plugin 's3'. This plugin isn't well supported by the community and likely has no maintainer. {:level=>:info}
Using version 0.1.x codec plugin 'plain'. This plugin isn't well supported by the community and likely has no maintainer. {:level=>:info}
Using version 0.1.x output plugin 'stdout'. This plugin isn't well supported by the community and likely has no maintainer. {:level=>:info}
Using version 0.1.x codec plugin 'rubydebug'. This plugin isn't well supported by the community and likely has no maintainer. {:level=>:info}
Registering s3 input {:bucket=>"my-cloudtrai-bucket", :region=>"us-east-1", :level=>:info}
Pipeline started {:level=>:info}
Logstash startup completed
Using default generated file for the sincedb {:filename=>"/root/.sincedb_dc760775953947267f2d81029009a3a0", :level=>:info}
Here is my logstash config to test this out.
nput {
s3 {
bucket => "my-cloudtrai-bucket"
access_key_id => "ID"
secret_access_key => "KEY"
type => "cloudtrail"
}
}
output {
stdout {
codec => rubydebug
}
}
from logstash-input-s3.
Just an update. I tried testing with a much smaller bucket and the plugin responded so I think it is at least working. Interestingly enough it is throwing some errors now. I will look in to the errors but I figured I would at least post an update.
Here's what the errors are reporting:
Error: No such file or directory - /tmp/logstash/ELBAccessLogTestFile {:level=>:error}
A plugin had an unrecoverable error. Will restart this plugin.
Plugin: <LogStash::Inputs::S3 bucket=>"my-cloudtrail-bucket", access_key_id=>"ID", secret_access_key=>"KEY", type=>"cloudtrail", region=>"us-east-1", temporary_directory=>"/tmp/logstash">
Error: No such file or directory - /tmp/logstash/ELBAccessLogTestFile {:level=>:error}
A plugin had an unrecoverable error. Will restart this plugin.
Plugin: <LogStash::Inputs::S3 bucket=>"my-cloudtrail-bucket", access_key_id=>"ID", secret_access_key=>"KEY", type=>"cloudtrail", region=>"us-east-1", temporary_directory=>"/tmp/logstash">
Error: No such file or directory - /tmp/logstash/ELBAccessLogTestFile {:level=>:error}
A plugin had an unrecoverable error. Will restart this plugin.
Plugin: <LogStash::Inputs::S3 bucket=>"my-cloudtrail-bucket", access_key_id=>"ID", secret_access_key=>"KEY", type=>"cloudtrail", region=>"us-east-1", temporary_directory=>"/tmp/logstash">
Got it working by explicity creating /tmp/logstash
.
from logstash-input-s3.
I wonder if there is any way to change this location /tmp/logstash
to something else, so it persists with system reboots. tmp/ files are getting cleaned up in a reboot.
from logstash-input-s3.
Related Issues (20)
- logstash s3 input enable use_accelerate_endpoint failed
- Logstash S3 input plugin assume role not working HOT 9
- backup_to_dir backups rotation
- seahorse::client:: networking error HOT 2
- S3 input plugin is not reading AWS-KMS (CMK) encrypted bucket HOT 2
- Large files are very slow to read locally HOT 2
- Files being unprocessed with the same last modified timestamp HOT 6
- Could not fetch objects from "requester pays" enabled bucket HOT 1
- logstash-input-s3 3.6.0 restarting due to unrecoverable error with CipherSuites array issue HOT 1
- s3 input plugin not handling shutdown correctly, leading to duplicates once started again HOT 2
- Files being unprocessed because of cutoff time calculation part
- logstash-input-s3 Error: Net::OpenTimeout 没人解决就关闭问题吗?
- [Logstash 7.16.2] S3 input plugin replaces the region in endpnt url HOT 7
- [Docs] Document workaround when using s3 private link endpoints with us-east-1
- sincedb file not created, files from bucket not deleted HOT 2
- S3 input plugin does not work with IAM role WebIdentity HOT 3
- Plugin dont process objects correctly, dont delete or backup HOT 11
- Files with same last modified timestamp miss processing HOT 1
- Constant and frequent s3 plugin restart due to TCP connection failure
- java.util.concurrent.ScheduledThreadPoolExecutor related to S3 input resulting in all pipeline logstash failure. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from logstash-input-s3.