From owner-freebsd-elastic@freebsd.org Tue Mar 13 16:45:24 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 30B92F30D94 for ; Tue, 13 Mar 2018 16:45:24 +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 D989768270 for ; Tue, 13 Mar 2018 16:45:23 +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 647CD21226 for ; Tue, 13 Mar 2018 12:45:23 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute3.internal (MEProxy); Tue, 13 Mar 2018 12:45:23 -0400 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=xoemG7 He6/PlolEuTI1GwB/QSmuzbU2OCacBIkfVgLE=; b=YeZkj1pt5m3G3MifgzKymW 704OOmJXhs0OzCmrsDNb7iQ3YutAev7cISiYIeZi+DdK4uT1Acz8PjJVYaLX63Zs xVsJh7MsPECUSDoRsg4gEEtpm5qWzsgZpWjltagcnyjOMRNH+FERuRMyBtOhHsrP waoUHeXk0CDqu460X3RPwku1pXdh8gvLUWhuc4W7V7yo8Gbu1ra25idz1r5MWYXm iYvTHSfHlYuKPkA5rFeiJmlj66IvmUDODNav8GzWJFTdxtWtiNLFKBdRJRQly1NF fhlr1MAuZG+atre28ShJkFsMQJgqlCFNkJoXBf3aZpadhgC7WDW/g8izpFF3qVLw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 3DB81BA43C; Tue, 13 Mar 2018 12:45:23 -0400 (EDT) Message-Id: <1520959523.4160936.1301725184.7519F688@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-54087d22 In-Reply-To: References: <1520613071.2637344.1297510176.6EBF62F8@webmail.messagingengine.com> Subject: Re: logstash improvements Date: Tue, 13 Mar 2018 11:45:23 -0500 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, 13 Mar 2018 16:45:24 -0000 On Fri, Mar 9, 2018, at 12:58, Fotis Zabaras via freebsd-elastic wrote: > On Fri, 09 Mar 2018 18:31:11 +0200, Mark Felder wrote: > > > As logstash6 has fewer users at the moment, I've started making large > > improvements to the port. My recent commit does the following: > > > > sysutils/logstash6: Many improvements > > > > - all config files are now in ETCDIR > > - rc script is updated to use logsearch.yml to locate logging config > > (logstash.conf) > > This will not break existing setups that used the > > ETCDIR/logstash.conf file, > > as that is > > now part of the default logstash.yml file > > - added configtest to rc script > > - sample logstash.conf file no longer includes invalid syntax > > - pkg-message had historical messages removed > > > > > > > > Previously all of the logstash.yml, jvm.options, etc were in > > /usr/local/logstash/config which is not an ideal location and may not be > > preserved between pkg upgrades. Now it's in ETCDIR where it belongs. > > > > Soon I plan to also add a dedicated daemon user instead of running as > > root by default. There's no good reason for this unless you need to > > listen on syslog port 514, but there are other ways of solving that > > problem (MAC framework, for example). > > > > Nice :) > Should we add also on the pkg-message the requirement of /proc to be > mounted > as it is needed by java? > I tend to automatically mount procfs and fdescfs for Java programs, but this would be a useful message for new users. -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org From owner-freebsd-elastic@freebsd.org Tue Mar 13 17:06:02 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 DD28BF331A1 for ; Tue, 13 Mar 2018 17:06:02 +0000 (UTC) (envelope-from SRS0=bbpu=GD=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 7C9116980D; Tue, 13 Mar 2018 17:06:02 +0000 (UTC) (envelope-from SRS0=bbpu=GD=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E6C3528417; Tue, 13 Mar 2018 17:58:00 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id D621628412; Tue, 13 Mar 2018 17:57:58 +0100 (CET) Subject: Re: logstash improvements To: Mark Felder , freebsd-elastic@freebsd.org References: <1520613071.2637344.1297510176.6EBF62F8@webmail.messagingengine.com> <1520959523.4160936.1301725184.7519F688@webmail.messagingengine.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Tue, 13 Mar 2018 17:57:58 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 MIME-Version: 1.0 In-Reply-To: <1520959523.4160936.1301725184.7519F688@webmail.messagingengine.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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, 13 Mar 2018 17:06:03 -0000 Mark Felder wrote on 2018/03/13 17:45: > > > On Fri, Mar 9, 2018, at 12:58, Fotis Zabaras via freebsd-elastic wrote: >> On Fri, 09 Mar 2018 18:31:11 +0200, Mark Felder wrote: >> >>> As logstash6 has fewer users at the moment, I've started making large >>> improvements to the port. My recent commit does the following: >>> >>> sysutils/logstash6: Many improvements >>> >>> - all config files are now in ETCDIR >>> - rc script is updated to use logsearch.yml to locate logging config >>> (logstash.conf) >>> This will not break existing setups that used the >>> ETCDIR/logstash.conf file, >>> as that is >>> now part of the default logstash.yml file >>> - added configtest to rc script >>> - sample logstash.conf file no longer includes invalid syntax >>> - pkg-message had historical messages removed >>> >>> >>> >>> Previously all of the logstash.yml, jvm.options, etc were in >>> /usr/local/logstash/config which is not an ideal location and may not be >>> preserved between pkg upgrades. Now it's in ETCDIR where it belongs. >>> >>> Soon I plan to also add a dedicated daemon user instead of running as >>> root by default. There's no good reason for this unless you need to >>> listen on syslog port 514, but there are other ways of solving that >>> problem (MAC framework, for example). >>> >> >> Nice :) >> Should we add also on the pkg-message the requirement of /proc to be >> mounted >> as it is needed by java? >> > > I tend to automatically mount procfs and fdescfs for Java programs, but this would be a useful message for new users. I have seen this message printed by some Java ports in the past but I never mounted procfs and fdescfs. What problems can I expect? Will the application print some warnings? For example I am running Elasticsearch on 5 machines without procfs and fdescfs. Miroslav Lachman From owner-freebsd-elastic@freebsd.org Wed Mar 14 14:47:47 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 D11C7F566C1 for ; Wed, 14 Mar 2018 14:47:47 +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 7296083E78 for ; Wed, 14 Mar 2018 14:47:47 +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 1544320DF6 for ; Wed, 14 Mar 2018 10:47:45 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Wed, 14 Mar 2018 10:47:45 -0400 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=dWkdH4 D/hgWbgv3maQu4rK+VHKvb2NAldKoo4w4TlQ8=; b=mIlEPcydo5FGDq6sMO5rIh zDwNQPNx9SmQoYq2/tIiuHsJVkk1TXMu9Exhv3nPmfK0zejkDe3QPYaBbT3NEBPm VJWmLQzSDZVHa1s788pE6UburqZLLzbDLPo1aT7zYGdlPLyfLkqR7zIenE2JZPr+ SX6Szr7B20QWwDamln3+wPBFpMS89lIUKLNl3CGrG0PgJgec691Kv1UK6JjJTQjf 8qb5I1PVixPAXFmYSfrmt3BG9QJDro4h41zOgj0lHVr/+3SfPdE/N+aUVCfcxQyz frLTLYZzz4UqW0u1+bUSBUYDJJjcTvTPh/ZAhSZKeEa4nZXMLljnkbxTY6e5kR6A == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id EA2789E17C; Wed, 14 Mar 2018 10:47:44 -0400 (EDT) Message-Id: <1521038864.1863960.1302926696.29C56D7B@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-54087d22 In-Reply-To: References: <1520613071.2637344.1297510176.6EBF62F8@webmail.messagingengine.com> <1520959523.4160936.1301725184.7519F688@webmail.messagingengine.com> Subject: Re: logstash improvements Date: Wed, 14 Mar 2018 09:47:44 -0500 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: Wed, 14 Mar 2018 14:47:48 -0000 On Tue, Mar 13, 2018, at 11:57, Miroslav Lachman wrote: > > > > I tend to automatically mount procfs and fdescfs for Java programs, but this would be a useful message for new users. > > I have seen this message printed by some Java ports in the past but I > never mounted procfs and fdescfs. What problems can I expect? Will the > application print some warnings? > For example I am running Elasticsearch on 5 machines without procfs and > fdescfs. > > Miroslav Lachman I have not figured out what things in Java require them or an easy way to determine that they are required, so I just assume they're always needed. -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org From owner-freebsd-elastic@freebsd.org Wed Mar 14 16:48:10 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 6C04BD4C for ; Wed, 14 Mar 2018 16:48:10 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 02B946A805 for ; Wed, 14 Mar 2018 16:48:10 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B8056D4A; Wed, 14 Mar 2018 16:48:09 +0000 (UTC) Delivered-To: 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 A588BD49 for ; Wed, 14 Mar 2018 16:48:09 +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 4E7B96A803 for ; Wed, 14 Mar 2018 16:48:08 +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 8FEBC21097; Wed, 14 Mar 2018 12:48:08 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Wed, 14 Mar 2018 12:48:08 -0400 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=lX75AC mRu24Svkui5ig858FdTYbgaxeXhT31cd/Na0w=; b=K2ChZwr0vxsj2msIfoOp4p Qz03Liy7aIXmGvMnOkOOuHWE1Fimmh7GPYZ1RoIgbZCne+ItzVIfeUY7VgZFNkfu 1g7S3bMtss9o67haOWU/RMk3D0NVDH556nnYypJEvFnrCCNSC31xiZqHqmjGSgAP gWfbiKmTPTMsP7+kl7PTemFJV81aLpEHqouifpTgZ/hp4x0poKJe+I2yj5eDr2wN SAI5yG+dV2fRqSFNOqLgxlxQU492Wa+vtfz27bwf/gWTa3uSE5nlSW787XEtsSOQ T3+ptRxpgrOadOChDOhhDZxBQ6842oExq/ReSB8aKNUERHUDgzCX52zalRhgdRlw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 6CDE69E17C; Wed, 14 Mar 2018 12:48:08 -0400 (EDT) Message-Id: <1521046088.2861451.1303090824.0D4A3A30@webmail.messagingengine.com> From: Mark Felder To: Sonny Smith , 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-54087d22 Subject: Re: FreeBSD Port: textproc/elasticsearch5-x-pack References: <039f01d3b70c$eca986e0$c5fc94a0$@shortcircuittech.us> In-Reply-To: <039f01d3b70c$eca986e0$c5fc94a0$@shortcircuittech.us> Date: Wed, 14 Mar 2018 11:48:08 -0500 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: Wed, 14 Mar 2018 16:48:10 -0000 On Thu, Mar 8, 2018, at 13:40, Sonny Smith wrote: > Hello Elastic! > > Is there a port for Logstash x-pack? If not, has anyone gotten > "logstash-plugin" to execute on FreeBSD? > > > > Thank you for any guidance you can provide. > I'm working through these issues right now, but currently focusing on version 6.x. The "x-pack" packages for 5.x will most certainly be removed because they're not doing the right things. You are not supposed to be downloading/extracting the zip file for x-pack, which is what we're doing with the packages. There is more to it as handled by the "foo-plugin" tools. If all goes well the plugin scripts could be fixed today, but I hope by the end of the week for sure. -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org From owner-freebsd-elastic@freebsd.org Wed Mar 14 17:31:53 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 B0C28F2D228 for ; Wed, 14 Mar 2018 17:31:53 +0000 (UTC) (envelope-from sonny@shortcircuittech.us) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 443976CACC for ; Wed, 14 Mar 2018 17:31:53 +0000 (UTC) (envelope-from sonny@shortcircuittech.us) Received: by mailman.ysv.freebsd.org (Postfix) id 05468F2D226; Wed, 14 Mar 2018 17:31:53 +0000 (UTC) Delivered-To: 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 E5963F2D224 for ; Wed, 14 Mar 2018 17:31:52 +0000 (UTC) (envelope-from sonny@shortcircuittech.us) Received: from smtp74.iad3a.emailsrvr.com (smtp74.iad3a.emailsrvr.com [173.203.187.74]) (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 6F03A6CAC7 for ; Wed, 14 Mar 2018 17:31:52 +0000 (UTC) (envelope-from sonny@shortcircuittech.us) Received: from smtp10.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp10.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id E23546338; Wed, 14 Mar 2018 13:24:24 -0400 (EDT) X-Auth-ID: sonny@shortcircuittech.us Received: by smtp10.relay.iad3a.emailsrvr.com (Authenticated sender: sonny-AT-shortcircuittech.us) with ESMTPSA id 961F75E37; Wed, 14 Mar 2018 13:24:24 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=shortcircuittech.us; s=20170907-95xjblxr; t=1521048264; bh=84Lt3sx/lTkssLg3+werIhM4kucMVchFzjsRKFcAFis=; h=From:To:Subject:Date:From; b=krmhkLH60So5O0XUkxKFw31AjlltiYff4QzwwiCAYFTMzpv9XD6lMOobkGCh+yMY0 kJoigjTt8bFMfDkNY2NgWEQFaQxIOECIABYd5//cVh3Eu964LgagUi2TDjum9ZOLpw ghk0/qzxun/qs8dYHvhjFh3DdeMU6DSLqPRHTwwE= X-Sender-Id: sonny@shortcircuittech.us Received: from Rambleon (ip98-164-64-75.no.no.cox.net [98.164.64.75]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:465 (trex/5.7.12); Wed, 14 Mar 2018 13:24:24 -0400 From: "Sonny Smith" To: "'Mark Felder'" , References: <039f01d3b70c$eca986e0$c5fc94a0$@shortcircuittech.us> <1521046088.2861451.1303090824.0D4A3A30@webmail.messagingengine.com> In-Reply-To: <1521046088.2861451.1303090824.0D4A3A30@webmail.messagingengine.com> Subject: RE: FreeBSD Port: textproc/elasticsearch5-x-pack Date: Wed, 14 Mar 2018 12:24:24 -0500 Organization: Short Circuit Technology Message-ID: <006a01d3bbb9$4ccfd870$e66f8950$@shortcircuittech.us> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQDvjFMWKbPw973VPj6XlBVnsw+EIAHwg++TpYjTaZA= Content-Language: en-us 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: Wed, 14 Mar 2018 17:31:53 -0000 Thanks for the insight! I'm documenting this for a lab I'm building so it's pretty easy to move = to 6.x now that it's available. That way, you don't have to split your = attention between versions. https://github.com/lordcantide/homelab-blackbox-elasticsearch If I'm hearing your recommendation: I should build on 6.x as that is = likely the first build that will have properly working foo-plugins. Sonny -----Original Message----- From: Mark Felder [mailto:feld@FreeBSD.org]=20 Sent: Wednesday, March 14, 2018 11:48 AM To: Sonny Smith ; elastic@FreeBSD.org Subject: Re: FreeBSD Port: textproc/elasticsearch5-x-pack On Thu, Mar 8, 2018, at 13:40, Sonny Smith wrote: > Hello Elastic! >=20 > Is there a port for Logstash x-pack? If not, has anyone gotten=20 > "logstash-plugin" to execute on FreeBSD? >=20 > =20 >=20 > Thank you for any guidance you can provide. >=20 I'm working through these issues right now, but currently focusing on = version 6.x. The "x-pack" packages for 5.x will most certainly be = removed because they're not doing the right things. You are not supposed = to be downloading/extracting the zip file for x-pack, which is what = we're doing with the packages. There is more to it as handled by the = "foo-plugin" tools. If all goes well the plugin scripts could be fixed today, but I hope by = the end of the week for sure. -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org From owner-freebsd-elastic@freebsd.org Wed Mar 14 19:18:47 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 B968AF3A2F1 for ; Wed, 14 Mar 2018 19:18:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5218272656 for ; Wed, 14 Mar 2018 19:18:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0EE5EF3A2F0; Wed, 14 Mar 2018 19:18:47 +0000 (UTC) Delivered-To: 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 F1CFFF3A2EF for ; Wed, 14 Mar 2018 19:18:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EE7972650 for ; Wed, 14 Mar 2018 19:18:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id BB3E4137B for ; Wed, 14 Mar 2018 19:18:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2EJIj6x026547 for ; Wed, 14 Mar 2018 19:18:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2EJIjEd026545 for elastic@FreeBSD.org; Wed, 14 Mar 2018 19:18:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: elastic@FreeBSD.org Subject: [Bug 226301] textproc/elasticsearch6: elasticsearch/config: No such file or directory Date: Wed, 14 Mar 2018 19:18:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: feld@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 14 Mar 2018 19:18:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226301 --- Comment #3 from commit-hook@freebsd.org --- A commit references this bug: Author: feld Date: Wed Mar 14 19:17:59 UTC 2018 New revision: 464526 URL: https://svnweb.freebsd.org/changeset/ports/464526 Log: textproc/elasticsearch6: Fix ability to install plugins - Update pkg-message to provide very useful info - Use login_class=3Droot by default to help users avoid this issue (affec= ts everyone) PR: 226301 Changes: head/textproc/elasticsearch6/Makefile head/textproc/elasticsearch6/files/elasticsearch.in head/textproc/elasticsearch6/files/pkg-message.in --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-elastic@freebsd.org Wed Mar 14 19:30:18 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 A6C24F3F54C for ; Wed, 14 Mar 2018 19:30:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3B9DC73166 for ; Wed, 14 Mar 2018 19:30:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E6D90F3F53E; Wed, 14 Mar 2018 19:30:17 +0000 (UTC) Delivered-To: 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 D583EF3F53D for ; Wed, 14 Mar 2018 19:30:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F66573164 for ; Wed, 14 Mar 2018 19:30:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A88EA14DE for ; Wed, 14 Mar 2018 19:30:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2EJUGBA054342 for ; Wed, 14 Mar 2018 19:30:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2EJUGtb054341 for elastic@FreeBSD.org; Wed, 14 Mar 2018 19:30:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: elastic@FreeBSD.org Subject: [Bug 226301] textproc/elasticsearch6: elasticsearch/config: No such file or directory Date: Wed, 14 Mar 2018 19:30:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: feld@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: feld@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 14 Mar 2018 19:30:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226301 Mark Felder changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --- Comment #4 from Mark Felder --- This should be fixed now. It's not as flexible as we would like, but it see= ms that even upstream doesn't allow this to be flexible on Linux either. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-elastic@freebsd.org Wed Mar 14 22:50:59 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 A8F60F4F904 for ; Wed, 14 Mar 2018 22:50:59 +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 5CAC07B1E3 for ; Wed, 14 Mar 2018 22:50:59 +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 B4C1A20CD2 for ; Wed, 14 Mar 2018 18:50:58 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute3.internal (MEProxy); Wed, 14 Mar 2018 18:50:58 -0400 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=kIeX8d UOR77QTpWH0cDbWrXU7SHA5GyfKPDhecJZirU=; b=b+wHnIFzd3uqN5AaekCaFN YTLFOsGEQyZYJyyzofmUhOB4q0UFbt+ucBcQF6mgUBnUWuXUhDCitSTjtXwGaz6u iP9IzcfqFiSElAunS5vfsRenYlbRubE99Wo+XNXoqPTz0I2MaCKwbu33oZoXyrUn s5YDRUoBcxNPgpoD27YnYN3cVFGYg0NGyykM+py7SPnW4L30jC4dJ1vXdrP4Qz8Y Vg2aEkYY1G+PHqkDF5YrbKNhycTmfDiJyaClzjPbLlGSwVSE4pgBGrt/FA88ES07 grD+hn+AdsB62o60F4Lv1/WBlFrlZiVxtG1EFXBO/s8MFC9W3PWjHhOnKOy2DWPg == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 95949BA43B; Wed, 14 Mar 2018 18:50:58 -0400 (EDT) Message-Id: <1521067858.2552269.1303508064.7EF8BB55@webmail.messagingengine.com> From: Mark Felder To: freebsd-elastic@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-54087d22 Subject: Re: Logstash 6.x plugins installation and updates In-Reply-To: Date: Wed, 14 Mar 2018 17:50:58 -0500 References: <1520368236.790950.1293860088.315C1855@webmail.messagingengine.com> 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: Wed, 14 Mar 2018 22:50:59 -0000 On Tue, Mar 6, 2018, at 18:17, news via freebsd-elastic wrote: > On Tue, 06 Mar 2018 22:30:36 +0200, Mark Felder wrote: >=20 > > > > > > 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 g= nu > >> expr and not the one we have on FreeBSD. > >> This seems to work now. I found and fixed the expr error. Not a GNU extensi= on -- just an error in jruby which has been fixed upstream, but logstash do= esn't bundle a version with this fixed. The update issue was an upstream bu= g which I've patched for us as well. root@elk:/usr/local/logstash # ./bin/logstash-plugin install x-pack Downloading file: https://artifacts.elastic.co/downloads/logstash-plugins/x= -pack/x-pack-6.2.2.zip Downloading [=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D] 100% Installing file: /tmp/studtmp-5dd043f3e10e926cdabe34b8c1870b8ea4c9f0b191590= 08f6b8c8ee90083/x-pack-6.2.2.zip Install successful root@elk:/usr/local/logstash # ./bin/logstash-plugin update Updating logstash-codec-cef, logstash-codec-collectd, logstash-codec-dots, = logstash-codec-edn, logstash-codec-edn_lines, logstash-codec-es_bulk, logst= ash-codec-fluent, logstash-codec-graphite, logstash-codec-json, logstash-co= dec-json_lines, logstash-codec-line, logstash-codec-msgpack, logstash-codec= -multiline, logstash-codec-netflow, logstash-codec-plain, logstash-codec-ru= bydebug, logstash-filter-aggregate, logstash-filter-anonymize, logstash-fil= ter-cidr, logstash-filter-clone, logstash-filter-csv, logstash-filter-date,= logstash-filter-de_dot, logstash-filter-dissect, logstash-filter-dns, logs= tash-filter-drop, logstash-filter-elasticsearch, logstash-filter-fingerprin= t, logstash-filter-geoip, logstash-filter-grok, logstash-filter-jdbc_static= , logstash-filter-jdbc_streaming, logstash-filter-json, logstash-filter-kv,= logstash-filter-metrics, logstash-filter-mutate, logstash-filter-ruby, log= stash-filter-sleep, logstash-filter-split, logstash-filter-syslog_pri, logs= tash-filter-throttle, logstash-filter-translate, logstash-filter-truncate, = logstash-filter-urldecode, logstash-filter-useragent, logstash-filter-xml, = logstash-input-beats, logstash-input-dead_letter_queue, logstash-input-elas= ticsearch, logstash-input-exec, logstash-input-file, logstash-input-ganglia= , logstash-input-gelf, logstash-input-generator, logstash-input-graphite, l= ogstash-input-heartbeat, logstash-input-http, logstash-input-http_poller, l= ogstash-input-imap, logstash-input-jdbc, logstash-input-kafka, logstash-inp= ut-pipe, logstash-input-rabbitmq, logstash-input-redis, logstash-input-s3, = logstash-input-snmptrap, logstash-input-sqs, logstash-input-stdin, logstash= -input-syslog, logstash-input-tcp, logstash-input-twitter, logstash-input-u= dp, logstash-input-unix, logstash-output-cloudwatch, logstash-output-csv, l= ogstash-output-elasticsearch, logstash-output-email, logstash-output-file, = logstash-output-graphite, logstash-output-http, logstash-output-kafka, logs= tash-output-lumberjack, logstash-output-nagios, logstash-output-null, logst= ash-output-pagerduty, logstash-output-pipe, logstash-output-rabbitmq, logst= ash-output-redis, logstash-output-s3, logstash-output-sns, logstash-output-= sqs, logstash-output-stdout, logstash-output-tcp, logstash-output-udp, logs= tash-output-webhdfs, x-pack Updated logstash-codec-fluent 3.1.5 to 3.2.0 Updated logstash-codec-netflow 3.11.0 to 3.11.2 Updated logstash-filter-dns 3.0.7 to 3.0.8 Updated logstash-filter-grok 4.0.2 to 4.0.3 Updated logstash-filter-kv 4.0.3 to 4.1.0 Updated logstash-filter-mutate 3.2.0 to 3.3.1 Updated logstash-input-beats 5.0.6 to 5.0.11 Updated logstash-input-exec 3.1.5 to 3.2.0 Updated logstash-input-jdbc 4.3.3 to 4.3.5 Updated logstash-input-syslog 3.2.4 to 3.4.0 Updated logstash-input-tcp 5.0.3 to 5.0.4 Updated logstash-output-elasticsearch 9.0.2 to 9.0.3 So at this point I think it's safe to say that Logstash on FreeBSD has fewe= r bugs than on their "supported" platforms. *smirk* Next up: backporting these fixes to elastic/kibana/logstash 5.x --=20 Mark Felder ports-secteam & portmgr member feld@FreeBSD.org From owner-freebsd-elastic@freebsd.org Thu Mar 15 20:53:12 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 6A882F52992 for ; Thu, 15 Mar 2018 20:53:12 +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 0750277F94 for ; Thu, 15 Mar 2018 20:53:11 +0000 (UTC) (envelope-from news@saz.gr) Received: from laptopidis (a8570-adsl6.pck.nerim.net [213.41.132.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.doom.gr (Postfix) with ESMTPSA id D2A9029AC3F for ; Thu, 15 Mar 2018 20:53:03 +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> <1521067858.2552269.1303508064.7EF8BB55@webmail.messagingengine.com> Date: Thu, 15 Mar 2018 21:53:00 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Fotis Zabaras" Message-ID: In-Reply-To: <1521067858.2552269.1303508064.7EF8BB55@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: Thu, 15 Mar 2018 20:53:12 -0000 On Wed, 14 Mar 2018 23:50:58 +0100, Mark Felder wrote: > > > On Tue, Mar 6, 2018, at 18:17, news via freebsd-elastic wrote: >> 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. >> >> > > This seems to work now. I found and fixed the expr error. Not a GNU > extension -- just an error in jruby which has been fixed upstream, but > logstash doesn't bundle a version with this fixed. The update issue was > an upstream bug which I've patched for us as well. > > root@elk:/usr/local/logstash # ./bin/logstash-plugin install x-pack > Downloading file: > https://artifacts.elastic.co/downloads/logstash-plugins/x-pack/x-pack-6.2.2.zip > Downloading > [=============================================================] 100% > Installing file: > /tmp/studtmp-5dd043f3e10e926cdabe34b8c1870b8ea4c9f0b19159008f6b8c8ee90083/x-pack-6.2.2.zip > Install successful > root@elk:/usr/local/logstash # ./bin/logstash-plugin update > Updating logstash-codec-cef, logstash-codec-collectd, > logstash-codec-dots, logstash-codec-edn, logstash-codec-edn_lines, > logstash-codec-es_bulk, logstash-codec-fluent, logstash-codec-graphite, > logstash-codec-json, logstash-codec-json_lines, logstash-codec-line, > logstash-codec-msgpack, logstash-codec-multiline, > logstash-codec-netflow, logstash-codec-plain, logstash-codec-rubydebug, > logstash-filter-aggregate, logstash-filter-anonymize, > logstash-filter-cidr, logstash-filter-clone, logstash-filter-csv, > logstash-filter-date, logstash-filter-de_dot, logstash-filter-dissect, > logstash-filter-dns, logstash-filter-drop, > logstash-filter-elasticsearch, logstash-filter-fingerprint, > logstash-filter-geoip, logstash-filter-grok, > logstash-filter-jdbc_static, logstash-filter-jdbc_streaming, > logstash-filter-json, logstash-filter-kv, logstash-filter-metrics, > logstash-filter-mutate, logstash-filter-ruby, logstash-filter-sleep, > logstash-filter-split, logstash-filter-syslog_pri, > logstash-filter-throttle, l > ogstash-filter-translate, logstash-filter-truncate, > logstash-filter-urldecode, logstash-filter-useragent, > logstash-filter-xml, logstash-input-beats, > logstash-input-dead_letter_queue, logstash-input-elasticsearch, > logstash-input-exec, logstash-input-file, logstash-input-ganglia, > logstash-input-gelf, logstash-input-generator, logstash-input-graphite, > logstash-input-heartbeat, logstash-input-http, > logstash-input-http_poller, logstash-input-imap, logstash-input-jdbc, > logstash-input-kafka, logstash-input-pipe, logstash-input-rabbitmq, > logstash-input-redis, logstash-input-s3, logstash-input-snmptrap, > logstash-input-sqs, logstash-input-stdin, logstash-input-syslog, > logstash-input-tcp, logstash-input-twitter, logstash-input-udp, > logstash-input-unix, logstash-output-cloudwatch, logstash-output-csv, > logstash-output-elasticsearch, logstash-output-email, > logstash-output-file, logstash-output-graphite, logstash-output-http, > logstash-output-kafka, logstash-output-lumberjack, logstash-output-nagio > s, logstash-output-null, logstash-output-pagerduty, > logstash-output-pipe, logstash-output-rabbitmq, logstash-output-redis, > logstash-output-s3, logstash-output-sns, logstash-output-sqs, > logstash-output-stdout, logstash-output-tcp, logstash-output-udp, > logstash-output-webhdfs, x-pack > Updated logstash-codec-fluent 3.1.5 to 3.2.0 > Updated logstash-codec-netflow 3.11.0 to 3.11.2 > Updated logstash-filter-dns 3.0.7 to 3.0.8 > Updated logstash-filter-grok 4.0.2 to 4.0.3 > Updated logstash-filter-kv 4.0.3 to 4.1.0 > Updated logstash-filter-mutate 3.2.0 to 3.3.1 > Updated logstash-input-beats 5.0.6 to 5.0.11 > Updated logstash-input-exec 3.1.5 to 3.2.0 > Updated logstash-input-jdbc 4.3.3 to 4.3.5 > Updated logstash-input-syslog 3.2.4 to 3.4.0 > Updated logstash-input-tcp 5.0.3 to 5.0.4 > Updated logstash-output-elasticsearch 9.0.2 to 9.0.3 > > > So at this point I think it's safe to say that Logstash on FreeBSD has > fewer bugs than on their "supported" platforms. *smirk* > > > Next up: backporting these fixes to elastic/kibana/logstash 5.x > > I just tested it on a vm and it works :) Good job on fixing this problem. It is a lifesaver for people who work with custom logfiles :) Fotis