root@monitor:/etc/rc.conf.d # pkg info | grep kibana
kibana7-7.13.4 Browser based analytics and search interface to ElasticSearch
root@monitor:/etc/rc.conf.d # cat /etc/rc.conf.d/kibana
root@monitor:/etc/rc.conf.d # service kibana start
root@monitor:/etc/rc.conf.d # date
Wed Aug 4 17:16:13 CEST 2021
root@monitor:/etc/rc.conf.d # grep kiba /var/log/messages | tail -1
Aug 4 17:16:11 monitor kibana: Kibana does not support the current Node.js version v14.17.0. Please use Node.js >= v14.17.2.
root@monitor:/etc/rc.conf.d # service kibana status
kibana is not running.
root@monitor:/etc/rc.conf.d # pkg info | grep node | grep 14.17
Thank you for the report, this is not directly related to kibana, but more to www/node14 and www/npm-node14. Those two ports needs to be updated.
(In reply to Juraj Lutter from comment #1)
Thanks for your answer.
The defined dependencies in the kibana7 port currently don't specify v14.17.2 :
root@monitor:~ # grep www/ /usr/ports/textproc/kibana7/Makefile | grep node
BUILD_DEPENDS= node14>=14.17.0:www/node14 \
So the port will install, though node 14.17.2 is needed.
After update of www/kibana7 to 7.14.0, even node.je 14.17.3 is needed.
review D31433 has been opened for www/node14 maintainer.
Can this port be reverted to a working version? Really it should not be upgraded without a basic 'does it run' test.
We are working hard to get the update to node17.14.5 committed.
Fair enough. But could we get this port reverted so that people could use it in the meantime?