Closed pauljherring closed 8 years ago
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
Something's causing NodeJS to hit 100% CPU usage and then not accept any requests. It's not this.
Do we need to engage the NodeBB devs?
@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.
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.
Ok, that's the 100% reported.
Now about that URI....
@pauljherring it's just a stack trace, not a crash. Plus it happens completely inside the express
library, so NodeBB can't catch it.
E_CANT_FIX
then?
Yeah.
Upon restarting NodeBB - log at http://pastebin.com/8vm7FDcw