few things you may want to check. - are you running with default 1GB memory or increase to ~2GB? - default or production mode? - I usually run with this flag: node -nouse-idle-notification -expose-gc myHttpServer.js - does your server make any remote service call?
and what is the CPU / memory usage during the glitch? On Mon, Sep 24, 2012 at 4:54 PM, Hugo <[email protected]> wrote: > Confirmed :( I have been running almost 2 weeks with node 6.18 without a > glitch. With 0.8.9 I was seeing 2-3 issues per day at the minimum > > Unfortunately I don't have much of a diagnosis, I found out the issue > because I am monitoring the server with monit <http://mmonit.com> (it > tests the server with a basic http request that does nothing other than > acknowledging with a 200 code) > > For every failure, artifacts of the monit request was missing from the > logs - which leads me to believe that the server never acknowledged the > request(?) > > Note that the version of node is the only factor that was changed between > tests (same code, same server, same config for all components) > > > Has anyone experience anything of a similar nature? > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
