EPIPE error in Node.js

Question

The following code run fine on JPEG, Docx, zip and several other file formats. Then I try is on mpg-filer however, I am hit by a "Error: write EPIPE" that I am unable to debug. Using a try/catch construction also result in an uncaught exception.

The code:

var fs = require('fs')
const { spawn } = require('child_process')
var file = '/path/to/some/file.jpg'

var rs = fs.createReadStream(file)
const exiftool = spawn('exiftool', ['-json', '-']);
var exif = ''

exiftool.stdout.on('data', function(chunk) {
    exif += chunk
})

exiftool.on('close', function(code) {
    console.log('Sourcefile: %s', JSON.parse(exif)[0].SourceFile)
})

exiftool.on('error', function(error) {
    console.log('exiftool has error: %s', error)
})

rs.pipe(exiftool.stdin)

The error when using mpg-files:

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at WriteWrap.afterWrite [as oncomplete] (net.js:835:14)
Emitted 'error' event at:
    at Socket.onerror (_stream_readable.js:687:12)
    at Socket.emit (events.js:182:13)
    at onwriteError (_stream_writable.js:431:12)
    at onwrite (_stream_writable.js:456:5)
    at _destroy (internal/streams/destroy.js:40:7)
    at Socket._destroy (net.js:605:3)
    at Socket.destroy (internal/streams/destroy.js:32:8)
    at WriteWrap.afterWrite [as oncomplete] (net.js:837:10)

score 10 · Answer 1 · edited Jul 18 '19 at 21:57

10

edit: corrected the code due to issues found in the comments

This kind of error can happen when you try to write to a closed stream

Try/Catch isn't the way to handle stream errors, but you can do it this way:

rs.pipe(exiftool.stdin).on('error', function(e) {
  console.log('rs.pipe has error: ' + e.message)
});

edited Jul 18 '19 at 21:57

pizzaisdavid

455
3
13

answered Aug 14 '18 at 10:58

Sasha Pomirkovany

532
2
9

But why does the stream close mpg's but not the other files, and how do I fix it? – rlp Aug 14 '18 at 11:04
I tried your code, but I do see "rs.pipe has error:" in the output. I get the exact same error message. – rlp Aug 14 '18 at 11:05
I get that. But your exemple would begin the output with "rs.pipe has error:" and that does not happen. I keep getting the exact same error as in the original post. – rlp Aug 14 '18 at 11:37
1

ok, sorry, that wasn't the right way to do it. The next should help, just try changing your last row to the next: rs.pipe(exiftool.stdin).on('error', function(e){ console.log("rs.pipe has error:" + e.message) }); The error message still doesn't say much, but with this you at least get the result and your code doesn't fail – Sasha Pomirkovany Aug 14 '18 at 11:53
1

Thanks a lot, that works. Any input as to how I can make the error not occurring? Is seems like bad practice just to ignore it. – rlp Aug 14 '18 at 12:40
It's hard to tell since there is no meaningful error output. Seems like some problem with exiftool reading .mp4 files, because it works with large .mpg files perfectly. You may try to pass your file to the exiftool in the command line directly to see if there is more meaningful error message there – Sasha Pomirkovany Aug 14 '18 at 13:36
Exiftool handles the files just fine. – rlp Aug 14 '18 at 13:58
Unfortunately, I don't know how to fix it than. EPIPE in this case means that exiftool has closed connection while you still writing to the pipe. Maybe there is something in .mp4 file structure that causing that. For example, exiftool may close the connection ones it already read the metadata it needs to output result, while nodejs still has some chunks to send – Sasha Pomirkovany Aug 14 '18 at 20:02

EPIPE error in Node.js

1 Answers1