@exodo @sloosecannon It's this:

https://github.com/boomzillawtf/tdwtf/blob/master/plugins/nodebb-plugin-tdwtf-customizations/index.js#L13
https://github.com/boomzillawtf/tdwtf/blob/master/watchdog.bash

Is anyone who is affected by this using the dbsearch plugin with a MongoDB database? I got rid of ours and the periodic hangs went away, at least for the last 24 hours.

@baris said in NodeBB periodically hangs:

Do you guys get this hanging issue daily?

We've been tracking the manual restarts here: https://what.thedailywtf.com/topic/19990/the-official-server-cooties-tracking-thread

Ok, time for an update. The iframely problem was definitely one of the causes, but we're still getting occasional lock-ups. Nowhere near as bad as before, but the site still goes down a few times a day. We have a topic where we track manual restarts, but the data doesn't really show any pattern other than that the infinite loop is happening during times when a lot of pages are loaded.

Okay, strace showed both instances hanging after this:

connect(85, {sa_family=AF_INET, sin_port=htons("[iframely port]"), sin_addr=inet_addr("[iframely IP]")}, 16) = -1 EINPROGRESS (Operation now in progress)

I've blacklisted the forum's hostname from iframely. We'll see if that fixes it.

@baris I was able to pause it and get a backtrace up until it actually encountered the hang, and then the debugger never finished whatever command I threw at it.

I'm stumped.

ok, I see that there is a way to get a stack trace from NodeJS, but it requires starting it with --debug-brk so a debugger can be attached (and then unpaused and allowed to run as normal until it hangs).

Should I edit loader.js for that, or is there some other way to start one of the instances of a cluster with an extra parameter?