URIError: Failed to decode param 'til-%EF%BD%81%EF%BD%82%EF%BD%8F%EF%BD%95%EF%BD%94-%EF%BD%94%EF%BD%88%EF%BD%85-%EF%BD%84%EF%BD%81%EF%BD%E2%80%99%EF%BD%8B-%EF%BD%81%EF%BD%E2%80%99%EF%BD%94%EF%BD%93-%EF%BD%8F%EF%BD%86-%EF%BD%88%EF%BD%94%EF%BD%8D%EF%BD%8C'

[pauljherring]

Upon restarting NodeBB - log at http://pastebin.com/8vm7FDcw

[BenLubar]

It's an IP in Thailand with this user agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36 OPR/26.0.1656.60

[BenLubar]

Something's causing NodeJS to hit 100% CPU usage and then not accept any requests. It's not this.

[boomzillawtf]

Do we need to engage the NodeBB devs?

[BenLubar]

@pauljherring if the forum stops accepting requests and hits 100% CPU usage on both node instances and I'm not awake, $ docker restart wtdwtf-nodebb

@boomzillawtf at this point, I have no idea what's causing the problem.

The URIError isn't actually causing any problems - it doesn't crash the instance and it's in the HTTP server library, so NodeBB can't and shouldn't do anything about it.

[boomzillawtf]

It's the "no idea" part that says maybe we need some help. If nothing else, maybe post something here:

https://community.nodebb.org/category/16/technical-support

...and see if anyone has any ideas.

[BenLubar]

https://community.nodebb.org/post/50432

[pauljherring]

Ok, that's the 100% reported.

Now about that URI....

[BenLubar]

@pauljherring it's just a stack trace, not a crash. Plus it happens completely inside the express library, so NodeBB can't catch it.

[pauljherring]

E_CANT_FIX then?

[BenLubar]

Yeah.