Forever and lot of processes

[ec.developer]

Hi all,
I got a strange problem with Forever .I've started a server, and
everything was fine at the beginning. After a few days I have checked
the process list (top) on my VPS, and I see 6 processes of my server.
It seems that forever forks the process for some reasons. Is it
normal?

Check out the screenshot. There is htop tree output of the process.
http://postimage.org/image/dfi5eknzn/

[Dave Clements]

I wonder if this related to my issue with forever, my hosts have killed all my node processes a few times, because of going over allotted memory - I stopped using Forever and the memory usage has stayed low. 

[henry....@sharelatex.com]

I have come to the conclusion forever is not quite production ready. Although I really like it, there are still lots of bugs, more than the maintainers have time to fix at the moment. I have reverted to using upstart which although not as nice is tried and tested.

[Marak Squires]

Possibly related to: 

https://github.com/nodejitsu/forever/issues/257

--
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 nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--

-- 

Marak Squires

Co-founder and Chief Evangelist

Nodejitsu, Inc.

marak....@gmail.com

[Nuno Job]

Nodejitsu runs on forever. How many servers do you have? :)

Fair point on the issue, im just stating the obvious: forever is run in production in thousands of servers

Sent from my iPhone

--

[Matt]

I prefer runit because the package handles logging, setting userid, and environment variable setting too among other things. It's really nice and easy to use and 100% stable.

--

[ec.developer]

I've checked the issue at github (High memory usage issue), but
despite multiple subprocesses running - memory/cpu consumption is ok.

I'm running 3 servers on my VPS using forever. Each of the servers has
multiple subprocesses running.

Matt thx, I'll check out the runit.

On Apr 19, 5:18 pm, Matt <hel...@gmail.com> wrote:
> I prefer runit because the package handles logging, setting userid, and
> environment variable setting too among other things. It's really nice and
> easy to use and 100% stable.
>

> On Thu, Apr 19, 2012 at 3:46 AM, henry.osw...@sharelatex.com <

>
>
>
>
>
>
>
> henry.osw...@sharelatex.com> wrote:
> > I have come to the conclusion forever is not quite production ready.
> > Although I really like it, there are still lots of bugs, more than the
> > maintainers have time to fix at the moment. I have reverted to using
> > upstart which although not as nice is tried and tested.
>
> > On Thursday, April 19, 2012 6:14:16 AM UTC+1, Dave Clements wrote:
>
> >> I wonder if this related to my issue with forever, my hosts have killed
> >> all my node processes a few times, because of going over allotted memory -
> >> I stopped using Forever and the memory usage has stayed low.
>
> >> On Wednesday, 18 April 2012 09:14:21 UTC+1, ec.developer wrote:
>
> >>> Hi all,
> >>> I got a strange problem with Forever .I've started a server, and
> >>> everything was fine at the beginning. After a few days I have checked
> >>> the process list (top) on my VPS, and I see 6 processes of my server.
> >>> It seems that forever forks the process for some reasons. Is it
> >>> normal?
>
> >>> Check out the screenshot. There is htop tree output of the process.

> >>>http://postimage.org/image/**dfi5eknzn/<http://postimage.org/image/dfi5eknzn/>

[Charlie Robbins]

According to avianflu memory leak issues are fixed in https://github.com/nodejitsu/forever/tree/daemon-patch. We haven't seen it really enough across our thousands of forever procs to make it worth merging into master, but it will probably land in a couple weeks.

Forever is production-ready. Show me reproducible and scientific benchmarks that prove otherwise. I won't deny there are a couple of edge cases in extremely long-term processes, but this will all be resolved in no...@0.8.x when we can **finally ditch** daemon.node and all the other native modules on which forever depends.

--Charlie

[ec.developer]

I've tried runit, and it seems that forever is much more friendly :)
I have restarted now all my servers on VPS once again, and will check
the process list in a few days. When the server is started - there 4
processes created at start. Hope this number of processes will not
increase.

On Apr 20, 7:00 am, Charlie Robbins <charlie.robb...@gmail.com> wrote:
> According to avianflu memory leak issues are fixed inhttps://github.com/nodejitsu/forever/tree/daemon-patch. We haven't seen it

> really enough across our thousands of forever procs to make it worth
> merging into master, but it will probably land in a couple weeks.
>
> Forever is production-ready. Show me reproducible and scientific benchmarks
> that prove otherwise. I won't deny there are a couple of edge cases in
> extremely long-term processes, but this will all be resolved in

> n...@0.8.xwhen we can **finally ditch** daemon.node and all the other

> native modules
> on which forever depends.
>
> --Charlie
>

[Bgsosh]

Does anyone know why the OP is seeing multiple threads spawned for his node process running wallattack.server.js though? Doesn't look like anyone has addresses that yet. 

I'm also a confused about why this is happening.