FS#67415 - [kibana] is incompatible with current nodejs package

Attached to Project: Community Packages
Opened by Antoine P (Stargateur) - Monday, 27 July 2020, 13:03 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 December 2022, 02:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

kibana depends on nodejs but it seem nodejs is too much up to date for kibana.

See detail here https://stackoverflow.com/questions/62742307/unable-to-start-kibana
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 04 December 2022, 02:54 GMT
Reason for closing:  None
Additional comments about closing:  Was dropped to the AUR 2022-01-08
Comment by Hayden Parker (hkparker) - Saturday, 22 August 2020, 23:37 GMT
I'm impacted by this as well, installing nodejs-lts-erbium over nodejs worked, though I doubt this is a long term solution.
Comment by Hayden Parker (hkparker) - Saturday, 10 October 2020, 21:36 GMT
correction: nodejs-lts-dubnium. However now kibana complains that it requires 10.22.0 and nodejs-lts-dubnium is on 10.22.1-1, so it requires a downgrade to keep kibana working in Arch.
Comment by Antoine P (Stargateur) - Tuesday, 24 November 2020, 18:02 GMT
since 7.9 https://github.com/elastic/kibana/blob/v7.9.0/.node-version should be ok with dubnium (there is now a 7.10). @anthraxx

nevermind dubnium is already at 10.23, I don't get why kibana refuse biger minor version, open a bug report in kibana github https://github.com/elastic/kibana/issues/84266

look like the 8.0 https://github.com/elastic/kibana/blob/master/.node-version will update to erbium.
Comment by Antoine P (Stargateur) - Wednesday, 25 November 2020, 09:56 GMT
that exactly why I don't like work with elk stack https://github.com/elastic/kibana/pull/19154 I have no word.

ugly fix: edit /usr/share/kibana/package.json and change the end

"engines": {
"node": "10.23.0"
}

I don't know if this is possible but I would create a patch simply remove the check and changing the node version by just adding >=
Comment by Olivier S. (obones) - Tuesday, 12 January 2021, 13:54 GMT
I have been struggling to get Kibana back to working and finally resorted to creating a "kibana-withnode" package.
Basically, it does two things:

1. Do not remove the "NodeJS" binaries that Kibana is providing in the source package
2. Use that binary to start the Kibana instance

With this I'm back on track, but I totally understand that this might not be desirable to no longer depend on the regular "nodejs" package

Loading...