Evo-mp4writer - segmentation fault error

Support ForumCategory: Installation and Basic OperationEvo-mp4writer – segmentation fault error
drozd Member asked 2 years ago

We utilize Evostream for recording of the RTMP stream and then process the files into MP4s.
We have run into an “Segmentation fault“issue with the processing of the recording while running this command: sudo -u evostreamd evo-mp4writer -path=/mnt/archive/evostream-recording/d36af850-159b-4320-aa16-89d693e881b0-360p_part0000.mp4. Following segments were processed ok.
Syslog error: “[1558236.248882] evo-mp4writer[32597]: segfault at 7f96e4413000 ip 00007f96e44a6909 sp 00007ffd718ae718 error 7 in libc-2.23.so[7f96e4413000+1bf000]
Server configuration: Ubuntu 16.04 x64, 40 CPU, 16 GB RAM

4 Answers
Don Evostream-Staff answered 2 years ago

Hi drozd,

Could you provide the EMS version by running this command?
$ evostreamms –version

I’m not sure I understand your process. Are you using the record command of the EMS to record RTMP streams? Was the EMS shutdown unexpectedly while recording, leaving behind partial MP4 files that you’re trying to assemble? Or is there another reason why run evo-mp4writer manually?

Cheers,
Don

drozd Member answered 2 years ago

Hi Don,
This is the output of the $evostreamms –version command
EvoStream Media Server (www.evostream.com) version 1.7.1 build 4491 with hash: 64b305253110afc4acd5aeaf87f0a0b0f9b53526 – PacMan|m| – (built for Ubuntu-16.04-x86_64 on 2016-06-17T10:05:48.000)
Compiled on machine: `Linux build-16-64 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux`
Yes, we were using the EMS ‘record’ command to record RTMP stream a ‘removeConfig’ command to stop recording repeatedly. There was no unexpected shutdown of the EMS and next recordings of the same RTMP stream were processed without any problems. When we discovered the problem with this segment, we tried to recover it manually with the help of the evo-mp4writer, but encountered this problem.
Thanks,
Vladimir

Don Evostream-Staff answered 2 years ago

Hi Vladimir,

So the partial MP4 files were found right after using the ‘removeConfig’ command to stop recording?
Could you shutdown the EMS before running evo-mp4writer?
Also, please try adding ‘–recovery’ to the command.
> $ ./evo-mp4writer -path=/path/to/file/partial_filename.mp4 –recovery
I’m assuming that you have the following files before running the above command:
> /path/to/file/partial_filename.mp4.info
> /path/to/file/partial_filename.mp4.track1
> /path/to/file/partial_filename.mp4.track2

Cheers,
Don

drozd Member answered 2 years ago

Hi Don,
 
Yesy, the partial MP4 files were found after using the ‘removeConfig’ command to stop recording. We have also tried to run the evo-mp4writer with the ‘–recovery’ option, but still with the same result. I am not able to shutdown EMS before running evo-mp4writer at the moment. We have live events currently running and I don’t want to disturb the workflow (I can try that on Monday). 
 
The recorded files on the storage look like this:
-rw-r–r–+  1 evostreamd evostreamd  4.3K Apr 17 16:42 d36af850-159b-4320-aa16-89d693e881b0-360p_part0000.mp4.info
-rw-r–r–+  1 evostreamd evostreamd  357M Apr 17 16:42 d36af850-159b-4320-aa16-89d693e881b0-360p_part0000.mp4.mdat
-rw-r–r–+  1 evostreamd evostreamd  2.9M Apr 17 16:42 d36af850-159b-4320-aa16-89d693e881b0-360p_part0000.mp4.track1
-rw-r–r–+  1 evostreamd evostreamd  1.6M Apr 17 16:42 d36af850-159b-4320-aa16-89d693e881b0-360p_part0000.mp4.track2
 
Thanks,
 
Vladimir