-
Notifications
You must be signed in to change notification settings - Fork 136
CryptoStream error when using Node 0.12 #48
Comments
Hi Edoardo, The core is not breathing cyan and not connecting to the cloud. Do you think even after reverting the node.js there is some elese broken ? Please let me know if you have any idea. Thanks, |
@satendra4u , i highly recommend that you setup again using a clean installation and verify if the issue exists. |
@kennethlimcp, I re-ran through spark-server setup again (Mac OSX Yosemite 10.10.4) and am getting this: Followed guide for installing spark-server (master branch) $ git clone https://github.com/spark/spark-server.git $ cd spark-server
CXX(target) Release/obj.target/ursaNative/src/ursaNative.o node-oauth2-server@1.5.3 node_modules/node-oauth2-server when@3.7.3 node_modules/when moment@2.10.6 node_modules/moment hogan-express@0.5.2 node_modules/hogan-express spark-protocol@0.1.5 node_modules/spark-protocol express@3.4.8 node_modules/express ursa@0.8.5 node_modules/ursa request@2.60.0 node_modules/request spark-server $ node -v spark-server $ nvm install 0.10.36 spark-server $ node -v spark-server $ node main.jsNo users exist, you should create some users!connect.multipart() will be removed in connect 3.0 dyld: Symbol not found: _node_module_register Trace/BPT trap: 5 spark-server $ If I switch to node 0.12.7 I get the same output as @endorama when i run node main.js |
It sounds like a problem building the "ursa" module, which depends on OpenSSL being installed. Can you run:
|
spark-server $ openssl version |
Hmm, this might be an issue with node modules that were partially installed, and then the version of node changed... Can you delete your "node_modules" folders, and try running |
That solved it! Thanks David! |
Awesome! |
events Controller / events Manager
Hello, I've found a misbehaviour when running the server using nodejs 0.12.
It throws a
CryptoStream
error which prevents my Core to properly complete handshake with the server.Here you can find the relevant forum post about the behaviour.
For future reference, I'm copying here the relevant part of the server log:
As a workaround you can use node 0.10.36 ( download it from here ) and everything should work properly.
The text was updated successfully, but these errors were encountered: