Hello Miroslav, I have run into the same issue recently. There is a ticket for this problem:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220467 The reporter of the ticket proposes to adjust the kibana dependencies to point to node6 which doesn't have the bug. Would maybe a good idea to stick to the stable 6 versions, as long as kibana doesn't neccessarily need a need a newer one. At least from the source code side, version 6 seems to be fine: https://github.com/elastic/kibana/blob/master/.node-version Best regards, Matthias Am Mittwoch, den 19.07.2017, 01:36 +0200 schrieb Miroslav Lachman: > I upgraded ports on our test server, it includes upgrade of node > from > 7.10.0 to 8.1.4 but Kibana failed to start with the following stack > trace > > (node:13668) [DEP0022] DeprecationWarning: os.tmpDir() is > deprecated. > Use os.tmpdir() instead. > /usr/local/bin/node[13668]: ../src/env-inl.h:131:void > node::Environment::AsyncHooks::push_ids(double, double): Assertion > `(trigger_id) >= (0)' failed. > 1: node::Abort(void) [/usr/local/bin/node] > 2: node::Assert(char const* const[4]*) [/usr/local/bin/node] > 3: > node::AsyncWrap::PushAsyncIds(v8::FunctionCallbackInfo<node::AsyncWra > p::PushAsyncIds::Value> > const&) [/usr/local/bin/node] > 4: > v8::internal::FunctionCallbackArguments::Call(void(*)(v8::FunctionCal > lbackInfo<v8::Value> > const&)) [/usr/local/bin/node] > 5: v8::internal::Isolate*<v8::internal::Object> > v8::internal::Builtins::InvokeApiFunction(v8::internal::Isolate*, > bool, > v8::internal::Handle<v8::internal::HeapObject>(int, > v8::internal::Object*, v8::internal::HeapObject) > [/usr/local/bin/node] > 6: v8::internal::Builtin_HandleApiCall(int, > v8::internal::Object**, > v8::internal::Isolate*) [/usr/local/bin/node] > Abort (core dumped) > > I found similar issue on GitHub https://github.com/nodejs/node/issues > /14198 > > Is it possible to add the fox from nightly version to port www/node? > Otherwise Kibana cannot run. > > Kind regards > Miroslav Lachman > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.o > rg" _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
