From owner-freebsd-elastic@freebsd.org Fri Mar 30 12:15:55 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 D7EB7F6773F for ; Fri, 30 Mar 2018 12:15:54 +0000 (UTC) (envelope-from mich@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 7709885EF1 for ; Fri, 30 Mar 2018 12:15:54 +0000 (UTC) (envelope-from mich@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 38959F6773E; Fri, 30 Mar 2018 12:15:54 +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 273ADF6773D for ; Fri, 30 Mar 2018 12:15:54 +0000 (UTC) (envelope-from mich@freebsd.org) Received: from mail.prodnet.eu (mail.prodnet.eu [IPv6:2001:41d0:1008:608::]) (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 BFCED85EEF for ; Fri, 30 Mar 2018 12:15:53 +0000 (UTC) (envelope-from mich@freebsd.org) Received: from [192.168.1.11] (AMontsouris-682-1-47-175.w90-87.abo.wanadoo.fr [90.87.210.175]) by mail.prodnet.eu (Postfix) with ESMTPA id D5FFA63B76 for ; Fri, 30 Mar 2018 14:15:42 +0200 (CEST) Authentication-Results: mail.prodnet.eu; dmarc=none (p=none dis=none) header.from=freebsd.org From: "Michael Landin" To: elastic@FreeBSD.org Subject: FreeBSD Port: sysutils/logstash5 Date: Fri, 30 Mar 2018 14:15:42 +0200 X-Mailer: MailMate (1.11r5462) Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown Content-Transfer-Encoding: quoted-printable 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: Fri, 30 Mar 2018 12:15:55 -0000 hi, It seems since the ES (and logstash5) 5.3.0 -> 5.6.8 the log-rotation = (log4j2) is no longer working ? ES is correctly started : 29156 0- I 5397:38.18 /usr/local/openjdk8/bin/java -Xms8g -Xmx8g = -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=3D75 = -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC = -XX:+AlwaysPreTouch -server -Djava.awt.headless=3Dtrue = -Dfile.encoding=3DUTF-8 -Djna.nosys=3Dtrue -Dio.netty.noUnsafe=3Dtrue = -Dio.netty.noKeySetOptimization=3Dtrue -Dlog4j.shutdownHookEnabled=3Dfals= e = -Dlog4j2.disable.jmx=3Dtrue -Dlog4j.skipJansi=3Dtrue = -XX:+HeapDumpOnOutOfMemoryError = -Des.path.home=3D/usr/local/lib/elasticsearch -cp = /usr/local/lib/elasticsearch/lib/* = org.elasticsearch.bootstrap.Elasticsearch -d = --pidfile=3D/var/run/elasticsearch/elasticsearch.pid = -Epath.conf=3D/usr/local/etc/elasticsearch Upgrade was done the 26/3/18 : =E2=9D=AF ls -alt /var/log/elasticsearch total 16286 drwxr-xr-x 2 elasticsearch elasticsearch 83 Mar 30 13:56 . -rw-r--r-- 1 elasticsearch elasticsearch 119977419 Mar 30 10:46 = jaf_deprecation.log drwxr-xr-x 6 root wheel 64 Mar 30 09:00 .. -rw-r--r-- 1 elasticsearch elasticsearch 5408903 Mar 28 16:15 = jaf.log -rw-r--r-- 1 elasticsearch elasticsearch 2180721 Mar 26 22:47 = jaf-2018-03-26.log -rw-r--r-- 1 elasticsearch elasticsearch 49059 Mar 24 13:57 = jaf-2018-03-24.log -rw-r--r-- 1 elasticsearch elasticsearch 2101479 Mar 23 13:28 = jaf-2018-03-23.log -rw-r--r-- 1 elasticsearch elasticsearch 49569 Mar 22 11:31 = jaf-2018-03-22.log -rw-r--r-- 1 elasticsearch elasticsearch 366249 Mar 21 10:19 = jaf-2018-03-21.log My log4j2 policy looks correct: appender.rolling.type =3D RollingFile appender.rolling.name =3D rolling appender.rolling.fileName =3D = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}.= log appender.rolling.layout.type =3D PatternLayout appender.rolling.layout.pattern =3D [%d{ISO8601}][%-5p][%-25c{1.}] = %marker%.-10000m%n appender.rolling.filePattern =3D = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}-= %d{yyyy-MM-dd}.log appender.rolling.policies.type =3D Policies appender.rolling.policies.time.type =3D TimeBasedTriggeringPolicy appender.rolling.policies.time.interval =3D 1 appender.rolling.policies.time.modulate =3D true Same issue for logstash5. Thanks, /mich From owner-freebsd-elastic@freebsd.org Fri Mar 30 19:35:00 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 A8B91F5BF48; Fri, 30 Mar 2018 19:35:00 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 5518D7B604; Fri, 30 Mar 2018 19:35:00 +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 AD2C020FC7; Fri, 30 Mar 2018 15:34:59 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute3.internal (MEProxy); Fri, 30 Mar 2018 15:34:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=0nYQZ1 cblautmzAJ2hBFoQvfLIVkEhYi3zPlbeWc9k0=; b=RALA5B41NcIA0yx6LYG3uS Lb9XWPDajYqbuGFsQV3e8OvTvhnoSAvJnV8/47gKwFj2Qgt1ToGIWcGHN7Gcwt9m nGpcSQDpDRQK4XKdX52XB8DJPgZvsECzGDMvoANjNN1glf/kQ0YoIfZOHb50qoLQ YEBAyQivSXjzlJ9+N00ZBcBGln8mpv9iicEKH4vZ6noHzecko1hhlEkcLNI0/VWC +pyfC1a/sT2dYLZE0u2UHEettyIeKQJXgjPyPOSBYpXXZjAobqcl42zAggunN+aV gSUpUAIg7EBHSOyFAQflRwTeuUAsOj75f8h9vasjUioIHd4/5tB+70hLw4HxFKEw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 8B17EBA43B; Fri, 30 Mar 2018 15:34:59 -0400 (EDT) Message-Id: <1522438499.493684.1321661104.266F8B86@webmail.messagingengine.com> From: Mark Felder To: =?utf-8?Q?Leander=20Sch=C3=A4fer?= , freebsd-ports@freebsd.org Cc: 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-bb419338 References: Date: Fri, 30 Mar 2018 14:34:59 -0500 Subject: Re: FreeBSD textproc/elasticsearch6 does not honour /etc/profile In-Reply-To: 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: Fri, 30 Mar 2018 19:35:00 -0000 On Thu, Mar 29, 2018, at 05:43, Leander Sch=C3=A4fer wrote: > Hello, >=20 > it looks like textproc/elasticsearch6 does not honour /etc/profile? > Please have a look for detailed description and reproduction of the > issue: > https://forums.freebsd.org/threads/textproc-elasticsearch6-does-not-honou= r-etc-profile.65338/ >=20 > Best regards, >=20 > Leander S. I'm pretty sure this is not supposed to work. /etc/profile is used by sh(1)= and would only be read during a login shell. The FreeBSD rc subsystem uses= "su -m" when running processes as a specific user, not "su -l". The "su -l= " would fail because ElasticSearch's user has a default shell of /sbin/nolo= gin. As far as I can tell this is normal behavior. If you need to change env for Elastic you can use the elasticsearch_env=3D"= " in /etc/rc.conf. Any further questions about overcoming issues in your en= vironment are welcome. We also have a list for elastic now called "freebsd-= elastic@FreeBSD.org".=20 Hope that helps, --=20 Mark Felder ports-secteam & portmgr member feld@FreeBSD.org