NodeBB v1.0.4-auto.229/5 02:45  - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised. 29/5 02:45  - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised. (node) warning: possible EventEmitter memory leak detected. 11 connect listeners added. Use emitter.setMaxListeners() to increase limit. 29/5 02:45  - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised. Trace at Socket.addListener (events.js:252:17) at Socket.Readable.on (_stream_readable.js:673:33) 29/5 02:45  - [32minfo[39m: [app] Database connection closed. 29/5 02:45  - [32minfo[39m: [app] Database connection closed. at Socket.once (events.js:278:8) 29/5 02:45  - [32minfo[39m: [app] Web server closed to connections. 29/5 02:45  - [32minfo[39m: [app] Web server closed to connections. at Socket.unref (net.js:1013:10) 29/5 02:45  - [32minfo[39m: [app] Shutdown complete. 29/5 02:45  - [32minfo[39m: [app] Shutdown complete. at Connection.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/connection.js:453:23) at /home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:189:7 at Array.forEach (native) at Pool.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:182:15) at Server.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/topologies/server.js:1072:31) at Server.close (/home/wing/nodebb/node_modules/mongodb/lib/server.js:417:17) 29/5 02:45  - [32minfo[39m: [app] Database connection closed. 29/5 02:45  - [32minfo[39m: [app] Web server closed to connections. 29/5 02:45  - [32minfo[39m: [app] Shutdown complete. [cluster] Child Process (774) has exited (code: 0, signal: null) [cluster] Child Process (779) has exited (code: 0, signal: null) [cluster] Child Process (782) has exited (code: 0, signal: null)
CPU utilization increased in 0.6.x
Ok, good to hear
Upgrade to 1.7 finished. I only had to disable the nodebb-plugin-topic-badges plugin as it resulted in crashes.
We got two search icons in the header now also. Is that "as designed"?
17/3 19:13  - error: TypeError: Object #<Object> has no method 'push' at Object.TopicBadges.addThreadTools [as method] (/usr/mysensors/mysensors-forum/NodeBB/node_modules/nodebb-plugin-topic-badges/library.js:27:15) at /usr/mysensors/mysensors-forum/NodeBB/src/plugins/hooks.js:89:12 at /usr/mysensors/mysensors-forum/NodeBB/node_modules/async/lib/async.js:272:13 at iterate (/usr/mysensors/mysensors-forum/NodeBB/node_modules/async/lib/async.js:149:13) at Object.async.eachSeries (/usr/mysensors/mysensors-forum/NodeBB/node_modules/async/lib/async.js:165:9) at Object.async.reduce (/usr/mysensors/mysensors-forum/NodeBB/node_modules/async/lib/async.js:271:15) at fireFilterHook (/usr/mysensors/mysensors-forum/NodeBB/src/plugins/hooks.js:81:9) at Plugins.fireHook (/usr/mysensors/mysensors-forum/NodeBB/src/plugins/hooks.js:66:5) at Object.threadTools (/usr/mysensors/mysensors-forum/NodeBB/node_modules/async/lib/async.js:656:23) at /usr/mysensors/mysensors-forum/NodeBB/node_modules/async/lib/async.js:583:25
You can disable the on on the left from ACP>navigation
Ohh.. sweet a new menu for handling top bar!
There is something wrong with category permissions! Many of your categories is hidden for registered users/guests (only admin=me) can see it. Tried re-saving but this seems to make it even more worse (they disappear one by one). Panic!
I have to enable old disabled categories to see them. Definitely a bug somewhere in the permission-on-categories part.
Reset password does dot work any more. You only get a "invalid reset code" popup.
File uploads does not quite work. They end up on server but they are not shown in posts. Only appear as:
![Screen Shot 2015-03-16 at 07.19.35.png](/uploads/files/1426625913085-Screen Shot 2015-03-16 at 07.19.35.png)
Which plugin is responsible for parsing image tags? What could be the issue.
I would say the filename with spaces "1426624191257-sensor shield rev 1.6 pcb.png " breaks the parsing.
Previously the files got names such as upload-2fd43287-38ca-4fb2-98c3-57120164d605.png
Panic:ing. Which component should I downgrade to get the old behaviour? marked?
Okay so Baris fixed the reset issue an hour or so ago, but I would not recommend updating to the latest master beyond that commit on a live forum
I hate to be the bearer of bad news but the other two issues are more oriented towards @baris and @julian who are AFK till the morning at worst. I hope you can cope (this is the reason why we don't recommend using a non-stable build)
Any chance of dropping back to latest stable (0.6x)? Do you have backups? Otherwise hang tight and we will try to resolve tomorrow?
I can live without reset for a few days. Or cherrypick 37fe438c63359e9ce25a307aea48c752f0ce7c2a.
But image upload is worse.
For the category permissions its a bug I encountered myself earlier so pinging @julian for that.
The fix was going though every single category and updating the privs, check everything (ex. Read/find for guests, read/find/post/reply for everyone else). Its a pain in the ass but this will fix that for you right now.
We need to write an upgrade script
Yes, have backups. But there will be post/user-losses going back.
The community just have to wait for tomorrow then.
Seems file upload works here but you send them away to imgur and the generated url looks "parsable" without any spaces.
@hek I'll make a couple issues on our tracker so its more visible. Welcome to the latest and greatest (and broken) master
Hehe.. guess you need kamikaze pilots helping to smoke out those bugs at some point.
Added some comments here:
Hi! Just took the leap to 0.6.x. A few thing I have noticed.
- First time sitemap.xml is accessed NodeBB crashes. Second time works fine.
- CPU usage went up ~10% on a 1GB digital ocean droplet.
- We get plenty of these in the log:
Error: invalid csrf token at verifytoken (/usr/mysensors/mysensors-forum/NodeBB/node_modules/csurf/index.js:237:11)
- Number of online users has dropped from ~250 to ~60. Has timeout times been changed?
Is 0.7.x out of the question for production use?
Feedback is appreciated.
Csrf could spell an out of date theme.
If you want stability, stick with stable. I use 0.7 on my live site. And it's used here. But, wouldn't recommend it.
What would i need to change on my theme to remove this csrf issue?
Is this your theme?
Delete the header.tpl (in fact, you might want to just delete any templates that you haven't specifically modified) - this will result in your theme inheriting the original template from vanilla, which will make upgrades easier.
Otherwise, replay the commits here https://github.com/NodeBB/nodebb-theme-vanilla/commits/master/templates/header.tpl until you are inline with your core revision