App in audit mode by Watcher...

[Monty Mccune]

I had successfully pushed my app to Nodester on Saturday night -
confirmed it working - went to bed - YAY- and the following day I
received a 503 error when trying to access it :( So I restarted it and
tried to access it but the app just stalls.

Now my logs say:


New PID: 19883
chroot_runner
chroot_runner
Running node v-0.6.12
App in audit mode by Watcher...

info: socket.io started

PORT:16239
HOST:127.0.0.1

DIRECTORY:/app


?????




thanks,
Monty McCune

[Chris Matthieu]

Due to the demand of free Nodester hosting, we needed to set limits on apps to manage our resources.  We added a watcher process over the weekend to keep apps running at 25MB RAM and 25 MB disk space. While we are still evaluating these settings, we intend to offer a paid service in the future with more resources.  We also may increase these free resources in the near future.

Regards,

Chris

[Monty Mccune]

I'm not sure I understand - are you saying that apps cant exceed 25 MB in size? My git repo shows it is 7.4 MB. Could you please clarify. Thanks, Monty

[Kevin Isom]

It's possible, depending how the app is written, that you are
consuming more than 25MB of ram, not diskspace. If it is disk space,
you may want to check the size of the node_modules as well (I assume
those aren't committed)

Cheers
Kev

[Monty Mccune]

How could you check to see how much ram the app is consuming?

[Alejandro Morales Gámez]

That's and interesting question. We are using "process.getMemoryUsage().rss" 

Checkout => https://github.com/nodester/watcher/blob/master/lib/watcher.js#L55

Are you having problems with our limits?