@g0st docker exec -ti [mongo container name] mongo

I have this in my crontab:

42 * * * * cd /home/ben/.nodebb-docker.git && git fetch -p origin > /dev/null 2> /dev/null && git push --mirror > /dev/null 2> /dev/null

You can download the docker image from my repo: https://hub.docker.com/r/benlubar/nodebb/

I documented the commands needed to set up the forum for my community here, but most of them should be pretty easy to adapt for any other community. Ignore the stuff about postgres unless you're importing from a forum that used postgres.

@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

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.

On what.thedailywtf.com, we've been having trouble with the NodeJS instances stopping handling requests and running at near 100% CPU usage until they are restarted. We run MongoDB for the main database, Redis for clustering support, and 2 NodeBB clustered instances (down from 4 due to this problem).

At this point, I have no idea what could be causing the problem, other than that it started about a week ago. Is there some way to get a stack trace from a running NodeJS instance?

There's no log output during the time the problem occurs. servercooties.com tracks our instance's uptime, so @accalia can probably pinpoint the times when the problem occurred.

/cc @boomzilla @PJH

Commenting out the fast path (these three lines) seems to be working so far (although extremely slowly).

My instance would previously get killed at around 15% (there were a lot of posts from two forum softwares ago when pasting files into a forum wasn't a thing), but now it's at 90%. It's been about 4 hours since I started this attempt.

Here's our emoji pack for FontAwesome (yes, it's just the json file):

https://github.com/boomzillawtf/tdwtf/blob/master/emoji/fontawesome.json

@JJSagan said in Postgresql Integration:

my_cool_db

@JJSagan said in Postgresql Integration:

MY_NEW_DATABASE

Are these the same database or a different one?

@JJSagan said in Postgresql Integration:

1. Run ./nodebb setup.

You shouldn't need to do this step.

@jjsagan said in Postgresql Integration:

Hi @julian,
First allow me to thank you and the team for all the improvements made recently with 1.10+. As always you guys are amazing!
Is there any chance to see @Ben-Lubar 's postgresql pull request integrated soon?
Thank you!
JJ.

We are currently running the PR on https://what.thedailywtf.com/, and it's working without any new problems.

Commenting out the fast path (these three lines) seems to be working so far (although extremely slowly).

My instance would previously get killed at around 15% (there were a lot of posts from two forum softwares ago when pasting files into a forum wasn't a thing), but now it's at 90%. It's been about 4 hours since I started this attempt.

@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.