No activity on server with WebRTC stream,

Wowza Streaming Engine
1

I do have an issue with a client, who tries to send a webrtc input stream through out web application, current chrome. I do have a console, which does not show any issues, i could’t find any activity on server, there is no matrices change in server, even i checked in trans coder nothing there, not show the stream incoming at all, even though there is no webrtc error. Current chrome, most recent Streaming Engine version.

i checked with log i getting log there, but it could’t help me out

2020-05-31 20:32:20 UTC comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/172.31.32.92:52730 - - - 26794.484 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:17 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26851.962 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:27 UTC comment server INFO 200 - TranscodingSession.updateBehindFilter[webrtc/definst/myStream]: Video behind filter state change. New state: SKIP1FRAME - - - 26861.4 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:27 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26861.477 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:28 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26863.227 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:29 UTC comment server INFO 200 - TranscodingSession.updateBehindFilter[webrtc/definst/myStream]: Video behind filter state change. New state: SKIP2FRAME - - - 26863.433 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:30 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26865.311 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:31 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26866.327 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:32 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26867.342 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:33 UTC comment server INFO 200 - TranscodingSession.updateBehindFilter[webrtc/definst/myStream]: Video behind filter state change. New state: SKIP1FRAME - - - 26867.592 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:33 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26868.373 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:35 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26869.91 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:37 UTC comment server INFO 200 - TranscodingSession.updateBehindFilter[webrtc/definst/myStream]: Video behind filter state change. New state: ALLFRAMESON - - - 26871.437 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:44 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 26878.607 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:58 UTC comment server INFO 200 - WebRTCMessageHandler.handleDTLSMessage: DTLS Alert: close session - - - 26893.354 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:58 UTC comment server INFO 200 - WebRTCSession.shutdown[1121547038]: Shutdown WebRTC session. - - - 26893.392 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC unpublish webrtc INFO 200 myStream - defaultVHost webrtc definst 26893.4 - - - - - - - - - - 1 3194948675 12733331 0 myStream - - - 0 0.0 /myStream /myStream - - -

2020-05-31 20:33:59 UTC comment server INFO 200 - TranscodingSession.close[webrtc/definst/myStream] - - - 26893.403 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC destroy stream INFO 200 myStream - defaultVHost webrtc definst 270.921 - - - - - - - - - - 1 0 12733331 0 myStream - - - 0 0.0 /myStream /myStream - - -

2020-05-31 20:33:59 UTC comment server INFO 200 - TranscoderStreamNameGroup.removeInternal[defaultVHost:webrtc/definst/myStream]: Remove name group: myStream_all - - - 26893.444 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC comment server INFO 200 - TranscoderStreamNameGroup.removeInternal[defaultVHost:webrtc/definst/myStream]: Remove name group: myStream_mobile - - - 26893.445 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC comment server INFO 200 - TranscodingSession.shutdown[webrtc/definst/myStream] - - - 26893.445 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC transcoder-stop transcoder INFO 200 myStream - - - - 26893.445 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC decoder-video-stop transcoder INFO 200 myStream {“ActiveDecodes”:“0”} - - - 26893.445 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC decoder-audio-stop transcoder INFO 200 myStream - - - - 26893.446 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC encoder-video-stop transcoder INFO 200 myStream {“name”:“360p”} - - - 26893.446 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC encoder-audio-stop transcoder INFO 200 myStream {“name”:“360p”} - - - 26893.446 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC encoder-video-stop transcoder INFO 200 myStream {“name”:“160p”} - - - 26893.447 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC encoder-audio-stop transcoder INFO 200 myStream {“name”:“160p”} - - - 26893.447 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:33:59 UTC unpublish stream INFO 200 myStream_160p - - - - 269.097 - - - - - - - - - - 2 0 10222689 0 myStream_160p - - - 0 0.0 /myStream_160p /myStream_160p - - -

2020-05-31 20:33:59 UTC destroy stream INFO 200 myStream_160p - - - - 269.099 - - - - - - - - - - 2 0 10222689 0 myStream_160p - - - 0 0.0 /myStream_160p /myStream_160p - - -

2020-05-31 20:33:59 UTC unpublish stream INFO 200 myStream_360p - - - - 269.111 - - - - - - - - - - 3 0 29703615 0 myStream_360p - - - 0 0.0 /myStream_360p /myStream_360p - - -

2020-05-31 20:33:59 UTC destroy stream INFO 200 myStream_360p - - - - 269.112 - - - - - - - - - - 3 0 29703615 0 myStream_360p - - - 0 0.0 /myStream_360p /myStream_360p - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream]: Destroy live stream packetizer: smoothstreamingpacketizer - - - 26933.53 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_360p]: Destroy live stream packetizer: smoothstreamingpacketizer - - - 26933.53 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_160p]: Destroy live stream packetizer: smoothstreamingpacketizer - - - 26933.53 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream]: Destroy live stream packetizer: cupertinostreamingpacketizer - - - 26933.53 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_360p]: Destroy live stream packetizer: cupertinostreamingpacketizer - - - 26933.53 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_160p]: Destroy live stream packetizer: cupertinostreamingpacketizer - - - 26933.53 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream]: Destroy live stream packetizer: sanjosestreamingpacketizer - - - 26933.531 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_360p]: Destroy live stream packetizer: sanjosestreamingpacketizer - - - 26933.531 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_160p]: Destroy live stream packetizer: sanjosestreamingpacketizer - - - 26933.531 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream]: Destroy live stream packetizer: mpegdashstreamingpacketizer - - - 26933.531 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_360p]: Destroy live stream packetizer: mpegdashstreamingpacketizer - - - 26933.531 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:39 UTC comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[webrtc/definst/myStream_160p]: Destroy live stream packetizer: mpegdashstreamingpacketizer - - - 26933.531 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:34:59 UTC app-stop application INFO 200 definst webrtc/definst - - - 26953.633 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:38:15 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 27150.037 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:38:16 UTC comment server INFO 200 - VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost - - - 27151.053 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:45:25 UTC comment server ERROR 500 - HTTPProviderSimpleWebServer.onHTTPRequest: File missing: C:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.8.0/htdocs/webrtc/publish/index.htm - - - 27580.167 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 20:45:25 UTC comment server ERROR 500 - HTTPProviderSimpleWebServer.onHTTPRequest: File missing: C:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.8.0/htdocs/webrtc/publish/index.htm - - - 27580.213 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 21:26:05 UTC comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/183.136.225.44:7559 - - - 30019.967 - - - - - - - - - - - - - - - - - - - - - - - - -

2020-05-31 21:51:22 UTC comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/195.54.160.230:63473 - - - 31537.326 - - - - - - - - - - - - - - - - - - - - - - - - -

2

When watchdog is disabling the connection, it means that Wowza Streaming Engine is no longer receiving requests from the application. If Wowza Streaming Engine doesn’t receive a message from the client in 90 seconds, the internal client object is disabled assuming the connection is dead.

Send us a support ticket and we’ll take a closer look to see why it’s not connecting.

1 Like
3

I’m having a similiar problem with my log just filling with the:
VHostWatchdog: run: doWatchdog took too long. Interrupting thread.defaultVHost

Was any solution found for this problem?

4

Hi @veer_siniha, were you able to solve your customer’s problem? If so, can you explain what was needed?

@Rose_Power-Wowza_Com, Do you know anyone else who has this problem and has solved it?

Thanks.

5

My apoligies @Caio_Farinazzo as I just happened to come across this follow-up question today while doing some webrtc cleanup in the forums. I searched the watchdog error in our tickets and saw you discussing it with one of our engineers.

I hope his suggestion helps resolve it for you and if not, you can solve it together since you had asked about this such a long time ago, so sorry about that.

If you enabled any of the following properties in the / container, go ahead and disable them and see if the issue happens.
jitterBufferDebug , jitterBufferDelay , logPacketLoss , rtpDePacketizerWrapper , useNack

If you enabled the jitter buffer from here:

Please also disable it.

If you enabled the server side buffer:

Please also disable it and test to see if this resolves the unresponsiveness of your server.