Kibana/Elasticsearch fail

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Kibana/Elasticsearch fail

Eric Zylstra
I’ve installed the ELK packages (Elasticsearch, Logstash, Kibana) using pkg_add.  Installs went fine.  I checked out the pkg documentation (pkg_reames) and followed the steps for those that had documentation to follow.

When I boot, Logstash and Kibana fail.  I can use rcctl to start Logstash with no problem.  When I try to start Kibana, the following is what I see:

# rcctl -d start kibana
doing _rc_parse_conf
doing _rc_quirks
kibana_flags empty, using default ><
doing _rc_parse_conf /var/run/rc.d/kibana
doing _rc_quirks
doing rc_check
kibana
doing rc_start
doing _rc_wait start
doing rc_check
No home directory /nonexistent!
Logging in with home = "/".
Kibana does not support the current Node.js version v10.16.3. Please use Node.js v>=10.15.0 <10.16.
doing _rc_rm_runfile
(failed)


I’m not sure what to do with this.  Why is Logstash not starting on reboot?  Why does Kibana fail?  I assume there is some config that need be done, because that Node.js error wouldn’t have made it to distribution, right?

Thanks,

EZ
Reply | Threaded
Open this post in threaded view
|

Re: Kibana/Elasticsearch fail

Aaron Bieber-2
On Thu, 06 Feb 2020 at 23:31:01 -0600, Eric Zylstra wrote:

> I’ve installed the ELK packages (Elasticsearch, Logstash, Kibana) using pkg_add.  Installs went fine.  I checked out the pkg documentation (pkg_reames) and followed the steps for those that had documentation to follow.
>
> When I boot, Logstash and Kibana fail.  I can use rcctl to start Logstash with no problem.  When I try to start Kibana, the following is what I see:
>
> # rcctl -d start kibana
> doing _rc_parse_conf
> doing _rc_quirks
> kibana_flags empty, using default ><
> doing _rc_parse_conf /var/run/rc.d/kibana
> doing _rc_quirks
> doing rc_check
> kibana
> doing rc_start
> doing _rc_wait start
> doing rc_check
> No home directory /nonexistent!
> Logging in with home = "/".
> Kibana does not support the current Node.js version v10.16.3. Please use Node.js v>=10.15.0 <10.16.
> doing _rc_rm_runfile
> (failed)
>
>
> I’m not sure what to do with this.  Why is Logstash not starting on reboot?  Why does Kibana fail?  I assume there is some config that need be done, because that Node.js error wouldn’t have made it to distribution, right?

> that Node.js error wouldn’t have made it to distribution

It did, and it's entirely my fault.

Kibana is failing because it is very strict about the version of node it wants
to use (hence the "Kibana does not support.." message).

Apparently the tests I had run to verify this update worked failed:
http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/kibana/patches/patch-package_json?rev=1.4&content-type=text/x-cvsweb-markup

Here is a diff that fixes it for 6.6 (you will have to build it from ports
until (if?) a proper fix is in place).

https://deftly.net/patches/kibana-6.6.1.diff

Index: Makefile
===================================================================
RCS file: /cvs/ports/www/kibana/Makefile,v
retrieving revision 1.32
diff -u -p -r1.32 Makefile
--- Makefile 28 Sep 2019 09:37:54 -0000 1.32
+++ Makefile 11 Feb 2020 04:13:52 -0000
@@ -3,7 +3,7 @@
 COMMENT= browser based analytics/search interface to ElasticSearch
 
 V = 6.6.1
-REVISION = 1
+REVISION = 2
 PKGNAME = kibana-${V}
 DISTNAME = kibana-oss-${V}-darwin-x86_64
 
Index: patches/patch-package_json
===================================================================
RCS file: /cvs/ports/www/kibana/patches/patch-package_json,v
retrieving revision 1.4
diff -u -p -r1.4 patch-package_json
--- patches/patch-package_json 13 May 2019 22:08:11 -0000 1.4
+++ patches/patch-package_json 11 Feb 2020 04:13:52 -0000
@@ -8,7 +8,7 @@ Index: package.json
    },
    "engines": {
 -    "node": "10.15.1"
-+    "node": ">=10.15.0 <10.16"
++    "node": "10.16.3"
    }
 -}
 \ No newline at end of file

>
> Thanks,
>
> EZ

--
PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A  4AF0 1F81 112D 62A9 ADCE

Reply | Threaded
Open this post in threaded view
|

Re: Kibana/Elasticsearch fail

Eric Zylstra
You rock!  I’ll let you know it works for me when I get a chance.

EZ


Sent from my iPhone

> On Feb 10, 2020, at 11:19 PM, Aaron Bieber <[hidden email]> wrote:
>
> On Thu, 06 Feb 2020 at 23:31:01 -0600, Eric Zylstra wrote:
>> I’ve installed the ELK packages (Elasticsearch, Logstash, Kibana) using pkg_add.  Installs went fine.  I checked out the pkg documentation (pkg_reames) and followed the steps for those that had documentation to follow.
>>
>> When I boot, Logstash and Kibana fail.  I can use rcctl to start Logstash with no problem.  When I try to start Kibana, the following is what I see:
>>
>> # rcctl -d start kibana
>> doing _rc_parse_conf
>> doing _rc_quirks
>> kibana_flags empty, using default ><
>> doing _rc_parse_conf /var/run/rc.d/kibana
>> doing _rc_quirks
>> doing rc_check
>> kibana
>> doing rc_start
>> doing _rc_wait start
>> doing rc_check
>> No home directory /nonexistent!
>> Logging in with home = "/".
>> Kibana does not support the current Node.js version v10.16.3. Please use Node.js v>=10.15.0 <10.16.
>> doing _rc_rm_runfile
>> (failed)
>>
>>
>> I’m not sure what to do with this.  Why is Logstash not starting on reboot?  Why does Kibana fail?  I assume there is some config that need be done, because that Node.js error wouldn’t have made it to distribution, right?
>
>> that Node.js error wouldn’t have made it to distribution
>
> It did, and it's entirely my fault.
>
> Kibana is failing because it is very strict about the version of node it wants
> to use (hence the "Kibana does not support.." message).
>
> Apparently the tests I had run to verify this update worked failed:
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/kibana/patches/patch-package_json?rev=1.4&content-type=text/x-cvsweb-markup
>
> Here is a diff that fixes it for 6.6 (you will have to build it from ports
> until (if?) a proper fix is in place).
>
> https://deftly.net/patches/kibana-6.6.1.diff
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/www/kibana/Makefile,v
> retrieving revision 1.32
> diff -u -p -r1.32 Makefile
> --- Makefile    28 Sep 2019 09:37:54 -0000    1.32
> +++ Makefile    11 Feb 2020 04:13:52 -0000
> @@ -3,7 +3,7 @@
> COMMENT=    browser based analytics/search interface to ElasticSearch
>
> V =        6.6.1
> -REVISION =    1
> +REVISION =    2
> PKGNAME =    kibana-${V}
> DISTNAME =    kibana-oss-${V}-darwin-x86_64
>
> Index: patches/patch-package_json
> ===================================================================
> RCS file: /cvs/ports/www/kibana/patches/patch-package_json,v
> retrieving revision 1.4
> diff -u -p -r1.4 patch-package_json
> --- patches/patch-package_json    13 May 2019 22:08:11 -0000    1.4
> +++ patches/patch-package_json    11 Feb 2020 04:13:52 -0000
> @@ -8,7 +8,7 @@ Index: package.json
>    },
>    "engines": {
> -    "node": "10.15.1"
> -+    "node": ">=10.15.0 <10.16"
> ++    "node": "10.16.3"
>    }
> -}
> \ No newline at end of file
>
>>
>> Thanks,
>>
>> EZ
>
> --
> PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A  4AF0 1F81 112D 62A9 ADCE

Reply | Threaded
Open this post in threaded view
|

Re: Kibana/Elasticsearch fail

David Higgs
In reply to this post by Aaron Bieber-2
On Mon, Feb 10, 2020 at 11:20 PM Aaron Bieber <[hidden email]> wrote:

> On Thu, 06 Feb 2020 at 23:31:01 -0600, Eric Zylstra wrote:
> > I’ve installed the ELK packages (Elasticsearch, Logstash, Kibana) using
> pkg_add.  Installs went fine.  I checked out the pkg documentation
> (pkg_reames) and followed the steps for those that had documentation to
> follow.
> >
> > When I boot, Logstash and Kibana fail.  I can use rcctl to start
> Logstash with no problem.  When I try to start Kibana, the following is
> what I see:
> >
> > # rcctl -d start kibana
> > doing _rc_parse_conf
> > doing _rc_quirks
> > kibana_flags empty, using default ><
> > doing _rc_parse_conf /var/run/rc.d/kibana
> > doing _rc_quirks
> > doing rc_check
> > kibana
> > doing rc_start
> > doing _rc_wait start
> > doing rc_check
> > No home directory /nonexistent!
> > Logging in with home = "/".
> > Kibana does not support the current Node.js version v10.16.3. Please use
> Node.js v>=10.15.0 <10.16.
> > doing _rc_rm_runfile
> > (failed)
> >
> >
> > I’m not sure what to do with this.  Why is Logstash not starting on
> reboot?  Why does Kibana fail?  I assume there is some config that need be
> done, because that Node.js error wouldn’t have made it to distribution,
> right?
>
> > that Node.js error wouldn’t have made it to distribution
>
> It did, and it's entirely my fault.
>
> Kibana is failing because it is very strict about the version of node it
> wants
> to use (hence the "Kibana does not support.." message).
>
> Apparently the tests I had run to verify this update worked failed:
>
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/kibana/patches/patch-package_json?rev=1.4&content-type=text/x-cvsweb-markup
>
> Here is a diff that fixes it for 6.6 (you will have to build it from ports
> until (if?) a proper fix is in place).
>
> https://deftly.net/patches/kibana-6.6.1.diff
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/www/kibana/Makefile,v
> retrieving revision 1.32
> diff -u -p -r1.32 Makefile
> --- Makefile    28 Sep 2019 09:37:54 -0000      1.32
> +++ Makefile    11 Feb 2020 04:13:52 -0000
> @@ -3,7 +3,7 @@
>  COMMENT=       browser based analytics/search interface to ElasticSearch
>
>  V =            6.6.1
> -REVISION =     1
> +REVISION =     2
>  PKGNAME =      kibana-${V}
>  DISTNAME =     kibana-oss-${V}-darwin-x86_64
>
> Index: patches/patch-package_json
> ===================================================================
> RCS file: /cvs/ports/www/kibana/patches/patch-package_json,v
> retrieving revision 1.4
> diff -u -p -r1.4 patch-package_json
> --- patches/patch-package_json  13 May 2019 22:08:11 -0000      1.4
> +++ patches/patch-package_json  11 Feb 2020 04:13:52 -0000
> @@ -8,7 +8,7 @@ Index: package.json
>     },
>     "engines": {
>  -    "node": "10.15.1"
> -+    "node": ">=10.15.0 <10.16"
> ++    "node": "10.16.3"
>     }
>  -}
>  \ No newline at end of file
>
> >
> > Thanks,
> >
> > EZ
>
> --
> PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A  4AF0 1F81 112D 62A9
> ADCE
>
>
Works great for me, thanks for the belated update.

--david