Don't know why but we get this!
He has åäö in his name, and using Google SSO to login!
Something we can troubleshoot!
That's odd. Did
./nodebb build complete without errors?
As 1.6.1 did not require any upgrade scripts, you can simply
git reset --hard v1.6.0 to go back to v1.6.0 and be up and running again (assuming you were on v1.6.0 before).
In the future, we'd advise you to use a staging instance to test upgrades on before doing it on live instances.
I was able to successfully rollback to 1.6.0 however I'd still like to upgrade to 1.6.1 as soon as possible. Now that I'm all rolled back, what steps do you recommend I take to upgrade?
I would make a copy of your database, and set up another installation of NodeBB for testing purposes... I've never seen an issue with NodeBB just refusing to start like that, so I don't know where to begin debugging.
@julian Staging server will be ready in 10 minutes. In SSH now I just need a few minutes to setup.
@julian Sorry about the delays, file transfers took a bit longer than expected. I have a staging server setup at https://staging.sinfulforums.net/login/2fa, if you'd like I can send you SSH Credentials to Staging. I'm fixing a few things regarding plugins. It still has certain plugins deactivated breaking login so I'm working on a fix for that then we can start working on an upgrade tactic.
@nsuchy We could use that as part of the test... if you disable all plugins except the bundled ones, does it upgrade to v1.6.1 without issues
@julian Ok on staging I ran nodebb reset -p to deactivate all plugins, I ran th commands to upgrade, and now nodebb is running at 100% CPU on the staging server.
root@NodeBB-Staging:/var/www/html/NodeBB# curl -I http://127.0.0.1:4567 curl: (7) Failed to connect to 127.0.0.1 port 4567: Connection refused root@NodeBB-Staging:/var/www/html/NodeBB# ./nodebb log Hit Ctrl-C to exit This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For the full license, please visit: http://www.gnu.org/copyleft/gpl.html Clustering enabled: Spinning up 1 process(es). 16/10 15:17:25  - info: Initializing NodeBB v1.6.1 https://staging.sinfulforums.net:443 16/10 15:17:25  - warn: You have no mongo username/password setup! 16/10 15:17:28  - info: [socket.io] Restricting access to origin: *:* 16/10 15:17:28  - info: Routes added
CPU and RAM at 100% utilization by the way.
For all those wondering... @nsuchy had a really large (i.e. 2mb+ of pure text) blacklist.
... don't make your blacklist that large
@shard I probably have the world's most unique edgecase
Sidenote for huge IP Ban Lists run the following bash script:
for i in `cat ./list.txt`; do echo 'deny' $i';' >> denyips.conf; done
list.txt being a list of IP addresses/ranges one IP / Range per line, denyips.conf being the file you give to the nginx proxy.
root@vps146875:/etc/nginx# wc -l ./denyips.conf 158740 ./denyips.conf
it took like a second to do it's thing very fast for so many lines.
Would that not better handled by your reverse proxy, software, or hardware firewall?
I've got the same problem a while ago. Deactivating the broken plug-ins isn't enough: you have to uninstall (
npm un <package-name>) the right one from your installation.
They usually show up in the logs from template building (
node nodebb build) as errors or warns and in the dev console (
node nodebb dev) as errors.