From owner-freebsd-elastic@freebsd.org Tue Mar 6 23:17:51 2018 Return-Path: Delivered-To: freebsd-elastic@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78C60F38A82 for ; Tue, 6 Mar 2018 23:17:51 +0000 (UTC) (envelope-from news@saz.gr) Received: from mail.doom.gr (doom.gr [46.101.135.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 10E3070C73 for ; Tue, 6 Mar 2018 23:17:50 +0000 (UTC) (envelope-from news@saz.gr) Received: from laptopidis (178-6-134.dynamic.cyta.gr [178.59.6.134]) by mail.doom.gr (Postfix) with ESMTPSA id 032B429C28D for ; Tue, 6 Mar 2018 23:17:37 +0000 (UTC) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-elastic@freebsd.org Subject: Re: Logstash 6.x plugins installation and updates References: <1520368236.790950.1293860088.315C1855@webmail.messagingengine.com> Date: Wed, 07 Mar 2018 01:17:31 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: news Message-ID: In-Reply-To: <1520368236.790950.1293860088.315C1855@webmail.messagingengine.com> User-Agent: Opera Mail/1.0 (Win32) X-BeenThere: freebsd-elastic@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Support of ElasticSearch-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 23:17:51 -0000 On Tue, 06 Mar 2018 22:30:36 +0200, Mark Felder wrote: > > > On Mon, Mar 5, 2018, at 11:03, news via freebsd-elastic wrote: >> >> the expr error is probably a syntax error because it's trying to use gnu >> expr and not the one we have on FreeBSD. >> > > Good catch. > >> The installation of the plugin I tried(logstash-output-plugin) seems to >> work. Also I used a working configuration from a linux setup I have on >> production and it didn't produce any errors. >> >> The big problems start when I try to update the included plugins, which >> can cause also problems if a plugin needs an updated version of a >> installed plugin(if we try to install the logstash-output-influxdb >> plugin >> on logstash5 port we can see it tries to update the logstash-core plugin >> and it fails) >> > > Is logstash-core a plugin or part of the software installed by the > package? (I'm not familiar with the plugins for logstash) > logstash-core is included on the default installation of logstash. If you run bin/logstash-plugin list you will not see it. Buit if a newer version is a depedency for another plugin installation it pops up. > Alternatively we could try our hand at packaging plugins, but if they > have a lot of dependencies it could lead us down a rabbithole... > Logstash keeps a local directory storage for "gems" on logstash/vendor/bundle/jruby/1.9/gems and logstash/vendor/bundle/jruby/2.3/gems . On logstash6 there is only the 2.3 directory as far as I have seen