question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

node main.js never completes

See original GitHub issue

I’m struggling to get wekan running on my centos7 minimal installation. I’ve followed three guides and run into different errors with each. here are the steps I’m taking.

Fresh CentOS Linux release 7.0.1406 (Core) installation.

setenforce 0 (just for good measure) wget http://nodejs.org/dist/v0.10.40/node-v0.10.40-linux-x64.tar.gz tar --strip-components 1 -xzvf node-v* -C /usr/local node --version v0.10.40

git clone https://github.com/wekan/wekan.git cd wekan

vi /etc/yum.repos.d/mongodb.repo [mongodb] name=MongoDB Repository baseurl=http://downloads-distro.mongodb.org/repo/redhat/os/x86_64/ gpgcheck=0 enabled=1

yum install mongodb-org -y systemctl start mongod

curl https://install.meteor.com/ | sh meteor build …/wekan-build --directory # the output from this command is toEnd: wrong arguments-i18n-compiler` fr… /
to: wrong arguments

cd …/wekan-build/bundle/programs/server/ npm install #output below npm WARN package.json meteor-dev-bundle@0.0.0 No description npm WARN package.json meteor-dev-bundle@0.0.0 No repository field. npm WARN package.json meteor-dev-bundle@0.0.0 No README data

fibers@1.0.5 install /root/wekan-build/bundle/programs/server/node_modules/fibers node ./build.js linux-x64-v8-3.14 exists; testing Binary is fine; exiting ansi-regex@0.2.1 node_modules/ansi-regex ansi-styles@1.1.0 node_modules/ansi-styles escape-string-regexp@1.0.3 node_modules/escape-string-regexp chalk@0.5.1 node_modules/chalk has-ansi@0.1.0 node_modules/has-ansi strip-ansi@0.3.0 node_modules/strip-ansi supports-color@0.2.0 node_modules/supports-color eachline@2.3.3 node_modules/eachline type-of@2.0.1 node_modules/type-of amdefine@1.0.0 node_modules/amdefine asap@2.0.3 node_modules/asap meteor-promise@0.4.6 node_modules/meteor-promise underscore@1.5.2 node_modules/underscore promise@7.0.4 node_modules/promise source-map-support@0.3.2 node_modules/source-map-support semver@4.1.0 node_modules/semver source-map@0.1.32 node_modules/source-map fibers@1.0.5 node_modules/fibers

export MONGO_URL=‘mongodb://127.0.0.1:27017/libreboard’ export ROOT_URL=‘https://example.com’ export MAIL_URL=‘smtp://user:pass@mailserver.example.com:25/’ export PORT=8080

cd …/…/

node main.js #output below [root@libreboard bundle]# node main.js Meteor._wrapAsync has been renamed to Meteor.wrapAsync

Starting board-background-color migration. Finishing board-background-color migration. Starting lowercase-board-permission migration. Finishing lowercase-board-permission migration. Starting change-attachments-type-for-non-images migration. Finishing change-attachments-type-for-non-images migration. Starting card-covers migration. Finishing card-covers migration. Starting use-css-class-for-boards-colors migration. Finishing use-css-class-for-boards-colors migration. Starting denormalize-star-number-per-board migration. Finishing denormalize-star-number-per-board migration. Starting add-member-isactive-field migration. Finishing add-member-isactive-field migration.

and my server never passes this point?? any suggestions?

Thanks

Michael

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:13 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
ePiratcommented, Sep 2, 2015

I’ve just checked, it seems on latest meteor version, the weird

toEnd: wrong arguments-i18n-compiler` fr...

to: wrong arguments

is normal, it happens for me as well but still the final build works fine. Note that it is expected that output stops and the app will not exit, as it’s supposed to be run by a watchdog/service like systemd. So just try to connect, if it works you just have to use your prefered service manager to run it in the background or use the simple

node main.js &
echo $! > ./pid.txt

approach.

0reactions
mhorne484commented, Sep 3, 2015

sure can! thanks all

Read more comments on GitHub >

github_iconTop Results From Across the Web

strange npm problem, command never finishes, hangs forever
Node itself is installed nodejs/node_modules/npm. ... The main reason I started this odyssey is I wanted global modules in ONE location.
Read more >
Nodejs does not wait for promise resolution - exits instead
If I am not mistaken, Node.js does not wait for ever-pending Promises: 'use strict'; (async function main() { await new Promise((resolve) ...
Read more >
Don't Block the Event Loop (or the Worker Pool) - Node.js
You should make sure you never block the Event Loop. In other words, each of your JavaScript callbacks should complete quickly. This of...
Read more >
Top 10 Most Common Node.js Developer Mistakes - Toptal
Often, reasons for such criticisms are rooted in how developers use/misuse the language. This article explores ten common mistakes that Node.js developers ...
Read more >
NodeJS - The Complete Guide (MVC, REST APIs, GraphQL ...
Master Node JS & Deno.js, build REST APIs with Node.js, GraphQL APIs, add Authentication, use MongoDB, SQL & much more!
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found