Node v0.6.3 crashes EC2 instance

[leahciMic]

Node v0.6.3 is crashing my EC2 instance. I have installed it on the default 32-bit Amazon AMI. I believe it's a problem with Xen.

Node v0.4.x works fine (I've tried v0.4.7 and v0.4.12).

Message from syslogd@ip-10-56-53-235 at Nov 6 13:41:31 ...
kernel:[171753.697946] invalid opcode: 0000 [#8] SMP

Message from syslogd@ip-10-56-53-235 at Nov 6 13:41:31 ...
kernel:[171753.697956] last sysfs file: /sys/devices/system/cpu/cpu0/cache/index2/shared_cpu_map

Message from syslogd@ip-10-56-53-235 at Nov 6 13:41:31 ...
kernel:[171753.698006] Process node (pid: 27776, ti=d481a000 task=e604be80 task.ti=d481a000)

[bnoordhuis]

If by 'crash' you mean 'hangs the kernel' I'm afraid there is not much we can do about that. You'll have to contact EC2 customer support for that.

[pzgz]

Well, got same issue on my EC2 instance with 0.6.5 installation.

[leahciMic]

I believe it's Xen and not Amazon specifically. Anyone with Xen experience can confirm this? If Node is to continue its current growth it's essential that it is able to run under virtual machines. Currently 0.4.x does, and 0.6.x does not. I believe this makes 0.6.x buggy, and not worthy of being put into production (but then again, one could argue Node in itself isn't ready for production).

[bnoordhuis]

You never did confirm the kind of behaviour you're seeing. Is it Node that is crashing or the VM?

[leahciMic]

Node itself crashes, and the instance becomes extremely slow, and never seems to recover until the instance is restarted.

[bnoordhuis]

Okay, so you're looking at two issues here, a crash in Node and strange Xen behaviour. Can you try this:

./configure --debug && make && gdb --args ./node_g script.js

When it crashes, type backtrace full and post the output here.

[leahciMic]

Sure, it may take me a day to have this completed

[migounette]

I use Xen 4.1 (org) and node it works perfectly under Windows and Linux (Ubuntu Maverick / Oneric). At this stage, so far so good... Can you provide us more details on the Version of EC2 and/or Xen. If you are the admin, you can look at /var/log/xen logs files for more details.

[leahciMic]

I don't have a /var/log/xen. The setup is using Amazon's Linux AMI (latest), and node 0.6.x. Please confirm that you are running 0.6.x under Xen. If this is the case, it's something specific to Amazon's setup.

[migounette]

I am running V0.6.0 with a Xen 4.1 on Ubuntu Oneiric 64-bits under dom0 Xen 4.1.1

If this is the case, it's something specific to Amazon's setup.
==> Yes or No, depending of several parameters
Kernel Version / API calls that my current implementation does not implement (Pure HTTP / WebSocket oriented)

A way to debug is to install in debug mode or try to catch the last calls....

eg. trace (attaching to the process) or gdb (attaching to the process) and try to reproduce the issue in order to get more details.

[georgesnelling]

just a note: I've been running node 0.6.2 - 0.6.4 on Amazon's current default Linux 64-bit AMI with no major trouble. I've built from source and used the yum package manager and all seems fine.

[pzgz]

Well, my updates coming. I tried to reboot my ec2 instance and it just wouldn't come back. And I saw a thread in the support forum:

https://forums.aws.amazon.com/thread.jspa?threadID=82018

I noticed, it error message he got is totally same as mine. So I tried the introduction within this link: https://aws.amazon.com/amazon-linux-ami/latest-release-notes/

The steps are listed in section "After using yum to upgrade to Amazon Linux AMI 2011.09, t1.micro 32-bit instances fail to reboot."

After that, my instance was back. And the good news is, I also tried node.js, now it works perfectly.

Maybe it's just something with Amazon latest instance release.

[bnoordhuis]

Closing, turns out the issue was with EC2, not Node.

I believe this makes 0.6.x buggy, and not worthy of being put into production

You should get one of those "jumping to conclusions" pads, they're awesome.

[iloire]

I was running Linux AMI 2011 32 bits and experienced the described problem.
Tried to yum upgrade as the article suggested and didn't work.

Tried a new instance Linux AMI 2011 64 bits and worked!

In both cases I compiled 0.6.7 from source code (configure, make, sudo make install)