From owner-freebsd-elastic@freebsd.org Tue Mar 6 20:30:37 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 9201AF2C535 for ; Tue, 6 Mar 2018 20:30:37 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 3DA5568E9C for ; Tue, 6 Mar 2018 20:30:37 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 67FE020C08 for ; Tue, 6 Mar 2018 15:30:36 -0500 (EST) Received: from web4 ([10.202.2.214]) by compute3.internal (MEProxy); Tue, 06 Mar 2018 15:30:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=l1MtwI 6ZHSEqSPaNJjW3mJVptpHHDKPP/dbPoRJ60dw=; b=htssA0WZHUBhv6tvN8Ekin 9dq16PWHquxSWLDyxsl3qXjkY7wZutykqisUfv2RBmVGx28QZvDhP8TvHORZWbEy UYgE2wXSiOm7JfYHlweSp1X4ZbglLmIbrV2PETrcDVsf0kw2F9TcsJKVWCCJmb6S z7y0CTjShSgHBmLoR9eR/Ic+KMcNbjMZrtXr5isIuP7wLBJsj8gK71MP1H1g78k+ XwwcL8iifRp/kWA/RBOemN0GLRkw2Ahl+H5kVxK9JRQZj6MStxE5iJUEOOUB5Dbl r336YPNIAPTm/g6loDMHN2H3d49belnjac9zKFCBaMERKUmQwqPHG6feX4/sRezQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 43FC4BA43B; Tue, 6 Mar 2018 15:30:36 -0500 (EST) Message-Id: <1520368236.790950.1293860088.315C1855@webmail.messagingengine.com> From: Mark Felder To: freebsd-elastic@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b86e6959 Date: Tue, 06 Mar 2018 14:30:36 -0600 In-Reply-To: References: Subject: Re: Logstash 6.x plugins installation and updates 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 20:30:37 -0000 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) Alternatively we could try our hand at packaging plugins, but if they have a lot of dependencies it could lead us down a rabbithole... -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org