Problem solved with version 3.
Frontend freeze on version later than v1.0.2
No, standard persona theme. The system just hangs. No logs no nothing. Running as root in docker. If its idle for a while it hangs.
I am using mongodb and its not DB related. I guess it something wrong with dependencies for tag v1.0.3. I can stop the service but nobody can connect. It just freezes. Maybe to new persona? No loggs or errors
Hard to troubleshoot this!
I guess this is a frontend issue that triggers on certain db structure!
Branch v1.x.x seams to work better, except nodebb-plugin-custom-pages (Downgrade to 0.2.4)
It had a crash fix in the git logs. Maybe thats why tag v.1.0.3 (without fix) it crashes
Nope, v1.x.x also crashes If I deactivate plugins are they gone from the process or can they still break things? Still troubleshooting .... seams to be something wrong with nodebb-plugin-custom-pages ....
If deactivated they don't get loaded at all. So they can't break anything.
Ok, good 2 know. I am going insane over this issue. All seams more stable in tag v1.0.2. I can stop the server when the webb is crashed.
I start it with this -> node loader.js --no-daemon --no-silent
The plugin I use: https://www.nodebb.se/topic/4/bra-plugin-att-känna-till (Something unstable here) ?
It can trigger in 5-30 mins so ite hell to find this issue ... Gahh...
Crash when all plugins are off wen > v1.0.2
Could be nodebb-theme-persona ??
.... Trying master now. Maybe that works
... Nope, master with no plugins and all disabled dont work. It could be docker or something in the DB. There must be a better way to troubleshoot this?
Any new system dependency for > v1.0.2 ??
Need help here! I am stuck!
If I connect to the same DB v1.0.2 works but not > v1.0.2. It dies random when you click in the menu om the site. (But you can still stop the server with nodebb stop without error) I get no errorlog what so ever! It just dies on me!
I have another DB with less data.(Both are small databases) that seams to work with >v1.0.2. I guess its something in the DB that triggers this.
How can I troubleshoot this?
- I need a tip about database structure checker for nodebb (My other db is still alive so something is wrong).
- More verbose debugging somehow
- Is it possible to clean the db somehow without loosing data?
@psychobunny what tools do you use to troubleshoot the system?
belstgut last edited by
did u run
Yes i did More good ideas?
Trying now with node debug app.js but still no output Iam am stuck with v1.0.2. Unable fix this.
Is it possible to remove every plugin-settings from the DB? Or some other type of cleanup !
charles last edited by charles
Not having problems with the version but this topic brings up a good thing to have. A clean import/export feature built in to nodbeb would be nice. I believe wp export cleanly without all the "crap" and then imports into completely new clean install.
I will need to wait for at fix for this, I am stuck at 1.0.2
i´m ok with 1.0.3, did u tried fresh install?
@Jenkler you can't expect a fix if the issue can't be identified.
I have troubleshooted for 4 days with no success. Dont know what todo. Clean install works. It somthing in the database that triggers this and I have no idea what todo next
I am now running with v1.0.2 and updated plugins and it works. But if I try to upgrade to >v1.0.2 the frontend crashes with NO error, Just hangs. The fronted just stops taking in connections and it works to stop and restart nodebb. The crash comes after a while. 5-60 mins
Maybe som plugin setting that fucks the db up!
Its not only one site. I have atleast 2> sitest that behaves this way.
Tried node debug and nodebb debug, no success. Its just not f***ng working
jarey last edited by
@Jenkler 1.0.3 seems ok to me, and if a clean install behaves ok, it seems something with the particular data or modifications of your install. That said its very rare that the process crahs without any log. Did you at least find when the crash happens in terms of front end actions you do that makes the crash happens?
I would delete all info of plugins and custom data of BBDD and go progressively adding info to the BBDD in order to identify if it is a problem generated by the data.