Error #131 Econnreset
Sign in Pricing Blog Support Search GitHub This repository Watch 10 Star 131 Fork 18 magne4000/quassel-webserver Code Issues 17 Pull requests 0 Projects 0 Pulse Graphs New issue Error: read ECONNRESET crashes #131 Closed burukuru opened this Issue Mar 8, 2016 · 3 comments Projects None yet Labels waiting for information Milestone No milestone Assignees No one assigned 2 participants burukuru commented Mar 8, 2016 I'm getting the following errors when quasselweb crashes: `Connected to localhost:4242 (7da6d8906dcaa5d70818c5ecc2806daaccc8a6de73f9f77d73b9f085b152a862) POST /p/connect 200 25.687 ms - 138 Forwarding socket with token 7da6d8906dcaa5d70818c5ecc2806daaccc8a6de73f9f77d73b9f085b152a862 TCP connection closed by remote (7da6d8906dcaa5d70818c5ecc2806daaccc8a6de73f9f77d73b9f085b152a862) Websocket connection closed (7da6d8906dcaa5d70818c5ecc2806daaccc8a6de73f9f77d73b9f085b152a862) events.js:141 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET at exports._errnoException (util.js:837:11) at TCP.onread (net.js:544:26)` Is it just the connection to the core being reset and causing quasselweb to crash? Is there a debug mode I can run this in? Owner magne4000 commented Mar 8, 2016 check in your browser and in quasselcore if you have other errors, the useful information are usually there. burukuru commented Mar 13, 2016 Had a look at the browser and no errors there. Sounds like it might be an issue with the core. I'll need to run it in debug mode or something to see more detail. magne4000 added the waiting for information label Apr 6, 2016 Owner magne4000 commented Apr 14, 2016 Closing this for now. Feel free to reopen it if needed magne4000 closed this Apr 14, 2016 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
#define ECONNRESET 131 /* Connection reset by peer */ === /|\ Manu Mittal ------- http://www.*-*-*.com/ ~manum Time is a great teacher, but unfortunately it kills all its pupils. --Hector Berlioz Sat, 29 Nov 2003 03:58:04 GMT Mark A. Ode#2 / 4 Errno 131 question Quote:> What does errno 131 really mean!? > Does it mean that the client has closed the connection or wht ? Not a C question. No idea. A C question is something https://github.com/magne4000/quassel-webserver/issues/131 like: Q: Why is it bad to cast the return value of malloc()? A: It can hide the failure to include stdlib.h which will potentially screw up the malloc() prototype. A non-C question is something like: Q: How do I ensure that my buffer gets sent right away with a TCP/IP socket in a send() call? A: Sockets are not part of ISO C. -- Warmest regards. Optimize only if it runs too slowly or does not fit, spaces instead of http://computer-programming-forum.com/47-c-language/1c4f3ad0e28ad5f3.htm tabs. Sat, 29 Nov 2003 04:20:41 GMT Tobias Oe#3 / 4 Errno 131 question Quote: > What does errno 131 really mean!? > Does it mean that the client has closed the connection or wht ? > Thanks > -Manu > #define ECONNRESET 131 /* Connection reset by peer */ The meaning of the different values errno can take are implementation defined. You could use perror("That's the problem:"); to have the system issue an error message. Armed with this message you could then ask in a newsgroup dealing with your os. HTH, Tobias. Sat, 29 Nov 2003 04:39:11 GMT Villy Kru#4 / 4 Errno 131 question Quote: >> What does errno 131 really mean!? >> Does it mean that the client has closed the connection or wht ? >> Thanks >> -Manu >> #define ECONNRESET 131 /* Connection reset by peer */ >The meaning of the different values errno can take are >implementation defined. You could use >perror("That's the problem:"); >to have the system issue an error message. Armed with this >message you could then ask in a newsgroup dealing with your >os. Or even RTFM. The tcp/ip people would guaranteed know what the error means. Villy Sat, 29 Nov 2003 15:46:38 GMT Page 1 of 1 [ 4 post ] Relevant Pages 1. Converting char to CString - Dumb Question #131 2. Getting an address from IP (ie 207.46.131.15 to www.microsoft.com) 3. Question about
working great until the recent ssl update. So I added my ssl certificates and https://twittercommunity.com/t/restricting-api-twitter-com-to-ssl-tls-traffic/12331?page=7 I've confirmed that my ssl verisign G2 certificate is installed https://www.npmjs.com/package/request-promise properly. but now I'm getting the following 401 error back:
TwitterOAuth Object (
[http_code] => 401
[url] => https://api.twitter.com/1.1/statuses/update.json
[host] => https://api.twitter.com/1.1/
[timeout] => 30
[connecttimeout] => 30
[ssl_verifypeer] => 1
[format] => json
[decode_json] => error #131 1
[http_info] => Array (
[url] => https://api.twitter.com/1.1/statuses/update.json
[content_type] => application/json;charset=utf-8
[http_code] => 401
[header_size] => 709
[request_size] => 545
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0.080973
[namelookup_time] => 3.1E-5
[connect_time] => 0.015966
[pretransfer_time] => 0.053174
[size_upload] => 357
[size_download] => 87 error #131 econnreset
[speed_download] => 1074
[speed_upload] => 4408
[download_content_length] => 87
[upload_content_length] => 357
[starttransfer_time] => 0.080945
[redirect_time] => 0
[certinfo] => Array ( )
[redirect_url] => )
[useragent] => TwitterOAuth v0.2.0-beta2
[sha1_method] => OAuthSignatureMethod_HMAC_SHA1 Object ( )
[consumer] => OAuthConsumer Object (
[key] =>
[secret] =>
[callback_url] => )
[token] => OAuthConsumer Object (
[key] =>
[secret] =>
[callback_url] => )
[http_header] => Array (
[cache_control] => no-cache, no-store, must-revalidate, pre-check=0, post-check=0
[content_length] => 87
[content_type] => application/json;charset=utf-8
[date] => Fri, 24 Jan 2014 06:36:57 GMT
[expires] => Tue, 31 Mar 1981 05:00:00 GMT
[last_modified] => Fri, 24 Jan 2014 06:36:57 GMT
[pragma] => no-cache
[server] => tfe
[set_cookie] => guest_id=; Domain=.twitter.com; Path=/; Expires=Sun, 24-Jan-2016 06:36:57 UTC
[status] => 401 Unauthorized
[strict_transport_security] => max-age=631138519
[x_access_level] => read
[x_frame_options] => SAMEORIGIN
[x_rate_limit_limit] => 15
[x_rate_limit_remaining] => 13
[x_rate_limit_reset] => 13905462
[x_transaction] => fbc94029b62664f
[x_xss_protection] => 1; mode=block
[www_authenticate] => OAu
simplified HTTP request client 'request' with Promise support. Powered by Bluebird. Request and Bluebird are pretty awesome, but I found myself using the same design pattern. Request-Promise adds a Bluebird-powered .then(...) method to Request call objects. By default, http response codes other than 2xx will cause the promise to be rejected. This can be overwritten by setting options.simple = false. Also check out the new libraries that are very similar to request-promise v4: request-promise-native v1 – Does not depend on Bluebird and uses native ES6 promises instead. request-promise-any v1 – Allows you to register any Promise library supported by any-promise. Migration from v3 to v4 request became a peer dependency. Thus make sure that request is installed into your project as a direct dependency. (npm install --save request) Continuation Local Storage is no longer supported. However, you can get back the support by using request-promise-any. When you migrated your transform function to v3 and had to add if (!(/^2/.test('' + response.statusCode))) { return resolveWithFullResponse ? response : body; } you may now set the option transform2xxOnly = true instead. Migration from v2 to v3 The handling of the transform function got overhauled. This has two effects: StatusCodeError.response is the transformed instead of the original response now. This error is thrown for non-2xx responses when options.simple is true (default). Please update your transform functions to also cover the transformation of non-2xx responses. To get the old behavior you may add if (!(/^2/.test('' + response.statusCode))) { return resolveWithFullResponse ? response : body; } to the first line of your transform functions that are used for requests with options.simple === true. However, you may prefer updating your transform functions to being able to transform 2xx as well as non-2xx responses because this decouples their implementation from the use of the simple option when doing requests. If a transform operation throws an error, the request will be rejected with a TransformError. Its cause attr