Yes, it does appear to just be a bug in the template display. When I go into the Admin group itself, it shows the normal members. Thanks.
scottalanmiller
Posts
-
New Users Default to Admin -
Version MismatchIn the logs I see this after an update: info: Initializing NodeBB v0.5.0-4
But the web interface still says: "You are running NodeBB v0.5.0-3.
A new version (v0.5.0-4) has been released. Consider upgrading your NodeBB."
-
New Users Default to AdminUpdate: If I remove "Admin" from the users manually, it comes right back.
-
New Users Default to AdminAt some point, I don't know when, every new user joining our community was marked as an admin. Don't know if they were always this way (after a certain point, they definitely were not originally like this) or if they converted after some point. But this is kind of an emergency situation. We have thousands of admins now!! What can we do to "remove all but one or two" quickly? And how do we stop it from happening with new users?
-
Chat Windows Not Refreshingyes, working here too. 2.6 was the trick. We have been pretty stable for a week now.
-
NodeBB Fails to Start - Logs Tell Nothing -
NodeBB Fails to Start - Logs Tell NothingFixed 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:
-
NodeBB Fails to Start - Logs Tell NothingHere 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 +++ -
NodeBB Fails to Start - Logs Tell NothingThe process just dies almost instantly. Nothing more happens. Other instances are running on the same database no problem.
-
NodeBB Fails to Start - Logs Tell NothingHere 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 -
Tags Show Topics.Tag.Score After 0.5.0-3 Update -
Chat Windows Not Refreshing@julian said:
Okay, so as it turns out, NodeBB is no longer compatible with MongoDB 2.4. Admins are now required to update to MongoDB v2.6.
AH ha, cool, thanks. Will try to get to that tonight. Ubuntu 14.04 is MongoDB 2.4, surprisingly.
-
Chat Windows Not Refreshing@julian said:
Not sure if this is related, but your instance seems to be attempting to load
waterdrop-low.wav
when sending a chat message even though the file should bewaterdrop-low.mp3
...Sounds ARE all blanked out. We don't use sounds on our site. But a lot of people have complained that they keep getting them and can't stop them.
-
Tags Show Topics.Tag.Score After 0.5.0-3 UpdateAfter the update, now we see this...
-
Chat Windows Not RefreshingUpdate done, still no working chat.
-
Chat Windows Not RefreshingLots of this in the logs...
info: [notifications.get] Could not retrieve nid null
-
Chat Windows Not RefreshingDoing the 0.5.0-3 update now, just in case that resolves anything.
-
Chat Windows Not RefreshingUsing.... Vimeo, Widget Essentials, Mentions, Imgur, Markdown, Solr, Spam Be Gone, YouTube, MailGun, ImgBed, and that is all.
-
Chat Windows Not RefreshingWe are on Ubuntu 14.04, if that helps.
-
Strange new users@julian said:
@scottalanmiller Are you utilising spam-be-gone now? (Have you been using it all along?)
We unofficially take abandoned plugins under the NodeBB umbrella... but don't want to set a precedent... otherwise that org is going to be a dumping ground for half-finished, broken NodeBB plugins
Not yet, looking to use it soon but don't want to add more plugins while chat and other features are broken.