[Bug 227354] textproc/elasticsearch6 is fails to start because java PATH from env is not passed to it

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Apr 7 21:07:59 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227354

            Bug ID: 227354
           Summary: textproc/elasticsearch6 is fails to start because java
                    PATH from env is not passed to it
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://forums.freebsd.org/threads/textproc-elasticsea
                    rch6-does-not-honour-etc-profile.65338/
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: feld at FreeBSD.org
          Reporter: jamie.baxter at tutanota.com
          Assignee: feld at FreeBSD.org
             Flags: maintainer-feedback?(feld at FreeBSD.org)

Created attachment 192319
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=192319&action=edit
Diff file for additions to elasticsearch.in to set & export JAVA_HOME

When elasticsearch6 is started from the rc.subr system on a default
installation, it fails to initialize because the path for java
(JAVA_HOME=/usr/local/openjdk8) is not passed to it (adding the path to
/etc/profile does not work as rc does not import from profile).

JAVA_HOME can be added through an additional (but possibly less recognized)
rcvar  ${portname}_env="JAVA_HOME=/usr/local/openjdk8", but even fresh
installations would necessitate this call (there does not appear to be any
documentation to suggest this fix).

It might be instead better to declare JAVA_HOME in the rc script similar to
sysutils/logstash6 (which also depends on java/openjdk8 in a similar manner),
where an rcvar declares a default JAVA_HOME & exports the value.

See attached diff for files/elasticsearch6.in as an example.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list