The following is copied over here from the npm discussion per Isaac's
suggestion.
Dan
-----------
s this what you expect:
events.js:48
throw arguments[1]; // Unhandled 'error' event
^
Error: getaddrinfo ENOENT
at errnoException (dns.js:31:11)
at Object.onanswer [as oncomplete] (dns.js:140:16)
On Mon, 28 May 2012 14:53:28 -0500, Isaac Schlueter wrote:
Run this node program, you'll get ENOENT because the DNS lookup fails.
It doesn't even get to the point of validating certificates.
require('http').get({
host: 'registry.npmjs.org',
path: '/'
}, function (res) {
console.error('got response')
process.exit(0)
})
It works in Firefox, but node is having problems with the DNS lookup.
Ask for help on the node mailing list.
On Mon, May 28, 2012 at 12:44 PM, Dan wrote:
If I browse to registry.npmjs.org with Firefox I get a lot of data in the
response. Is that what you mean? If not give me an example to try.
Dan
On Mon, 28 May 2012 11:38:52 -0500, Isaac Schlueter wrote:
The key is signed by the npmCA cert, which is not in your keychain,
but is the *only* thing in the npm client's keychain. We do ssl more
strictly than the browser. That's not the issue.
Can you make requests to registry.npmjs.org? Apparently that's what
node can't look up the address to. You're getting a ENOENT (that is,
"This thing doesn't exist") when calling getaddrinfo (get address
info). It's definitely a DNS issue.
On Mon, May 28, 2012 at 8:43 AM, Dan wrote:
1030 $ npm install buster pegjs uglify-js
npm http GET https://registry.npmjs.org/buster
npm http GET https://registry.npmjs.org/pegjs
npm http GET https://registry.npmjs.org/uglify-js
npm http GET https://registry.npmjs.org/uglify-js/-/uglify-js-1.2.6.tgz
npm ERR! failed to fetch
https://registry.npmjs.org/uglify-js/-/uglify-js-1.2.6.tgz
npm ERR! Error: getaddrinfo ENOENT
npm ERR! at errnoException (dns.js:31:11)
npm ERR! at Object.onanswer [as oncomplete] (dns.js:140:16)
npm ERR! You may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <n...@googlegroups.com>
npm ERR!
npm ERR! System Linux 3.2.12-gentoo
npm ERR! command "node" "/home/dbeavers/bin/npm" "install" "buster"
"pegjs"
"uglify-js"
npm ERR! cwd /home/dbeavers/source/snoflake/atdt-snoflake-4a461a7
npm ERR! node -v v0.6.18
npm ERR! npm -v 1.1.21
npm ERR! syscall getaddrinfo
npm ERR! code ENOTFOUND
npm ERR! message getaddrinfo ENOENT
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!
/home/dbeavers/source/snoflake/atdt-snoflake-4a461a7/npm-debug.log
npm not ok
-----------
So if tried to open
https://registry.npmjs.org/uglify-js/-/uglify-js-1.2.6.tgz in Firefox and
it
gives:
registry.npmjs.org uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
(Error code: sec_error_unknown_issuer)
It looks to me like there are some issues with certificates on the
server.
I can run the hello world examples in node so apparently I can make http
requests. I believe that resolv.conf is fine.
On Saturday, May 26, 2012 7:19:16 PM UTC-5, Isaac Schlueter wrote:
It looks like the DNS lookups are failing. Are you able to make any
http requests in node? Is your /etc/resolv.conf file configured
appropriately?
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
