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