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

Flood fails to upload torrent files #773

Closed
2 of 3 tasks
beadon opened this issue Mar 15, 2019 · 9 comments
Closed
2 of 3 tasks

Flood fails to upload torrent files #773

beadon opened this issue Mar 15, 2019 · 9 comments

Comments

@beadon
Copy link

beadon commented Mar 15, 2019

Type: Bug Report

  • Try to follow the update procedure described in the README and try again before opening this issue.
  • Please check the F.A.Q..
  • Please check the Troubleshooting wiki section.

Your Environment

  • Version used: 1.0

    • Commit ID (development release) git --no-pager log -1 commit 8d6e88c (HEAD -> master, origin/master, origin/HEAD)
  • Environment name and version:

    • Node.js version node --version v11.11.0
    • npm version npm --version 6.7.0
    • Web browser name and version Chrome 72.0.3626.121
  • Operating System and version:

  • Windows 10 (client)
  • Ubuntu 18.04.2 LTS

Summary

Flood UI fails to upload a file after a couple files have been added.

Expected Behavior

File should upload when "Add torrent" button is pushed

Current Behavior

When the file upload button is pushed, the spinner runs forever.

Possible Solution

How does one debug to find out why the UI is halting ? See error messages below.

Context

Trying to upload .torrent file from a browser.

Error message in Chrome console :
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
VM125:1 POST http://192.168.1.4:3000/api/client/add-files net::ERR_EMPTY_RESPONSE
(anonymous) @ VM125:1
(anonymous) @ xhr.js:178
e.exports @ xhr.js:12
e.exports @ dispatchRequest.js:57
Promise.then (async)
r.request @ Axios.js:51
r.(anonymous function) @ Axios.js:71
(anonymous) @ bind.js:9
addTorrentsByFiles @ TorrentActions.js:38
o.handleAddTorrents @ AddTorrentsByFile.js:121
(anonymous) @ ModalActions.js:41
r @ ReactErrorUtils.js:24
i @ EventPluginUtils.js:83
s @ EventPluginUtils.js:106
p @ EventPluginHub.js:41
m @ EventPluginHub.js:52
r @ forEachAccumulated.js:22
processEventQueue @ EventPluginHub.js:252
r @ ReactEventEmitterMixin.js:15
handleTopLevel @ ReactEventEmitterMixin.js:25
o @ ReactEventListener.js:70
perform @ Transaction.js:141
batchedUpdates @ ReactDefaultBatchingStrategy.js:60
o @ ReactUpdates.js:95
dispatchEvent @ ReactEventListener.js:145

Maybe a related D3 error ? :

d3.js:663 Error: <circle> attribute transform: Trailing garbage, "translate(203,NaN)".
a @ d3.js:663
(anonymous) @ d3.js:962
q @ d3.js:968
xi.each @ d3.js:961
xi.attr @ d3.js:652
value @ TransferRateGraph.js:217
value @ TransferRateGraph.js:186
value @ TransferRateGraph.js:93
value @ TransferData.js:90
r @ ReactErrorUtils.js:24
i @ EventPluginUtils.js:83
s @ EventPluginUtils.js:106
p @ EventPluginHub.js:41
m @ EventPluginHub.js:52
r @ forEachAccumulated.js:22
processEventQueue @ EventPluginHub.js:252
r @ ReactEventEmitterMixin.js:15
handleTopLevel @ ReactEventEmitterMixin.js:25
o @ ReactEventListener.js:70
perform @ Transaction.js:141
batchedUpdates @ ReactDefaultBatchingStrategy.js:60
o @ ReactUpdates.js:95
dispatchEvent @ ReactEventListener.js:145
@noraj
Copy link
Contributor

noraj commented Mar 16, 2019

@beadon are you sure it is not this issue : #741 ?

only happening with torrent file larger than 1,5MB ?

@beadon
Copy link
Author

beadon commented Mar 20, 2019

yes, positive. The file uploaded is 765KB. I can share the file privately if this helps with investigation ?

@noraj
Copy link
Contributor

noraj commented Mar 20, 2019

private message jfurrow on the discord server.

@beadon
Copy link
Author

beadon commented Mar 21, 2019

got it. joined now.

@Mogglio
Copy link

Mogglio commented Mar 26, 2019

Hello I have exactly the same issue, have you found a solution ?
I realize a git pull yesterday but the problem stay here.
Thx.

@T-z3P
Copy link

T-z3P commented Apr 3, 2019

+1
I've tried:
git pull
rm -rf node_modules
npm i
npm run build

And I got:

> flood@1.0.0 build /srv/torrent/flood
> node client/scripts/build.js

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

./client/src/sass/style.scss
Module build failed: ModuleBuildError: Module build failed: ValidationError: CSS Loader Invalid Options

options should NOT have additional properties
    at <anonymous>

./client/src/sass/style.scss
Module build failed: ValidationError: CSS Loader Invalid Options

options should NOT have additional properties

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!     /root/.npm/_logs/2019-04-03T08_35_29_334Z-debug.log
cat /root/.npm/_logs/2019-04-03T08_35_29_334Z-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.9.0
3 info using node@v8.15.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle flood@1.0.0~prebuild: flood@1.0.0
6 info lifecycle flood@1.0.0~build: flood@1.0.0
7 verbose lifecycle flood@1.0.0~build: 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:/srv/torrent/flood/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle flood@1.0.0~build: CWD: /srv/torrent/flood
10 silly lifecycle flood@1.0.0~build: Args: [ '-c', 'node client/scripts/build.js' ]
11 silly lifecycle flood@1.0.0~build: 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.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:915:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid flood@1.0.0
15 verbose cwd /srv/torrent/flood
16 verbose Linux 4.15.0-46-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v8.15.1
19 verbose npm  v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error flood@1.0.0 build: `node client/scripts/build.js`
22 error Exit status 1
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 ]

@noraj noraj added bug and removed more info needed labels May 6, 2019
@jfurrow
Copy link
Member

jfurrow commented May 26, 2019

I can't reproduce, Flood accepts this file without issue.

People commonly experience this when proxying Flood with nginx — are you proxying Flood?

@jfurrow
Copy link
Member

jfurrow commented May 30, 2019

@T-z3P The build error you encountered should be fixed in master

@beadon
Copy link
Author

beadon commented Jul 9, 2019

issue was with the size of accepted messages in rtorrent.

Add to .rtorrent.rc . file :

increase max size of RPC commands

network.xmlrpc.size_limit.set = 2000000

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants