This is something I've come to take for granted using Erlang.
Keeping node.js servers up forever
21–30 of 41 posts
Re: Keeping node.js servers up forever
#22Off topic, but I like to read blogs on my ipad while in bed and I hate it when authors fuck up with the meta viewport tag.
If I want to double tap to zoom in, because my eyes are not the same as 20 years ago, just let me do that, ok?
Sounded snob? maybe. Sounded reasonable? hell yes.
Btw, is there a bookmarklet to remove the meta viewport tag available somewhere?
Re: Keeping node.js servers up forever
#23When I see a blog post like this, it serves more to raise doubts about Node.js than anything else.
Before today, I had been considering Node for an upcoming product. Now I read that people are actually building and releasing software to work around the fact that Node.js servers regularly incapacitate themselves. Really? Like it just goes down and doesn't know how to cycle itself? Ouch. That translates to me as "Don't go anywhere near Node.js until they get it stable."
So yeah, I'm sure this is a great way to shore up your system. Buy I'm going to think twice before investing time in a system that needs shoring up.
Re: Keeping node.js servers up forever
#24Off topic, but I like to read blogs on my ipad while in bed and I hate it when authors fuck up with the meta viewport tag. If I want to double tap to zoom in, because my eyes are not the same as 20 years ago, just let me do that, ok? Sounded snob? maybe. Sounded reasonable? hell yes. Btw, is there a bookmarklet to remove the meta viewport tag available somewhere?
Just for you: https://gist.github.com/725354
Re: Keeping node.js servers up forever
#25When I see a blog post like this, it serves more to raise doubts about Node.js than anything else. Before today, I had been considering Node for an upcoming product. Now I read that people are actually building and releasing software to work around the fact that Node.js servers regularly incapacitate themselves. Really? Like it just goes down and doesn't know how to cycle itself? Ouch. That translates to me as "Don't…
More of a safety mechanism than anything else. I use daemontools to run qmail, and qmail has never crashed. But if it did, I would still want to receive my email, even though it's "horrible" that qmail could crash.
Sometimes the safest way to handle an error is to kill the process and start a new one. Starting recovery from a known-good state is better than starting from a known-bad one.
Re: Keeping node.js servers up forever
#26When I see a blog post like this, it serves more to raise doubts about Node.js than anything else. Before today, I had been considering Node for an upcoming product. Now I read that people are actually building and releasing software to work around the fact that Node.js servers regularly incapacitate themselves. Really? Like it just goes down and doesn't know how to cycle itself? Ouch. That translates to me as "Don't…
More of a safety mechanism than anything else. I use daemontools to run qmail, and qmail has never crashed. But if it did, I would still want to receive my email, even though it's "horrible" that qmail could crash. Sometimes the safest way to handle an error is to kill the process and start a new one. Starting recovery from a known-good state is better than starting from a known-bad one.
Seems reasonable enough. From the tone of the post, it sounded like crashing was a fairly common thing to happen with Node.js, and that it didn't cycle itself.
Coming from the context of IIS/ASP.NET, which hasn't yet crashed on me (at least not without cycling itself harmlessly) in the 10 years I've been running sites on it, the possibility that you'd need to worry about such things seemed a bit novel.
So basically what you're saying is that it just follows the Unix philosophy and doesn't run its own daemon to cycle it if it falls down. That doesn't sound anywhere near as unreasonable.
Re: Keeping node.js servers up forever
#27Oddly enough, the site is down.
Re: Keeping node.js servers up forever
#28Earlier quoted context omitted.
Well, we can call native node.js code from our process monitor now. We can extend our process monitor with functionality that would be difficult to implement in those other tools.
@intranation Just to toss out a scenario: Lets say under high traffic your application hits an edge case and starts to crash very frequently. Suppose you want to receive an email, SMS, or IM when something like this happens as a devops person. Would you consider that a valid concern of process monitoring? Planned features to Forever include this from the command line, but if you use it from node directly one could im…
Bit by bit... monit restarts the server a defined number of times per second. Then it stops if the service fails to start. If the service is not running, nagios dispatches the snmp traps, sms-es, ims and all the rest.
Re: Keeping node.js servers up forever
#29daemontools is a beautiful thing, personally I think its a much better idea to have a general purpose tool for this kind of thing. I'm not sure why everyone feels the need to reinvent the wheel when it comes to managing background services.
Re: Keeping node.js servers up forever
#30Use Upstart.