I updated the quickstart repo to remove nprogress
NodeBB Fails to Start - Logs Tell Nothing
-
Here is all that I get in the logs...
info: NodeBB v0.5.0-3 Copyright (C) 2013-2014 NodeBB Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info:
info: Time: Fri Aug 22 2014 04:44:37 GMT+0000 (UTC)
info: Initializing NodeBB v0.5.0-3
info: * using configuration stored in: /opt/redacted/config.json
info: * using mongo store at 127.0.0.1:27017
info: * using themes stored in: /opt/redacted/node_modules -
The process just dies almost instantly. Nothing more happens. Other instances are running on the same database no problem.
-
Here is the strace of it...
access("/bin/mv", R_OK) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [],= 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [INT CHLD],= 0
rt_sigprocmask(SIG_SETMASK, [INT CHLD], NULL,= 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f068f8e5a10) = 5905
rt_sigprocmask(SIG_SETMASK, [], NULL,= 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [],= 0
rt_sigprocmask(SIG_SETMASK, [], NULL,= 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [],= 0
rt_sigaction(SIGINT, {0x443620, [], SA_RESTORER, 0x7f068ef14000}, {SIG_DFL, [], SA_RESTORER, 0x7f068ef14000},= 0
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 5905
rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x7f068ef14000}, {0x443620, [], SA_RESTORER, 0x7f068ef14000},= 0
rt_sigprocmask(SIG_SETMASK, [], NULL,= 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5905, si_status=0, si_utime=0, si_stime=0} ---
wait4(-1, 0x7fff0a51d258, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn() = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [],= 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f068f8e5a10) = 5906
rt_sigprocmask(SIG_SETMASK, [], NULL,= 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [],= 0
rt_sigprocmask(SIG_SETMASK, [], NULL,= 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [],= 0
rt_sigaction(SIGINT, {0x443620, [], SA_RESTORER, 0x7f068ef14000}, {SIG_DFL, [], SA_RESTORER, 0x7f068ef14000},= 0
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 5906
rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x7f068ef14000}, {0x443620, [], SA_RESTORER, 0x7f068ef14000},= 0
rt_sigprocmask(SIG_SETMASK, [], NULL,= 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5906, si_status=0, si_utime=7, si_stime=1} ---
wait4(-1, 0x7fff0a51d458, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn() = 0
read(255, "", 3112) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [],= 0
rt_sigprocmask(SIG_SETMASK, [], NULL,= 0
exit_group(0) = ?
+++ exited with 0 +++ -
Fixed and very important to know.... if you upgrade from MongoDB 2.4 to 2.6, all of your NodeBB instances will keep working happily until the apps themselves restart. At which time they will fail to authenticate. The issue is, you need to recreate the user(s) under 2.6:
-
@scottalanmiller user for the database or the forum?
-
@scottalanmiller said:
Fixed and very important to know.... if you upgrade from MongoDB 2.4 to 2.6, all of your NodeBB instances will keep working happily until the apps themselves restart. At which time they will fail to authenticate. The issue is, you need to recreate the user(s) under 2.6:
Ooof, yes, I noticed that as well. I had to re-run the
db.createUser
command again. Good catch! -