# WARN: CloudHandler - ErizoController 0 ---- does not respond. Deleting it

**URL:** <https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444>\
**Category:** Support\
**Created:** [April 5, 2017, 10:05am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444 "2017-04-05T10:05:57Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![HemanthAnakapalle](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/hemanthanakapalle/32/144_2.png) [@HemanthAnakapalle](https://discourse.lynckia.com/u/HemanthAnakapalle)\
**Post date:** [April 5, 2017, 10:05am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/1 "2017-04-05T10:05:57Z")

</div>

WARN: CloudHandler - ErizoController 0 in x.x.x.x does not respond. Deleting it.

Any idea how to fix this?

---

<div class="post-metadata">

**Author:** ![steven8274](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/steven8274/32/70_2.png) [@steven8274](https://discourse.lynckia.com/u/steven8274)\
**Post date:** [April 7, 2017, 1:20am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/2 "2017-04-07T01:20:29Z")

</div>

I also met this problem, using the latest code from master branch.I install licode on Ubuntu 14.04.2.

---

<div class="post-metadata">

**Author:** ![steven8274](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/steven8274/32/70_2.png) [@steven8274](https://discourse.lynckia.com/u/steven8274)\
**Post date:** [April 7, 2017, 8:04am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/3 "2017-04-07T08:04:37Z")

</div>

Does it caused by no data in mongodb?Should I add some data to it?

---

<div class="post-metadata">

**Author:** ![steven8274](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/steven8274/32/70_2.png) [@steven8274](https://discourse.lynckia.com/u/steven8274)\
**Post date:** [April 7, 2017, 9:27am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/4 "2017-04-07T09:27:33Z")

</div>

This warning can be ignored…this is caused by an old erizoController which is created by former node process…

---

<div class="post-metadata">

**Author:** ![vrevidat](https://avatars.discourse-cdn.com/v4/letter/v/779978/32.png) [@vrevidat](https://discourse.lynckia.com/u/vrevidat)\
**Post date:** [April 16, 2017, 4:37pm UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/5 "2017-04-16T16:37:45Z")

</div>

Hi All - I keep getting this error too on one of my servers every few days… This happened since i upgraded to v2.

The sequence of events is always:

```
2017-04-12 09:53:56.477 - WARN: CloudHandler - ErizoController 0 in x.x.x.x does not respond. Deleting it.
2017-04-12 09:53:56.538 - WARN: CloudHandler - I received a keepAlive message from an unknown erizoController
2017-04-12 09:53:56.540 - ERROR: ErizoController - message: This ErizoController does not exist in cloudHandler to avoid unexpected behavior this ErizoController will die

```

After this, all connections will fail with the following error:

`2017-04-12 15:51:57.675 - ERROR: CloudHandler - No erizoController is available.`

Any idea on what could cause this?

---

<div class="post-metadata">

**Author:** ![Javier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/javier/32/20_2.png) [@Javier](https://discourse.lynckia.com/u/Javier)\
**Post date:** [April 17, 2017, 3:44pm UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/6 "2017-04-17T15:44:32Z")

</div>

You should review why ErizoController is failing in this case every few days.

---

<div class="post-metadata">

**Author:** ![vrevidat](https://avatars.discourse-cdn.com/v4/letter/v/779978/32.png) [@vrevidat](https://discourse.lynckia.com/u/vrevidat)\
**Post date:** [July 5, 2017, 6:31am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/7 "2017-07-05T06:31:13Z")

</div>

Hi,

I updated all my servers to v3. I have 2 in Europe and 2 in China. This issue still happens on my servers in China (one is on azure and the other on some local chinese provider). I must also say that I only saw this issue on my servers in China, never anywhere else.

Here is a snap of the logs… Last message before it happened was at 22:33:

`2017-07-04 22:33:44.903 - INFO: EcCloudHandler - message: deleting erizoJS, erizoId: e50b5cf2-edc6-19fd-b304-123237253504`

Then out of the blue, at 01:11, issue happened:

```
2017-07-05 01:11:28.958 - WARN: CloudHandler - ErizoController 0 in xxxxx does not respond. Deleting it.
2017-07-05 01:11:28.970 - WARN: CloudHandler - I received a keepAlive message from an unknown erizoController
2017-07-05 01:11:28.981 - ERROR: ErizoController - message: This ErizoController does not exist in cloudHandler to avoid unexpected behavior this ErizoController will die
2017-07-05 01:11:28.988 - INFO: CloudHandler - [CLOUD HANDLER]: ErizoController in host xxxxx wants to be killed.

```

When that happened, the MongoLog shows crazy times:

```
Wed Jul 5 01:11:28.813 [conn20] update nuvedb.erizoControllers query: { _id: ObjectId('5958b14b47c4f706031b1ecb') } update: { $set: { keepAlive: 0 } } idhack:1 nupdated:1 fastmod:1 keyUpdates:0 locks(micros) w:41 14864ms
Wed Jul 5 01:11:28.814 [conn3] update nuvedb.erizoControllers query: { _id: ObjectId('5958b14b47c4f706031b1ecb') } update: { $inc: { keepAlive: 1 } } idhack:1 nupdated:1 fastmod:1 keyUpdates:0 locks(micros) w:32 14864ms
Wed Jul 5 01:11:28.814 [conn2] update nuvedb.erizoControllers query: { _id: ObjectId('5958b14b47c4f706031b1ecb') } update: { $set: { keepAlive: 0 } } idhack:1 nupdated:1 fastmod:1 keyUpdates:0 locks(micros) w:51 13864ms
Wed Jul 5 01:11:28.814 [conn21] update nuvedb.erizoControllers query: { _id: ObjectId('5958b14b47c4f706031b1ecb') } update: { $inc: { keepAlive: 1 } } idhack:1 nupdated:1 fastmod:1 keyUpdates:0 locks(micros) w:23 13863ms
Wed Jul 5 01:11:28.814 [conn1] update nuvedb.erizoControllers query: { _id: ObjectId('5958b14b47c4f706031b1ecb') } update: { $set: { keepAlive: 0 } } idhack:1 nupdated:1 fastmod:1 keyUpdates:0 locks(micros) w:41 12863ms

```

I would greatly appreciate if anyone can help me troubleshoot this issue. Where should I look? Any other log or something i can do when it happens (since it pretty much does every few days)

Thanks

-VR

---

<div class="post-metadata">

**Author:** ![mkh](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/mkh/32/38_2.png) [@mkh](https://discourse.lynckia.com/u/mkh)\
**Post date:** [July 6, 2017, 2:35pm UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/8 "2017-07-06T14:35:56Z")

</div>

Happens also on my servers randomly (Ubuntu 16.04, Licode v3), really annoying ☹

---

<div class="post-metadata">

**Author:** ![HemanthAnakapalle](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/hemanthanakapalle/32/144_2.png) [@HemanthAnakapalle](https://discourse.lynckia.com/u/HemanthAnakapalle)\
**Post date:** [July 7, 2017, 3:59am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/9 "2017-07-07T03:59:39Z")

</div>

Hi Mohsen,

I could notice only v2, where you are referring v3?

_Please find the list of branches below:_

[hemanth@localhost licode]$ git branch -a

- master  
packages  
v1.2  
remotes/origin/HEAD -\> origin/master  
remotes/origin/agents\_monit  
remotes/origin/erizo\_tree  
remotes/origin/erizo\_tree\_v2  
remotes/origin/gh-pages  
remotes/origin/legacy  
remotes/origin/logs\_with\_connectionid  
remotes/origin/master  
remotes/origin/packages  
remotes/origin/pipe-erizojs-logs  
remotes/origin/revert-939-refactor/erizo\_client\_roomjs  
remotes/origin/test  
remotes/origin/upgrade\_openssl  
remotes/origin/v1.2

Thanks & Regards,  
Hemanth

---

<div class="post-metadata">

**Author:** ![HemanthAnakapalle](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/hemanthanakapalle/32/144_2.png) [@HemanthAnakapalle](https://discourse.lynckia.com/u/HemanthAnakapalle)\
**Post date:** [July 7, 2017, 4:23am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/10 "2017-07-07T04:23:47Z")

</div>

You are using code from master branch (or) some other branch?

---

<div class="post-metadata">

**Author:** ![mkh](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/mkh/32/38_2.png) [@mkh](https://discourse.lynckia.com/u/mkh)\
**Post date:** [July 7, 2017, 8:00am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/11 "2017-07-07T08:00:52Z")

</div>

Hi Hemanth,

Releases are specific commits in the master branch: [https://github.com/lynckia/licode/releases](https://github.com/lynckia/licode/releases)

---

<div class="post-metadata">

**Author:** ![HemanthAnakapalle](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/hemanthanakapalle/32/144_2.png) [@HemanthAnakapalle](https://discourse.lynckia.com/u/HemanthAnakapalle)\
**Post date:** [July 7, 2017, 8:16am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/12 "2017-07-07T08:16:14Z")

</div>

Thanks Mohsen.

I think it is better to tag with its version. We will suggest this.

---

<div class="post-metadata">

**Author:** ![Francesco\_Durighetto](https://avatars.discourse-cdn.com/v4/letter/f/a9a28c/32.png) [@Francesco\_Durighetto](https://discourse.lynckia.com/u/Francesco_Durighetto)\
**Post date:** [July 9, 2017, 8:32pm UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/13 "2017-07-09T20:32:03Z")

</div>

also happened to me once

---

<div class="post-metadata">

**Author:** ![xuminglong](https://avatars.discourse-cdn.com/v4/letter/x/e9bcb4/32.png) [@xuminglong](https://discourse.lynckia.com/u/xuminglong)\
**Post date:** [July 12, 2017, 1:27pm UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/14 "2017-07-12T13:27:32Z")

</div>

You can check the mongodb server and rabbitmq server have been started. If not ,start it by yourself.

---

<div class="post-metadata">

**Author:** ![mkh](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/mkh/32/38_2.png) [@mkh](https://discourse.lynckia.com/u/mkh)\
**Post date:** [July 17, 2017, 2:42am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/15 "2017-07-17T02:42:34Z")

</div>

Restarting EC fixes the problem temporarily. I had to handle it in my app so if EC does not respond after a while then I restart it.

---

<div class="post-metadata">

**Author:** ![batoy28](https://avatars.discourse-cdn.com/v4/letter/b/a88e4f/32.png) [@batoy28](https://discourse.lynckia.com/u/batoy28)\
**Post date:** [January 6, 2018, 8:49am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/16 "2018-01-06T08:49:54Z")

</div>

WARN: CloudHandler - ErizoController 0 in x.x.x.x does not respond. Deleting it.

I just installed the latest Licode and I face this issue in my server environment. In my local environment which Licode is 1 month ago installed, there is no warning like this.

I try to restart the server itself but it keeps popping-up.

Does anyone solved now this issue?

---

<div class="post-metadata">

**Author:** ![Francesco\_Durighetto](https://avatars.discourse-cdn.com/v4/letter/f/a9a28c/32.png) [@Francesco\_Durighetto](https://discourse.lynckia.com/u/Francesco_Durighetto)\
**Post date:** [January 8, 2018, 10:52am UTC](https://discourse.lynckia.com/t/warn-cloudhandler-erizocontroller-0-does-not-respond-deleting-it/444/17 "2018-01-08T10:52:24Z")

</div>

It prevents the current functionality of Licode or everything’s working fine anyway?  
Because Licode stores in mongodb each erizo controller ID and when you restart the process, it fetches the db, try to send ping to that controller and if it doesn’t repond it deletes him.  
so maybe you are getting this “error” every time you restart licode but it’s fine 'cause it’s an old process controller. It should have spawned a new one with a new ID and that should handle the traffic fine.