Skip to main content

Logstash throws error while installing plugins

While trying to install logstash plugin, I was getting below error:
$ /work/logstash/logstash-5.5.2/bin/logstash-plugin install logstash-input-cloudwatch
WARNING: A maven settings file already exist at ~/.m2/settings.xml, please review the content to make sure it include your proxies configuration.
Validating logstash-input-cloudwatch
Installing logstash-input-cloudwatch
Error Bundler::InstallError, retrying 1/10
An error occurred while installing logstash-core (5.5.2), and Bundler cannot continue.
Make sure that `gem install logstash-core -v '5.5.2'` succeeds before bundling.
Error Bundler::InstallError, retrying 2/10
An error occurred while installing logstash-core (5.5.2), and Bundler cannot continue.
Make sure that `gem install logstash-core -v '5.5.2'` succeeds before bundling.
Here are the things I did to make it work:
  1. Created maven ~/.m2/settings.xml file
    <?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <proxies>
    <proxy>
      <id>proxy.server.0</id>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.server</host>
      <port>80</port>
    </proxy>
  </proxies>
</settings>
  2. Set environment variables:
    export JAVA_HOME="/work/elasticsearch/jre1.8.0_162/"
export PATH=$JAVA_HOME/bin:$PATH
export http_proxy=http://proxy.server:80
export https_proxy=http://proxy.server:80
export NO_PROXY="127.0*,[::1],localhost,.local"
export no_proxy=$NO_PROXY
  3. Installed the plugin:
    /usr/bin/sudo -u root -H /bin/env https_proxy=http://proxy.server:80 HTTPS_PROXY=http://proxy.server:80 JRUBY_OPTS="-J-Dhttp.proxyHost=proxy.server -J-Dhttp.proxyPort=80" DEBUG=1 /work/logstash/logstash-5.5.2/bin/logstash-plugin install logstash-input-cloudwatch
Labels:
Location: London, UK

Comments

Post a Comment

Popular posts from this blog

MPlayer subtitle font problem in Windows

While playing a video with subtitles in mplayer, I was getting the following problem: New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). Solution is as follows: Right click on "My Computer". Select "Properties". Go to "Advanced" tab. Click on "Environment Variables". Delete "HOME" variable from User / System variables.
4 comments
Read more

wget and curl behind corporate proxy throws certificate is not trusted or certificate doesn't have a known issuer

If you try to run wget or curl in Ununtu/Debian behind corporate proxy, you might receive errors like: ERROR: The certificate of 'apertium.projectjj.com' is not trusted. ERROR: The certificate of 'apertium.projectjj.com' doesn't have a known issuer. wget https://apertium.projectjj.com/apt/apertium-packaging.public.gpg ERROR: cannot verify apertium.projectjj.com's certificate, issued by 'emailAddress=proxyteam@corporate.proxy.com,CN=diassl.corporate.proxy.com,OU=Division UK,O=Group name,L=Company,ST=GB,C=UK': Unable to locally verify the issuer's authority. To connect to apertium.projectjj.com insecurely, use `--no-check-certificate'. To solution is to install your company's CA certificate in Ubuntu. In Windows, open the first part of URL in your web browser. e.g. open https://apertium.projectjj.com in web browser. If you inspect the certifcate, you will see the same CN (diassl.corporate.proxy.com), as reported by the error above ...
Post a Comment
Read more

Kafka performance tuning

Performance Tuning of Kafka is critical when your cluster grow in size. Below are few points to consider to improve Kafka performance: Consumer group ID : Never use same exact consumer group ID for dozens of machines consuming from different topics. All of those commits will end up on the same exact partition of __consumer_offsets , hence the same broker, and this might in turn cause performance problems. Choose the consumer group ID to group_id+topic_name . Skewed : A broker is skewed if its number of partitions is greater that the average of partitions per broker on the given topic. Example: 2 brokers share 4 partitions, if one of them has 3 partitions, it is skewed (3 > 2). Try to make sure that none of the brokers is skewed. Spread : Brokers spread is the percentage of brokers in the cluster that has partitions for the given topic. Example: 3 brokers share a topic that has 2 partitions, so 66% of the brokers have partitions for this topic. Try to achieve 100% broker spread...
1 comment
Read more