-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSX Mavericks - Getting ECONNRESET #329
Comments
Node version? node-imap version? Can you set |
node v0.10.21 Here is the debug output from my script with the error. ( I edited the username and password )
|
Can you try this patch and see if it helps any? |
Sorry. Those changes did not help. The same error occurs. Additionally, I printed out this._stream.readable, and the value is true. |
I'm at a loss then. You might post on node's github issue tracker. Maybe it's some weird TLS-related edge case? shrug |
I just started getting this, too. I was playing with the code late last night on my Mac (OSX Mavericks) and didn't get this error at all and throughout the day (Windows 7) didn't have this issue but now tonight I'm getting it on and off with my Mac. I think it's something on Gmail's end. My theory is that they get swamped at certain times of the day and requests get kicked back. I setup a timeout in the event of this error to retry the process again and that seems to have worked, so far at least. Hope that helps! Related question for mscdex, should I have imap.end() in the error handler or is it unneeded? imap.once('error', function(err) {
if ( err.toString() === "Error: read ECONNRESET" &&
++attempts <= maximumAttempts){
console.log( "ERROR: Attempt " + attempts);
setTimeout( collectFunction, 500 );
}
imap.end();
}); Edit: Yeah, sometimes it works first attempt. Sometimes it takes one or two but eventually I do get it to collect the data. |
You shouldn't need |
I'm still getting this error every time I call |
@Zugwalt What if you try applying this patch on top of master? I don't have an OSX 10.9 system available to me at the moment, so I'm not sure what else to try. |
Unfortunately that patch didn't help--I'll see if I can dive into it on my OSX system after the new year. |
Solved capturing all imap error event, see #303 . |
I get this error, probably because I run chmod everywhere |
After upgrading to Mavericks for Mac, I am getting the following error. It seems to occur after an imap.search. The error doesn't always happen, it sometimes takes 3 - 5 times running the script, but it does happen and it never happened until I upgraded to Mavericks.
{ [Error: read ECONNRESET]
code: 'ECONNRESET',
errno: 'ECONNRESET',
syscall: 'read',
source: 'socket' }
Node v0.10.21
Here is my script. Before running, just replace the username and password.
The text was updated successfully, but these errors were encountered: