-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathnpm-debug.log
73 lines (73 loc) · 4.15 KB
/
npm-debug.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'install', '--save', 'edge' ]
2 info using npm@3.8.3
3 info using node@v5.10.0
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData edge
8 silly fetchNamedPackageData edge
9 silly mapToRegistry name edge
10 silly mapToRegistry using default registry
11 silly mapToRegistry registry https://registry.npmjs.org/
12 silly mapToRegistry data Result {
12 silly mapToRegistry raw: 'edge',
12 silly mapToRegistry scope: null,
12 silly mapToRegistry name: 'edge',
12 silly mapToRegistry rawSpec: '',
12 silly mapToRegistry spec: 'latest',
12 silly mapToRegistry type: 'tag' }
13 silly mapToRegistry uri https://registry.npmjs.org/edge
14 verbose request uri https://registry.npmjs.org/edge
15 verbose request no auth needed
16 info attempt registry request try #1 at 11:57:07 PM
17 verbose request id 4388629d7fd0c1f6
18 http request GET https://registry.npmjs.org/edge
19 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=socket hang up
20 info attempt registry request try #2 at 11:57:17 PM
21 http request GET https://registry.npmjs.org/edge
22 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=socket hang up
23 info attempt registry request try #3 at 11:58:17 PM
24 http request GET https://registry.npmjs.org/edge
25 silly fetchPackageMetaData Error: tunneling socket could not be established, cause=socket hang up
25 silly fetchPackageMetaData at ClientRequest.onError (/usr/lib/node_modules/npm/node_modules/request/node_modules/tunnel-agent/index.js:176:17)
25 silly fetchPackageMetaData at ClientRequest.g (events.js:273:16)
25 silly fetchPackageMetaData at emitOne (events.js:90:13)
25 silly fetchPackageMetaData at ClientRequest.emit (events.js:182:7)
25 silly fetchPackageMetaData at TLSSocket.socketErrorListener (_http_client.js:295:9)
25 silly fetchPackageMetaData at emitOne (events.js:90:13)
25 silly fetchPackageMetaData at TLSSocket.emit (events.js:182:7)
25 silly fetchPackageMetaData at emitErrorNT (net.js:1253:8)
25 silly fetchPackageMetaData at _combinedTickCallback (internal/process/next_tick.js:74:11)
25 silly fetchPackageMetaData at process._tickCallback (internal/process/next_tick.js:98:9)
25 silly fetchPackageMetaData error for edge { [Error: tunneling socket could not be established, cause=socket hang up] code: 'ECONNRESET' }
26 silly rollbackFailedOptional Starting
27 silly rollbackFailedOptional Finishing
28 silly runTopLevelLifecycles Starting
29 silly runTopLevelLifecycles Finishing
30 silly install printInstalled
31 verbose stack Error: tunneling socket could not be established, cause=socket hang up
31 verbose stack at ClientRequest.onError (/usr/lib/node_modules/npm/node_modules/request/node_modules/tunnel-agent/index.js:176:17)
31 verbose stack at ClientRequest.g (events.js:273:16)
31 verbose stack at emitOne (events.js:90:13)
31 verbose stack at ClientRequest.emit (events.js:182:7)
31 verbose stack at TLSSocket.socketErrorListener (_http_client.js:295:9)
31 verbose stack at emitOne (events.js:90:13)
31 verbose stack at TLSSocket.emit (events.js:182:7)
31 verbose stack at emitErrorNT (net.js:1253:8)
31 verbose stack at _combinedTickCallback (internal/process/next_tick.js:74:11)
31 verbose stack at process._tickCallback (internal/process/next_tick.js:98:9)
32 verbose cwd /home/rahul/hin
33 error Linux 3.13.0-24-generic
34 error argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "--save" "edge"
35 error node v5.10.0
36 error npm v3.8.3
37 error code ECONNRESET
38 error network tunneling socket could not be established, cause=socket hang up
39 error network This is most likely not a problem with npm itself
39 error network and is related to network connectivity.
39 error network In most cases you are behind a proxy or have bad network settings.
39 error network
39 error network If you are behind a proxy, please make sure that the
39 error network 'proxy' config is set properly. See: 'npm help config'
40 verbose exit [ 1, true ]