Date: Sat, 06 Feb 2021 21:50:27 +0000 From: bugzilla-noreply@freebsd.org To: elastic@FreeBSD.org Subject: maintainer-feedback requested: [Bug 253314] textproc/kibana7: fix memleak and some port improvements Message-ID: <bug-253314-37421-lm0lCQpzMj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253314-37421@https.bugs.freebsd.org/bugzilla/> References: <bug-253314-37421@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-elastic (Nobod= y) <elastic@FreeBSD.org> for maintainer-feedback: Bug 253314: textproc/kibana7: fix memleak and some port improvements https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253314 --- Description --- There's a memleak in Kibana ( https://github.com/elastic/kibana/issues/9027= 4 ). I think it is involved by incorrect using parameters xpack.ml.enabled and xpack.reporting.enabled added by ports r484109. The options should be passing by config file or command line arguments, not= by environmental variables (as a Docker). I've passed the params by command line and memleak had fixed. Also I've added some improvements to the rc-script: - Added kibana_syslog_output_* options for writing daemon(8) stdout to sysl= og. - Moved pidfile from /var/run/kibana to /var/run directory. - Moved daemon(8) pidfile control from child (-p) to supervisor (-P). It is need for using -r/-R options (auto-restart after terminated, ex. after memo= ry exhausting). - Added environmental variables passing for FreeBSD 11.4 compatibility. - Added --max-http-header-size=3D65536 node option (Kibana using).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253314-37421-lm0lCQpzMj>