Question

50

Node.js - events.js:154 throw err write EPIPE; Program Crashing

rated 0 times [ 56] [ 6] / answers: 1 / hits: 36372 / 8 Years ago, fri, february 26, 2016, 12:00:00

Trying to run my Node.js program, which has worked for a long time, and now it is suddenly... not. I'm trying to figure out the problem, and I figured it would be helpful if I posted here to try to track it down. Here's the log output:

events.js:154

    throw er; // Unhandled 'error' event

    ^



Error: write EPIPE

    at exports._errnoException (util.js:856:11)

    at WriteWrap.afterWrite (net.js:767:14)

Quite frankly I have no clue why it's throwing an EPIPE error, I've checked that there's nothing running that could interfere and it's running in the exact same shell as it has before. If there's anything I should add let me know.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

albert

Add To Favorites

Follow

Total Points: 652

Total Questions: 105

Total Answers: 108

Location: Pitcairn Islands

Member since Fri, Oct 15, 2021

3 Years ago

albert questions

1 MUI v5 - Extending Typography variant in TypeScript creates error No overload matches this call

Wed, Nov 17, 21, 00:00, 3 Years ago

1 Update one, insert if not exists and modify only when a condition is true MongoDB

Thu, Mar 19, 20, 00:00, 4 Years ago

1 React - input loses focus on keypress

Sat, Nov 9, 19, 00:00, 5 Years ago

1 Multiple select fields filtering with jQuery

Thu, Oct 24, 19, 00:00, 5 Years ago

1 How to update redux state using a react variable passed up to the component from a child

Wed, Sep 25, 19, 00:00, 5 Years ago

View All

answered 8 Years ago everardo · Accepted Answer

Quoting doc

EPIPE: A write on a pipe, socket, or FIFO for which there is no process to read the data. Commonly encountered at the net and http layers, indicative that the remote side of the stream being written to has been closed.

The steam maybe 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.

Please check if there is one big file written or long http package request in your program.

With the following code could make your program exit successfully in this case:

process.stdout.on('error', function( err ) {

    if (err.code == EPIPE) {

        process.exit(0);

    }

});