search

totemstech / dattss

9 stars 3 forks source link

Crash due to "process out of memory" #38

Open mocheng opened 10 years ago

mocheng commented 10 years ago

I have one dattss v1.0.0 deployed in production. It rans well for about one week and crashed with below log.

[2014-07-06T05:34:14.233Z] {DATTSS-SERVER} [CLEANUP] Done. [2014-07-06T06:34:13.196Z] {DATTSS-SERVER} [CLEANUP] Starting... [2014-07-06T06:34:14.164Z] {DATTSS-SERVER} [CLEANUP] Done. [2014-07-06T07:34:13.197Z] {DATTSS-SERVER} [CLEANUP] Starting... [2014-07-06T07:34:14.159Z] {DATTSS-SERVER} [CLEANUP] Done. [2014-07-06T08:34:13.199Z] {DATTSS-SERVER} [CLEANUP] Starting... [2014-07-06T08:34:14.246Z] {DATTSS-SERVER} [CLEANUP] Done. FATAL ERROR: JS Allocation failed - process out of memory

Anything I can do to debug this?

spolu commented 10 years ago

Hi @mocheng, unfortunately we've discontinued support for DaTtSs (as well as development or even internal use)... We've moved most of our graphing to AWS CloudWatch.

@n1t0 any idea?

mocheng commented 10 years ago

What a pity!

I deployed dattss for all our production application performance monitoring.

There is no licence specified in dattss repository. Can I copy it to a new project to continue work on it?

spolu commented 10 years ago

Yes! Consider it MIT!

n1t0 commented 10 years ago

Hello! I don't know, we've been running it for months without having this problem. It could be my.status from https://github.com/teleportd/dattss/blob/master/server/lib/environment.js which becomes too large, and causes a crash when we try to send an update through socket.io.