# doWatchdog took too long

**URL:** <https://community.wowza.com/t/dowatchdog-took-too-long/97324>\
**Category:** Wowza Streaming Engine\
**Created:** [June 6, 2024, 3:33pm UTC](https://community.wowza.com/t/dowatchdog-took-too-long/97324 "2024-06-06T15:33:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![laurent\_garnier](https://avatars.discourse-cdn.com/v4/letter/l/e99b99/32.png) [@laurent\_garnier](https://community.wowza.com/u/laurent_garnier)\
**Post date:** [June 6, 2024, 3:33pm UTC](https://community.wowza.com/t/dowatchdog-took-too-long/97324/1 "2024-06-06T15:33:26Z")

</div>

Hello,

We are facing an issue where all our encoders are disconnected from time to time. They reconnect automatically a few seconds later. We noticed in the logs that it happens when there is a trace mentionning “doWatchdog took too long”. After this line, we have 2 lines for each encoder (zero sized function and killConnection).  
What is the meaning of this message about Watchdog ? What could be done to fix this problem ?

| 2024-06-04 | 17:33:36 | CEST | comment | server | INFO | 200 | - | VHostWatchdog: run: doWatchdog took too long. Interrupting thread._defaultVHost_ | - | - | - | 732530.965 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 2024-06-04 | 17:33:36 | CEST | comment | server | ERROR | 500 | - | Zero sized function (client:336856530:FMLE/3.0 (compatible; FMSc/1.0)): type:20 size:0: | - | - | - | 732531.179 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
| 2024-06-04 | 17:33:36 | CEST | comment | server | INFO | 200 | - | RequestProcessData.killConnection: 336856530 | - | - | - | 732531.18 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |

Thanks

---

<div class="post-metadata">

**Author:** ![Bernd\_Backhaus1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/bernd_backhaus1/32/1328_2.png) [@Bernd\_Backhaus1](https://community.wowza.com/u/Bernd_Backhaus1)\
**Post date:** [June 7, 2024, 6:32am UTC](https://community.wowza.com/t/dowatchdog-took-too-long/97324/2 "2024-06-07T06:32:35Z")

</div>

> [@laurent\_garnier](#):
>
> doWatchdog took too long

Hi,

please open a [support ticket](https://support.wowza.com/techsupport-request) from your Wowza account, so we can help in your individual use case. Also include your [conf and log files](https://www.wowza.com/docs/how-to-create-a-compressed-zip-file-in-windows-os-x-and-linux) please.

Any additional information you can give about the source will also be helpful.

The error indicates an issue with the inbound connection, but to correctly debug, we’'ll need the full logs and the WSE startup sequence.

Regards,  
Bernd Backhaus  
Wowza Support  
WOWZA | The solution you start with, the partner you scale with.

[Wowza Video](https://www.wowza.com/video?utm_campaign=wowza-video-2022&utm_source=wowza&utm_medium=email-signature) is here! Look at all the new features that will help elevate your business.

[Manage your Support cases online](https://portal.wowza.com/account/support)  
Bookmark our [FAQ page](https://support.wowza.com/hc/en-us)  
Bookmark our [Status page](https://status.wowza.com/)

![](http://community.wowza.com/uploads/original/2X/3/3f119fef7577c4215fcca9d530587529b4e95406.png)