Closed pdehlke closed 7 years ago
For the record:
This turns out to be java throwing java.security.InvalidKeyException: Illegal key size or default parameters
and the whole gem-jruby-java chain swallowing it somewhere along the line. The solution is to install the JCE extensions:
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
Perhaps that dependency could be documented in README.md?
Closing this issue.
Using any of logstash versions 2.3.4, 2.4.0, or 5.3.2, with this configuration:
input { file { path => "/opt/logs/trx.log" start_position => "beginning" } }
output { google_cloud_storage { bucket => "xxxxxx-prod-trx-logs" key_path => "/root/logstash-5.3.1/config/trxlogger.p12" service_account => "trxlogging@xxxxxx.iam.gserviceaccount.com" temp_directory => "/tmp/logstash-gcs" log_file_prefix => "logstash_gcs" max_file_size_kbytes => 1024 output_format => "plain" date_pattern => "%Y-%m-%dT%H:00" flush_interval_secs => 2 gzip => true uploader_interval_secs => 60 } }
Logstash refuses to start as it is unable to initialize the GCS output plugin:
I've verified with openssl that
/root/logstash-5.3.1/config/trxlogger.p12
is a valid key file and that I can use the passphrasenotasecret
to open it. auditd confirms that the file is being opened and read by logstash.I've tried to use the workaround in #6 and trying to open the key file directly, with the same result:
Running on Ubuntu 16.04, java version "1.8.0_131", same behavior with logstash versions 2.3.4, 2.4.0, 5.3.1, and 5.3.2.