Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

freebsd error resolved adres #9204

Closed
coderxlsn opened this issue Feb 12, 2015 · 7 comments
Closed

freebsd error resolved adres #9204

coderxlsn opened this issue Feb 12, 2015 · 7 comments
Assignees
@cjihrig
Labels
freebsd net P-2 v0.12
Milestone
0.12.3

Comments

@coderxlsn
Copy link

events.js:85
throw er; // Unhandled 'error' event
^
Error: getaddrinfo EAI_BADFLAGS
at Object.exports._errnoException (util.js:746:11)
at errnoException (dns.js:49:15)
at GetAddrInfoReqWrap.onlookup as oncomplete

node v.0.12
freebsd v.10
@cjihrig
Copy link

cjihrig commented Feb 12, 2015

nodejs/node@04bea9f needs to be ported over.

@coderxlsn
Copy link
Author

fix. install io.js 1.1.0

@misterdjules misterdjules added this to the 0.12.1 milestone Feb 12, 2015
@misterdjules
Copy link

Reopening, as this issue hasn't been fixed in joyent/node.

@misterdjules misterdjules reopened this Feb 12, 2015
@pct
Copy link

pct commented Feb 13, 2015

Hi, the io.js patch worked! Please see and try the patch on your freebsd ports https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197539

uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Feb 13, 2015
www/node: fix error getaddrinfo EAI_BADFLAGS
6053abd 
PR:		197539
Reported by:	Valery Komarov <[email protected]>
Submitted by:	Daniel Lin <[email protected]> (maintainer)
Obtained from:	nodejs/node-v0.x-archive#9204


git-svn-id: svn+ssh://svn.freebsd.org/ports/head@378937 35697150-7ecd-e111-bb59-0022644237b5
uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Feb 13, 2015
@swills
www/node: fix error getaddrinfo EAI_BADFLAGS
2b554b0 
PR:		197539
Reported by:	Valery Komarov <[email protected]>
Submitted by:	Daniel Lin <[email protected]> (maintainer)
Obtained from:	nodejs/node-v0.x-archive#9204
uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Feb 13, 2015
www/node: fix error getaddrinfo EAI_BADFLAGS
a448fd0 
PR:		197539
Reported by:	Valery Komarov <[email protected]>
Submitted by:	Daniel Lin <[email protected]> (maintainer)
Obtained from:	nodejs/node-v0.x-archive#9204


git-svn-id: svn+ssh://svn.freebsd.org/ports/head@378942 35697150-7ecd-e111-bb59-0022644237b5
uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Feb 13, 2015
@swills
www/node: fix error getaddrinfo EAI_BADFLAGS
c25e075 
PR:		197539
Reported by:	Valery Komarov <[email protected]>
Submitted by:	Daniel Lin <[email protected]> (maintainer)
Obtained from:	nodejs/node-v0.x-archive#9204
@cjihrig cjihrig mentioned this issue Feb 13, 2015
Closed
@misterdjules misterdjules modified the milestones: 0.12.3, 0.12.2 Apr 1, 2015
misterdjules pushed a commit to misterdjules/node that referenced this issue Apr 21, 2015
net: do not set V4MAPPED on FreeBSD
ce83321 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes nodejs#8540 and nodejs#9204.
@misterdjules
Copy link

Fixed by #18204.

@misterdjules misterdjules added P-2 and removed P-1 labels Apr 21, 2015
@misterdjules
Copy link

Also downgrading to P-2 as I believe this is fixed in FreeBSD's ports.

misterdjules pushed a commit to misterdjules/node that referenced this issue Apr 23, 2015
net: do not set V4MAPPED on FreeBSD
1d47b40 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes nodejs#8540 and nodejs#9204.
misterdjules pushed a commit that referenced this issue Apr 28, 2015
net: do not set V4MAPPED on FreeBSD
0e392f3 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes #8540 and #9204.

Reviewed-By: Colin Ihrig <[email protected]>
PR-URL: #18204
@misterdjules
Copy link

Fixed by 0e392f3.

cjihrig pushed a commit to nodejs/node that referenced this issue May 15, 2015
@cjihrig
net: do not set V4MAPPED on FreeBSD
6f457a0 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
rvagg pushed a commit to rvagg/io.js that referenced this issue May 27, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
853a2b3 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: nodejs#1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Jun 17, 2015
@chrisdickinson
net: do not set V4MAPPED on FreeBSD
7a3e354 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Jul 22, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
a2ac312 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Jul 24, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
f0bccf9 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Jul 30, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
a78629e 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Aug 1, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
668ab61 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Aug 3, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
c6b9e2b 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Aug 4, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
d6a97eb 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
misterdjules pushed a commit to nodejs/node that referenced this issue Aug 4, 2015
@rvagg
net: do not set V4MAPPED on FreeBSD
9bc2e26 
V4MAPPED is not supported on recent FreeBSD versions, at least on 10.1.
Thus, do not set this flag in net.connect on FreeBSD.

Fixes: nodejs/node-v0.x-archive#8540
Fixes: nodejs/node-v0.x-archive#9204
PR-URL: nodejs/node-v0.x-archive#18204
PR-URL: #1555
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cjihrig cjihrig

Labels
freebsd net P-2 v0.12
Projects
None yet
Milestone
0.12.3
Development

No branches or pull requests
5 participants
@pct @misterdjules @orangemocha @cjihrig @coderxlsn