# FFMpeg Stream shutdown

**URL:** <https://community.wowza.com/t/ffmpeg-stream-shutdown/47959>\
**Category:** Wowza Streaming Engine\
**Created:** [February 9, 2017, 11:03am UTC](https://community.wowza.com/t/ffmpeg-stream-shutdown/47959 "2017-02-09T11:03:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![George\_Baker](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@George\_Baker](https://community.wowza.com/u/George_Baker)\
**Post date:** [February 9, 2017, 11:03am UTC](https://community.wowza.com/t/ffmpeg-stream-shutdown/47959/1 "2017-02-09T11:03:35Z")

</div>

We are pushing a live rtmp stream from ffmpeg to wowza following the documentation here [https://www.wowza.com/docs/how-to-use-ffmpeg-with-wowza-media-server-mpeg-ts](https://www.wowza.com/docs/how-to-use-ffmpeg-with-wowza-media-server-mpeg-ts). We are just killing the ffmpeg process. This causes and issue at end of stream, the publish command to wowza is issued delayed by about 10 seconds from when stream actually stopped. What will be an ideal way to end ffmpeg so that wowza receives expected unpublish ? Thanks

---

<div class="post-metadata">

**Author:** ![Jermaine\_Hemby](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@Jermaine\_Hemby](https://community.wowza.com/u/Jermaine_Hemby)\
**Post date:** [February 19, 2017, 8:26am UTC](https://community.wowza.com/t/ffmpeg-stream-shutdown/47959/2 "2017-02-19T08:26:35Z")

</div>

Hello,

Thanks for contacting Wowza Forums!

One way to troubleshoot this is to check your time stamps. Check when you send the stop command and then check the Wowza logs for when it receives the unpublish command. Checking to see if it is network latency that is causing the issue.

regards,

Jermaine