[[Support] spaceinvaderone - Shinobi Pro]

9 hours ago, thestraycat said:

 

Yup - Same here. Wondering if the timelapse folder needs to be set up as a variable in the docker or template or whether shinobi needs the timelapse destination referenced somewhere in the application. My install dosn't even really attempt to export it, high CPU load, then just gives up after about 5 seconds.

Im not to sure what is was doing before it broke but from the error being thrown, I think it is trying to grab what would be the created mp4 from the fileBin directory (which exists) but because nothing is in there after clicking the download button, it does nothing. 

 

I'm assuming that this is the location where after converting the jpegs to the mp4, it then pulls the mp4 file to be downloaded but it doesn't seem to be converting at all.

[[Support] spaceinvaderone - Shinobi Pro]

On 5/3/2020 at 9:32 AM, thestraycat said:

I'm having the same issue other than i don't even get that far. Download button does nothing for me... Can you paste your config?

Same here. This is what is thrown into the log after I click the download button for exporting a time lapse section:

 

Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:87:16) {
errno: 'EPIPE',
code: 'EPIPE',
syscall: 'write'
}
Uncaught Exception occured!
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:87:16)
Error: ENOENT: no such file or directory, stat '/opt/shinobi/fileBin/xxxxxxxxx/FrontOffice/2020-05-14T11-32-06_2020-05-14T23-07-26-30fps.mp4'
at Object.statSync (fs.js:915:3)
at ChildProcess.<anonymous> (/opt/shinobi/libs/videos.js:488:44)
at ChildProcess.emit (events.js:223:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12) {
errno: -2,
syscall: 'stat',
code: 'ENOENT',
path: '/opt/shinobi/fileBin/xxxxxxx/FrontOffice/2020-05-14T11-32-06_2020-05-14T23-07-26-30fps.mp4'
}
Uncaught Exception occured!
Error: ENOENT: no such file or directory, stat '/opt/shinobi/fileBin/xxxxxxx/FrontOffice/2020-05-14T11-32-06_2020-05-14T23-07-26-30fps.mp4'
at Object.statSync (fs.js:915:3)
at ChildProcess.<anonymous> (/opt/shinobi/libs/videos.js:488:44)
at ChildProcess.emit (events.js:223:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:431:19)
at writeOrBuffer (_stream_writable.js:419:5)
at Socket.Writable.write (_stream_writable.js:309:11)
at /opt/shinobi/libs/videos.js:501:61
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:61:3) {
code: 'ERR_STREAM_DESTROYED'
}
Uncaught Exception occured!
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:431:19)
at writeOrBuffer (_stream_writable.js:419:5)
at Socket.Writable.write (_stream_writable.js:309:11)
at /opt/shinobi/libs/videos.js:501:61
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:61:3)

 

Ommited some details with 'x' but yeh, not sure what all this means but after updating the docker it seems something has broken for exporting time lapse vids.