# Error after upgrading

**URL:** <https://discourse.nodered.org/t/error-after-upgrading/13487>\
**Category:** General\
**Created:** [19 July 2019 17:02 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487 "2019-07-19T17:02:38Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [19 July 2019 17:02 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/1 "2019-07-19T17:02:38Z")

</div>

Good afternoon

I'm upograding my system to latest versions and have error as follows at start:

(node:7539) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ready listeners added. Use emitter.setMaxListeners() to increase limit

I have even disabled all flows but still having this message on debug, what could be the problem?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [19 July 2019 17:05 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/2 "2019-07-19T17:05:47Z")

</div>

There isn’t a problem, you have 11 listeners set and if you need then all that’s fine it’s an automatic warning not an error

It doesn’t mean there’s actually a memory leak.

It comes up in the forum from time to time, I’m sure a search would return an answer from CJ or Nick…

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [19 July 2019 17:07 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/3 "2019-07-19T17:07:42Z")

</div>

Where I can set the number of listeners for not having the message?

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [19 July 2019 17:16 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/4 "2019-07-19T17:16:41Z")

</div>

> [@davidcgu](#):
>
> Where I can set the number of listeners...

As already answered....

> [@ukmoose](#):
>
> I’m sure a search would return an answer from CJ or Nick…

---

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [19 July 2019 18:16 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/5 "2019-07-19T18:16:24Z")

</div>

You could start with [this thread](https://discourse.nodered.org/t/maxlistenersexceededwarning-possible-eventemitter-memory-leak-detected-11-scanstop-listeners-added-use-emitter-setmaxlisteners-to-increase-limit-22/13400/5).

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 07:47 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/6 "2019-07-20T07:47:58Z")

</div>

The message tells:

Use emitter.setMaxListeners() to increase limit

However I don't know exactly where or how I should do this, any tip to follow is welcome.

Regards

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [20 July 2019 08:05 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/7 "2019-07-20T08:05:41Z")

</div>

I think it has to be set in the node causing the problem. However as has been stated, it is just a warning so you should be able to ignore it. It is likely from one of the config nodes which is why disabling the flows does not stop it.

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 08:07 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/8 "2019-07-20T08:07:36Z")

</div>

Perfect, thanks boss, I will keep moving forward to complete updates

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [20 July 2019 11:15 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/9 "2019-07-20T11:15:14Z")

</div>

If you do or can identify the node that would be helpful to try and get it fixed.

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 11:39 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/10 "2019-07-20T11:39:11Z")

</div>

I don't know how to search for it, I was trying to enable disable flows but didn't find it, any tip on how to look for it?

Regards

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [20 July 2019 13:23 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/11 "2019-07-20T13:23:12Z")

</div>

maybe there are more lines in the error log than just the one you posted ?

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 13:55 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/12 "2019-07-20T13:55:30Z")

</div>

Well for now what seems clear that arduino node is giving problems, during restart the pi at the begining it connected to the board as I see the relays switching but later on is not working.

If I go to the flow I see connecting and there is no way to make it work even trying to configure again the port.  
However If I remove the usb cable from the pi and plug again (that makes force to change the port from usb0 to usb1) then I change the port on the config node and deploy, then it works again.

To start seems latest 0.2.2 is in trouble with the usb serial port.

Regards

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 14:00 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/13 "2019-07-20T14:00:06Z")

</div>

From other side and less important even not having connetion of after unplug/plug usb cable and change the port on config node + reload page always shows outputs as connected and inputs as connecting.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/4931dca746c71e983028edbb0ece999bbdfcdadf.png)

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 14:01 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/14 "2019-07-20T14:01:00Z")

</div>

How can I downgrade to a previous version?

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [20 July 2019 14:02 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/15 "2019-07-20T14:02:26Z")

</div>

> <https://stackoverflow.com/questions/15890958/install-a-previous-version-of-a-package>

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 16:24 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/16 "2019-07-20T16:24:04Z")

</div>

Well, after many trials and attemps I think I have the clue....

I originally thought it was related to the serial port as apparently loads for a second after service restart but then is gone...node-red-node-serialport but after testing found no difference.

The point is with node-red-node-arduino versions 0.1.0 or previous it works fine, with 0.2.2/0.2.1 or 0.2.0 it has a problem, I see relays making a blink at service boot up _what means it connects for a moment_ but afterwarts is gone and does not connect anymore.

If I diconect usb cable and connect again so raspi reassign to port usb1, I change it on arduino config node and restart it will work at deploy, but as soon as you restart service again it will be again failing.

Hope that helps someone else, for now I remain at 0.1.0 npm version, proceed with\>

npm install node-red-node-arduino@0.1.0

note I have latest version up to date for everything

Thanks for your time guys.

Regards

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [20 July 2019 16:24 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/17 "2019-07-20T16:24:59Z")

</div>

Good clues. Thanks

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [20 July 2019 16:30 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/18 "2019-07-20T16:30:56Z")

</div>

What version of nodejs are you using?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [20 July 2019 16:37 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/19 "2019-07-20T16:37:06Z")

</div>

By the way, if you want to track down that listeners issue, try turning up the Node-RED logging level in settings.js. It produces a shed-load of output but should let you see what Node is loading when you get the error.

---

<div class="post-metadata">

**Author:** ![davidcgu](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@davidcgu](https://discourse.nodered.org/u/davidcgu)\
**Post date:** [20 July 2019 16:42 UTC](https://discourse.nodered.org/t/error-after-upgrading/13487/20 "2019-07-20T16:42:36Z")

</div>

0 Jul 18:42:12 - [info] Node-RED version: v0.20.7  
20 Jul 18:42:12 - [info] Node.js version: v8.16.0  
20 Jul 18:42:12 - [info] Linux 4.19.57-v7+ arm LE  
20 Jul 18:42:25 - [info] Dashboard version 2.15.5

pi@raspberrypi:~/.node-red $ npm list --depth=0  
node-red-project@0.0.1 /home/pi/.node-red  
├── node-red@0.20.7  
├── node-red-contrib-bigtimer@2.2.3  
├── node-red-contrib-broadlink@0.2.4  
├── node-red-contrib-counter@0.1.5  
├── node-red-contrib-cpu@0.0.4  
├── node-red-contrib-cron@0.0.4  
├── node-red-contrib-debounce@0.0.2  
├── node-red-contrib-google-home-notify@0.0.7  
├── node-red-contrib-ibm-watson-iot@0.2.8  
├── node-red-contrib-influxdb@0.3.0  
├── node-red-contrib-inotify@1.1.0  
├── node-red-contrib-moment@3.0.3  
├── node-red-contrib-play-audio@2.3.2  
├── node-red-contrib-reverse@1.0.2  
├── node-red-contrib-schedex@1.6.2  
├── node-red-contrib-smartswitch@0.0.1  
├── node-red-contrib-telegrambot@5.5.1  
├── node-red-contrib-upper@0.1.4  
├── node-red-contrib-uppercase@0.0.3  
├── node-red-dashboard@2.15.5  
├── node-red-node-arduino@0.1.0  
├── node-red-node-email@1.6.2  
├── node-red-node-ping@0.0.16  
├── node-red-node-random@0.1.3  
├── node-red-node-serialport@0.8.3  
├── node-red-node-smooth@0.1.0  
├── node-red-node-sqlite@0.3.7  
└── node-red-node-tail@0.0.3

[Next page](https://discourse.nodered.org/t/error-after-upgrading/13487.md?page=2)