Error: write EPIPE

[Gustavo Machado]

Hi,

We are getting EPIPE errors. Reproducing the error is a matter of uploading multiple files at the same time while keep on using the site, and eventually it will throw.

Here is the stack trace:

"stack":[
"Error: write EPIPE",
" at errnoException (net.js:770:11)",
" at Object.afterWrite (net.js:594:19)"
],

Node version: 0.8.16

What is the right way to handle/avoid this potential error? Any documentation I could look into?

On a somewhat related note, what's the status of domains?

Thanks,

Gustavo Machado
mach...@gmail.com

[Ben Noordhuis]

On Tue, Feb 19, 2013 at 12:47 PM, Gustavo Machado <mach...@gmail.com> wrote:
> Hi,
>
> We are getting EPIPE errors. Reproducing the error is a matter of uploading multiple files at the same time while keep on using the site, and eventually it will throw.
>
> Here is the stack trace:
>
> "stack":[
> "Error: write EPIPE",
> " at errnoException (net.js:770:11)",
> " at Object.afterWrite (net.js:594:19)"
> ],
>
> Node version: 0.8.16
>
> What is the right way to handle/avoid this potential error? Any documentation I could look into?

EPIPE means you're writing to a pipe or socket when the other end has
terminated the connection.

It's a run-time error; there is nothing you can do but close your end as well.

> On a somewhat related note, what's the status of domains?

Alive and well?

> Thanks,
>
> Gustavo Machado
> mach...@gmail.com

[Gustavo Machado]

Hi Ben,

 

EPIPE means you're writing to a pipe or socket when the other end has
terminated the connection.

It's a run-time error; there is nothing you can do but close your end as well.

Since it's throwing, looks like I have to add some try/catch in order to be able to close my end (am I right?). Judging by the stack trace, I won't be able to do so. Can you point me to some more information on how to handle this exception?

Thanks,

Gustavo Machado

[Ben Noordhuis]

You catch it by installing an 'error' event listener on the socket
object, like this:

var conn = net.createConnection(...);
conn.on('error', function(err) {
console.log('caught ' + err);
});

(Ditto for dgram/http/https/etc. objects.)

[Gustavo Machado]

Hi,

In turned out to be the process.stdout. Apart from reducing the console.logs to a minimum, we are planning to use epipebomb to avoid the process to crash under heavy load. Is there any way to re-open the connection to the console.log after it's been EPIPE'd ?

Thanks,

Gustavo Machado
mach...@gmail.com

> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Ben Noordhuis]

On Thu, Feb 21, 2013 at 6:17 PM, Gustavo Machado <mach...@gmail.com> wrote:
> Hi,
>
> In turned out to be the process.stdout. Apart from reducing the console.logs to a minimum, we are planning to use epipebomb to avoid the process to crash under heavy load. Is there any way to re-open the connection to the console.log after it's been EPIPE'd ?
>
> Thanks,
>
> Gustavo Machado
> mach...@gmail.com

What is process.stdout pointing to (tty, pipe, file)?

To answer your question about reopening process.stdout, you could do
something like this:

var fd = fs.openSync('/dev/tty', 'w');
process.stdout = new net.Socket({ fd: fd });

[Gustavo Machado]

Normally it would either be the tty (we are running on windows) or the tty from a child_process, something like this:

var exec = require("child_process").exec,

    path = require("path");

function executeCommand(command, folder, callback){

    var childProc = exec(command, {

        cwd: path.join(__dirname, folder)

    }, callback || function(){});

    childProc.stdout.pipe(process.stdout);

    childProc.stderr.pipe(process.stderr);

}

Thanks,

Gustavo