balderdashy / sails

Realtime MVC Framework for Node.js
https://sailsjs.com
MIT License
22.85k stars 1.95k forks source link

Skipper: req aborted error #4711

Open chandanpal opened 6 years ago

chandanpal commented 6 years ago

can anyone please share, how can we handle the aborted upload error.

at IncomingMessage.onReqAborted (/home/spyglass/callhome_from_pod/callhome/node_modules/skipper/node_modules/multiparty/index.js:175:17) at IncomingMessage.emit (events.js:182:13) at IncomingMessage.EventEmitter.emit (domain.js:442:20) at abortIncoming (_http_server.js:444:9) at socketOnClose (_http_server.js:437:3) at Socket.emit (events.js:187:15) at Socket.EventEmitter.emit (domain.js:442:20) at TCP._handle.close [as _onclose] (net.js:598:12)



nginx error:

10.0.1.190 nginx [13/Nov/2018:13:59:23 +0000] "POST /support/file/upload HTTP/1.1" 400 0 "-" "python-requests/2.9.1" "128.107.241.176" rt=854.173 uct=- uht=- urt=-

I have used  keepalive options but  still I am getting the same error.

upstream callhome_backend {
    server 10.106.3.199:1337;
    keepalive 1024;
}
.....

    location /support/ {
        auth_basic "Private Property";
        auth_basic_user_file /etc/nginx/.htpasswd;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection '';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_pass http://callhome_backend/;
    }

``

_Originally posted by @twhtanghk in https://github.com/balderdashy/skipper/issues/49#issuecomment-139506144_
sailsbot commented 6 years ago

@chandanpal Thanks for posting, we'll take a look as soon as possible. In the meantime, if you haven’t already, please carefully read the issue contribution guidelines and double-check for any missing information above. In particular, please ensure that this issue is about a stability or performance bug with a documented feature; and make sure you’ve included detailed instructions on how to reproduce the bug from a clean install. Finally, don’t forget to include the version of Node.js you tested with, as well as your version of Sails or Waterline, and of any relevant standalone adapters/generators/hooks.

Thank you!


For help with questions about Sails, click here. If you’re interested in hiring @sailsbot and her Austin-based minions, click here.

ceol95 commented 5 years ago

i have the same issue but on localhost. how you fix this?

raqem commented 5 years ago

Hi @chandanpal, We are currently working on moving all the open Sails issues into one repo to help the devs keep a better eye on things. ~Cheers!

johnabrams7 commented 5 years ago

@chandanpal @ceol95 - Hey, what version of skipper are you using? Does this issue still occur in the latest version 0.8.7 released 2 months ago?

jayeshagarwal commented 3 years ago

@chandanpal @ceol95 - Hey, what version of skipper are you using? Does this issue still occur in the latest version 0.8.7 released 2 months ago?

I'm also facing the same issue on localhost and I'm using skipper 0.8.7 when I set maxTimeToBuffer: 500000 in sails.config.http

eashaw commented 3 years ago

Hi @jayeshagarwal, would you be able to make a minimal Sails app that reproduces this issue in a Github repo?