Skip to content
This repository has been archived by the owner on May 31, 2021. It is now read-only.

i install flood but i can not run it #510

Closed
calsc opened this issue Oct 29, 2017 · 11 comments
Closed

i install flood but i can not run it #510

calsc opened this issue Oct 29, 2017 · 11 comments
Labels

Comments

@calsc
Copy link

calsc commented Oct 29, 2017

  1. apt-get install rtorrent,and run it.
    2.install nodejs 8.1.0 thought nvm
    3.install flood.

i run the flood. than ....

root@localhost:/srv/torrent/flood# systemctl start flood
root@localhost:/srv/torrent/flood# systemctl status flood
● flood.service
Loaded: loaded (/etc/systemd/system/flood.service; enabled)
Active: active (running) since Sun 2017-10-29 04:20:05 EDT; 594ms ago
Main PID: 12859 (npm)
CGroup: /system.slice/flood.service
└─12859 npm
root@localhost:/srv/torrent/flood# systemctl status flood
● flood.service
Loaded: loaded (/etc/systemd/system/flood.service; enabled)
Active: failed (Result: start-limit) since Sun 2017-10-29 04:20:08 EDT; 2s ago
Process: 12896 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
Main PID: 12896 (code=exited, status=1/FAILURE)

Oct 29 04:20:08 localhost.localdomain systemd[1]: flood.service: main process exited, code=exited, status=...LURE
Oct 29 04:20:08 localhost.localdomain systemd[1]: Unit flood.service entered failed state.
Oct 29 04:20:08 localhost.localdomain systemd[1]: flood.service start request repeated too quickly, refusi...art.
Oct 29 04:20:08 localhost.localdomain systemd[1]: Failed to start flood.service.
Oct 29 04:20:08 localhost.localdomain systemd[1]: Unit flood.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
root@localhost:/srv/torrent/flood#

@wopian
Copy link
Contributor

wopian commented Oct 29, 2017

Start flood with npm start and paste the error output

@calsc
Copy link
Author

calsc commented Oct 29, 2017

@wopian root@localhost:~# cd /srv/torrent
root@localhost:/srv/torrent# cd flood
root@localhost:/srv/torrent/flood# npm start

flood@1.0.0 start /srv/torrent/flood
node server/bin/start.js

Failed to start web server:
Static assets (index.html) are missing. Please check the 'Compiling assets and starting the server' section of README.md.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! flood@1.0.0 start: node server/bin/start.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flood@1.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! /root/.npm/_logs/2017-10-29T15_52_33_695Z-debug.log
root@localhost:/srv/torrent/flood#

============================】

debug log

0 info it worked if it ends with ok
1 verbose cli [ '/root/.nvm/versions/node/v8.1.0/bin/node',
1 verbose cli '/root/.nvm/versions/node/v8.1.0/bin/npm',
1 verbose cli 'start' ]
2 info using npm@5.0.3
3 info using node@v8.1.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle flood@1.0.0prestart: flood@1.0.0
6 silly lifecycle flood@1.0.0
prestart: no script for prestart, continuing
7 info lifecycle flood@1.0.0start: flood@1.0.0
8 verbose lifecycle flood@1.0.0
start: unsafe-perm in lifecycle true
9 verbose lifecycle flood@1.0.0start: PATH: /root/.nvm/versions/node/v8.1.0/lib/node_modules/npm/bin/node-gyp-bin:/srv/torrent/flood/node_modules/.bin:/root/.nvm/versions/node/v8.1.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle flood@1.0.0
start: CWD: /srv/torrent/flood
11 silly lifecycle flood@1.0.0start: Args: [ '-c', 'node server/bin/start.js' ]
12 silly lifecycle flood@1.0.0
start: Returned: code: 1 signal: null
13 info lifecycle flood@1.0.0~start: Failed to exec start script
14 verbose stack Error: flood@1.0.0 start: node server/bin/start.js
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/root/.nvm/versions/node/v8.1.0/lib/node_modules/npm/lib/utils/lifecycle.js:283:16)
14 verbose stack at emitTwo (events.js:125:13)
14 verbose stack at EventEmitter.emit (events.js:213:7)
14 verbose stack at ChildProcess. (/root/.nvm/versions/node/v8.1.0/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:125:13)
14 verbose stack at ChildProcess.emit (events.js:213:7)
14 verbose stack at maybeClose (internal/child_process.js:887:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5)
15 verbose pkgid flood@1.0.0
16 verbose cwd /srv/torrent/flood
17 verbose Linux 3.16.0-4-amd64
18 verbose argv "/root/.nvm/versions/node/v8.1.0/bin/node" "/root/.nvm/versions/node/v8.1.0/bin/npm" "start"
19 verbose node v8.1.0
20 verbose npm v5.0.3
21 error code ELIFECYCLE
22 error errno 1
23 error flood@1.0.0 start: node server/bin/start.js
23 error Exit status 1
24 error Failed at the flood@1.0.0 start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

@wopian
Copy link
Contributor

wopian commented Oct 29, 2017

Run npm run build once and then systemctl start flood will be 👌

@calsc
Copy link
Author

calsc commented Oct 30, 2017

hi @wopian

i run "npm run build",but the problem still exists

root@localhost:/srv/torrent/flood# npm run build

flood@1.0.0 build /srv/torrent/flood
node client/scripts/build.js
module.js:487
throw err;
^
Error: Cannot find module 'webpack-manifest-plugin'
at Function.Module._resolveFilename (module.js:485:15)
at Function.Module._load (module.js:437:25)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object. (/srv/torrent/flood/client/config/webpack.config.prod.js:8:24)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object. (/srv/torrent/flood/client/scripts/build.js:21:16)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! flood@1.0.0 build: node client/scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flood@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

@SanPilot
Copy link
Member

SanPilot commented Oct 30, 2017

Read this section of README.md. I think you may be forgetting some steps.

@d0tfile
Copy link

d0tfile commented Oct 30, 2017

@calsc previously you run "npm install --production", right? You can fix it by "npm install webpack-manifest-plugin" in flood root or just "npm install". After run "npm run build"

@SanPilot npm has "--production" flag. With that flag npm installs all dependencies but dev. (I described issue here: #509 (comment))

@mirolm
Copy link

mirolm commented Oct 30, 2017

Please look at the README as SanPilot suggested, because the way to build flood got changed with recent commits. As stated there:

Compiling assets and starting the server

Run npm install.
Run npm run build.
Run npm start.

The --production flag got removed and you do not need to use it.

@dcousens
Copy link
Contributor

@calsc was your issue resolved?

@calsc
Copy link
Author

calsc commented Nov 28, 2017 via email

@noraj
Copy link
Contributor

noraj commented Nov 28, 2017

Sorry to hear that :/

@noraj noraj closed this as completed Nov 28, 2017
@t0maz
Copy link

t0maz commented Oct 13, 2018

Hi guys,

Same issue here. I've followed above steps but here is the current situation:

flood@owczarek /mnt/data/Pliki/samba_share/Download/rtorrent/flood $ npm install
npm WARN flood@1.0.0 No repository field.
npm WARN flood@1.0.0 No license field.

updated 1 package and audited 34504 packages in 10.478s
found 8 moderate severity vulnerabilities
run npm audit fix to fix them, or npm audit for details
flood@owczarek /mnt/data/Pliki/samba_share/Download/rtorrent/flood $ npm audit fix
npm WARN flood@1.0.0 No repository field.
npm WARN flood@1.0.0 No license field.

updated 1 package in 8.143s
fixed 8 of 8 vulnerabilities in 34504 scanned packages
flood@owczarek /mnt/data/Pliki/samba_share/Download/rtorrent/flood $ npm run build

flood@1.0.0 build /mnt/data/Pliki/samba_share/Download/rtorrent/flood
node client/scripts/build.js

Creating an optimized production build...
Failed to compile.

Cannot read property 'compilation' of undefined

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! flood@1.0.0 build: node client/scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flood@1.0.0 build 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/flood/.npm/_logs/2018-10-13T21_16_51_957Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm@6.4.1
3 info using node@v10.12.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle flood@1.0.0prebuild: flood@1.0.0
6 info lifecycle flood@1.0.0
build: flood@1.0.0
7 verbose lifecycle flood@1.0.0build: unsafe-perm in lifecycle true
8 verbose lifecycle flood@1.0.0
build: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/mnt/data/Pliki/samba_share/Download/rtorrent/flood/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
9 verbose lifecycle flood@1.0.0build: CWD: /mnt/data/Pliki/samba_share/Download/rtorrent/flood
10 silly lifecycle flood@1.0.0
build: Args: [ '-c', 'node client/scripts/build.js' ]
11 silly lifecycle flood@1.0.0build: Returned: code: 1 signal: null
12 info lifecycle flood@1.0.0
build: Failed to exec build script
13 verbose stack Error: flood@1.0.0 build: node client/scripts/build.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:182:13)
13 verbose stack at maybeClose (internal/child_process.js:962:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid flood@1.0.0
15 verbose cwd /mnt/data/Pliki/samba_share/Download/rtorrent/flood
16 verbose Linux 4.4.0-128-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v10.12.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error flood@1.0.0 build: node client/scripts/build.js
23 error Failed at the flood@1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Please let me know if you need any more info.
Thanks

@Flood-UI Flood-UI locked as off-topic and limited conversation to collaborators Oct 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

8 participants