On Tue, Dec 23, 2014 at 7:34 AM, Aneek Mukhopadhyay
<dream.an...@gmail.com> wrote:
>
> Hello,
>
> I am using an Amazon EC2 instance using CentOs 5.4. I installed nodejs in 
> different servers that follow the same architecture. In the current server I 
> installed nodejs by following the below steps.
>
> INSTALL PYTHON 2.75
> yum install gcc zlib-devel python-setuptools readline-devel
> cd /usr/src
> wget http://www.python.org/ftp/python/2.7.5/Python-2.7.5.tgz
> tar -xzf Python-2.7.5.tgz
> cd Python-2.7.5
> ./configure
> make altinstall
> python2.7 -V
>
> INSTALL NODEJS
> sudo yum groupinstall 'Development Tools'
> sudo yum install openssl-devel
> cd /usr/local/
> wget http://nodejs.org/dist/node-latest.tar.gz
> tar zxvf node-latest.tar.gz
> cd node-v0.10.34
> PYTHON=/usr/local/bin/python2.7
> export PYTHON
> python2.7 configure && make && make install
> node --version
>
> But the issue is, when ever I run the "node" command I see the following 
> image.
>
>
>
>
>
>
>
>
>
>
> From nodejs IRC @fullstack suggested to run "strace -f /usr/local/bin/node" - 
> The result of this is : https://gist.github.com/aneek/0ef3d9fe1a6521fdee6a
> Also as per @fullstack's suggestion instead of using "python2.7 configure && 
> make && make install" I tried to install with "./configure && make && make 
> install". But error occurred (That's why I used Python2.7)
>
>
>
>
>
>
>
>
> Please help me on this. Thanks in advance!

For posterity:

> syscall_293(0xf33d5c, 0x80000, 0x622f6c61636f6c2f, 0x65646f6e2f6e69, 0x3, 
> 0x7fff291f3f60, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 
> 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1) = 0x125

strace doesn't recognize it (it's probably too old) but that's the
pipe2() system call and it's returning a rather strange value.  If you
interpret it as a sign-extended 64 bits value, it's -293, which can
hardly be a coincidence.

Negative values in the range -4095 to -1 inclusive is how the Linux
kernel returns error codes but why it returns that particular value is
beyond me; normal error codes approximately fall in the range -133 to
-1.

At any rate, we can probably figure it out.  If you file an issue at
https://github.com/libuv/libuv/issues and include the output of `uname
-a`, I'll take a look.

In case you're wondering, libuv is the I/O library that node uses
under the hood; that pipe2() system call originates from it.

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAHQurc_Ewz4k-dcxAoj6RWuBvZXZ_iFDYsr6uvrmfhx0AWVE1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to