This is pretty hacky but it's worked beautifully so far: I wrote a Ruby script that tries to load my page. If it fails, it restarts the server. This is run in a cron job every minute. Here's my code:

require 'net/http'

begin
	print "Downloading the page..."
	res = Net::HTTP.start("yourdomainhere.com", :read_timeout => 5)
	res.get('/')
	puts " success!"
rescue Net::ReadTimeout => e
	print " failed.\n\nRestarting the server..."
	`./nodebb restart`

	puts " success!"
end

Until the cause of this is figured out, this or something like it might be a good enough workaround. It sure beats me manually restarting it after my users throw a fit.

@julian I'll certainly give it a shot in my spare time--probably tomorrow night, during one of the usergroup meetings I attent. I'm a Rails guy for a living and I'm just kind of hacking my way through NodeJS land, and more specifically NodeBB.

I think most of the work involved will revolve around reproducing the error, since calls to translator without a param sent along the way so plainly work all over the rest of the software. Will be doing some research!

@L33t I set up a cron job so that it wouldn't be subject to the server resetting. I wanted it to be somewhat resilient in spite of its hackiness.

That said, this is just treating a symptom. I absolutely do not advocate for this approach on a permanent basis, only until the true cause has been revealed and addressed. It's the software engineers' equivalent of filling a hole in a dam with a big wad of gum. It buys you time. It doesn't solve the real issue.

@julian I've made a pull request that creates a test and actually addresses the underlying problem on top of it! https://github.com/NodeBB/NodeBB/pull/4796

If there's something messed up about it feel free to tell me. Like I said, I'm new to the NodeJS world so I wouldn't be surprised if I did something incorrectly.

TheStranjer created this issue in NodeBB/NodeBB

closed Sanitize posts before plugin filters, not afterward #4796

@julian I'll certainly give it a shot in my spare time--probably tomorrow night, during one of the usergroup meetings I attent. I'm a Rails guy for a living and I'm just kind of hacking my way through NodeJS land, and more specifically NodeBB.

I think most of the work involved will revolve around reproducing the error, since calls to translator without a param sent along the way so plainly work all over the rest of the software. Will be doing some research!

@julian I hacked it to work with this commit: https://github.com/LukeLaupheimer/nodebb-plugin-nwod-roller/commit/c54dbbe4182f2bc6ac6c1007e4f717827a4c7414

But something tells me that this is not the ideal approach, like, at all. File this under things that work, but shouldn't need to be done.

0 TheStranjer committed to LukeLaupheimer/nodebb-plugin-nwod-roller

Hacky solution to the rendering problem

@julian Unfortunately, I do not. There are no errors showing. What I get is just the raw text of the partial: [[nwodroll:no-rerolls]].In the code, I figured surrounding the No Rerolls method in parentheses might impact it, but it didn't.

I also tried using the translator object server-side and that worked beautifully! So there's clearly something wrong with my partials that I can't quite identify.

@L33t I set up a cron job so that it wouldn't be subject to the server resetting. I wanted it to be somewhat resilient in spite of its hackiness.

That said, this is just treating a symptom. I absolutely do not advocate for this approach on a permanent basis, only until the true cause has been revealed and addressed. It's the software engineers' equivalent of filling a hole in a dam with a big wad of gum. It buys you time. It doesn't solve the real issue.

In the template file I'm writing, I can use the internationalization function for entries that take a parameter (like %1 or %2). Example: [[nwodroll:again, {again}]] works just fine, but [[nwodroll:no_rerolls]] does not. I see examples of the latter all over the core NodeBB code, and the core NodeBB code actually works. So from that, I know I'm doing something wrong that causes this, but for the life of me I can't figure it out.

Here's the repository: https://github.com/LukeLaupheimer/nodebb-plugin-nwod-roller

Any ideas?

This is pretty hacky but it's worked beautifully so far: I wrote a Ruby script that tries to load my page. If it fails, it restarts the server. This is run in a cron job every minute. Here's my code:

require 'net/http'

begin
	print "Downloading the page..."
	res = Net::HTTP.start("yourdomainhere.com", :read_timeout => 5)
	res.get('/')
	puts " success!"
rescue Net::ReadTimeout => e
	print " failed.\n\nRestarting the server..."
	`./nodebb restart`

	puts " success!"
end

Until the cause of this is figured out, this or something like it might be a good enough workaround. It sure beats me manually restarting it after my users throw a fit.

NodeBB periodically hangs every few hours, requiring me to restart the server. No error messages are listed in the NodeBB log or the MongoDB log. I can't reproduce the error.

What causes this? Is there a tool one can use to detect this and automatically restart the server?

Hi guys, the NodeBB installation I have keeps crashing periodically. When it does it throws this error:

5/6 18:47 [310] - error: /sitemap/pages.xml
 undefined