darwin binaries will not run on freebsd/openbsd

[msimerson]

Summary

Both phantomjs and chromium include freebsd and openbsd as targets on which the Darwin builds can be deployed. This is nonsense as neither of those platforms can run Darwin binaries.

./bin/phantomjs: cannot execute binary file: Exec format error

The result of removing *bsd from the Darwin target is that now kibana will die with this error:

Unsupported platform: freebsd

instead of this error:

Failed to install browser. See kibana logs for more details.

That's much more accurate.

If adding support for FreeBSD and OpenBSD is desirable, the Right Way to do it is to depend on an OS supplied (via ports/packages) binary.

# file /usr/local/bin/phantomjs
/usr/local/bin/phantomjs: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.2, FreeBSD-style, stripped
# file /usr/local/bin/chrome
/usr/local/bin/chrome: POSIX shell script, ASCII text executable
# file /usr/local/share/chromium/chrome
/usr/local/share/chromium/chrome: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.2, FreeBSD-style, BuildID[sha1]=8504a6ceab82b1610b42d42b4efb93cb4105f46d, stripped

I have started looking into convincing the reporting module to use an installed binary. If I figure it out before running out of time, I'll create another PR.

Checklist

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[msimerson]

yes

[msimerson]

For anyone that really really wants the reporting module to work, I've found a workaround.

It takes advantage of this bug. The trick is to install phantomjs and point Kibana at the FreeBSD compatible binary.

hack

pkg install -y phantomjs
cd /usr/local/www/kibana6/node_modules/x-pack/plugins/reporting/.phantom
fetch https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-macosx.zip
mkdir -p phantomjs-2.1.1-macosx/bin
ln -s /usr/local/bin/phantomjs phantomjs-2.1.1-macosx/bin/phantomjs

enable reporting module in kibana.yml

xpack.reporting.enabled: true

restart Kibana

service kibana restart

[ltning]

Please do NOT "fix" this "bug" until support for system-provided phantomjs (as described by @msimerson) has been implemented. We are currently relying on this hack.

[elasticmachine]

Pinging @elastic/stack-monitoring

[joelgriffith]

Closing in favor of a follow up PR to fix this issue, potentially in the 8.0.0 major