High CPU usage from Node when wekan is running



Since the new update, every time I run node main.js and refresh the web page where weakn is on my machine’s CPU shots up to 98%, the output is as followed below:

[root@wekan_node_epel wekan]# node main.js
Note: you are using a pure-JavaScript implementation of bcrypt.
While this implementation will work correctly, it is known to be
approximately three times slower than the native implementation.
In order to use the native implementation instead, run

meteor npm install --save bcrypt

in the root directory of your application.
throw er; // Unhandled ‘error’ event

Error: listen EADDRINUSE
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at Server._listen2 (net.js:1258:14)
at listen (net.js:1294:10)
at net.js:1404:9
at _combinedTickCallback (internal/process/next_tick.js:83:11)
at process._tickCallback (internal/process/next_tick.js:104:9)

Any chance someone can explain what is happening? Could it be from updating wekan or a node problem?


Check Node.js etc versions that they are same as in Wekan repo Dockerfile.

100% CPU usage is problem for example with Node.js version 6.x


I have the same problem and use centOS 7 and Node 6.10.x LTS.

What version of nodejs is supported by wekan v0.28?
I dont use Docker.


Node 4.8.4


Damn, from the centOS repository i will only get Nodejs 6.x :frowning:
When your software supports newer nodejs Versions?


Wekan is made with Meteor.js framework that does not support Nodejs 6.x yet.

Wekan works with Docker on CentOS 7.


Okay, thanks for your information! You make really a great job with wekan!
Hope to chose the meteor framework is the right choise!



I’m 2nd maintainer of Wekan, using Meteor was not my choise.

Anyway, because of all functionality in Meteor etc, Wekan codebase is only about 7000 lines of code without frameworks, and code is quite logically organized, it makes maintaining and adding new features easier.