nohup.out
2.92 KB
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
74
75
76
77
78
79
80
81
82
83
84
85
> backend@0.0.0 start /home/swc/capD/backend
> node ./bin/www
module.js:549
throw err;
^
Error: Cannot find module 'csvtojson'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/swc/capD/backend/routes/index.js:4:17)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! backend@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the backend@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/swc/.npm/_logs/2018-06-06T11_24_10_530Z-debug.log
> backend@0.0.0 start /home/swc/capD/backend
> node ./bin/www
module.js:549
throw err;
^
Error: Cannot find module 'csvtojson'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/swc/capD/backend/routes/index.js:4:17)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! backend@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the backend@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/swc/.npm/_logs/2018-06-06T11_27_51_049Z-debug.log
> backend@0.0.0 start /home/swc/capD/backend
> node ./bin/www
Terminated
npm ERR! code ELIFECYCLE
npm ERR! errno 143
npm ERR! backend@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 143
npm ERR!
npm ERR! Failed at the backend@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/swc/.npm/_logs/2018-06-06T11_30_19_413Z-debug.log
> backend@0.0.0 start /home/swc/capD/backend
> node ./bin/www
[0mGET / [36m304 [0m250.367 ms - -[0m
[0mGET /stylesheets/style.css [36m304 [0m3.682 ms - -[0m
[0mGET / [36m304 [0m19.920 ms - -[0m
[0mGET /stylesheets/style.css [36m304 [0m0.507 ms - -[0m
[0mPOST /getPredict [32m200 [0m182.156 ms - 111[0m
[0mGET / [36m304 [0m26.552 ms - -[0m
[0mGET /stylesheets/style.css [36m304 [0m1.106 ms - -[0m
[0mPOST /getPredict [32m200 [0m151.838 ms - 23[0m