# Syslog filled with "(node:##) TimeoutOverflowWarning: ########## does not fit into a 32-bit signed integer"
**URL:** https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966
**Category:** General
**Created:** [8 June 2019 05:59 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966 "2019-06-08T05:59:13Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@Jesse305](https://discourse.nodered.org/u/Jesse305)
#### Post date: [8 June 2019 05:59 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/1 "2019-06-08T05:59:13Z")
Hello,
My syslog is being filled with variations of the following error messages (this is just a short excerpt):
> (node:1215) TimeoutOverflowWarning: 2587711790 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711789 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711788 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711787 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711785 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711784 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711783 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711782 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711780 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711779 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711778 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
> (node:1215) TimeoutOverflowWarning: 2587711777 does not fit into a 32-bit signed integer.
> Timeout duration was set to 1.
Because the timeout is reset to `1`, whatever is causing this issue is re-executed after 1ms.
Searching Google seems to indicate that a value larger than a 32-bit is being used fro setTimeout - this is exactly what the log entry indicates - but I am not manually setting that anywhere. In fact, all of my flow tabs are disabled (to unload it all).
**OS:** Linux vm-deb1 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86\_64 GNU/Linux
**Output from Node-RED's startup:**
8 Jun 01:58:12 - [info] Node-RED version: v0.20.5
8 Jun 01:58:12 - [info] Node.js version: v12.4.0
8 Jun 01:58:12 - [info] Linux 4.9.0-9-amd64 x64 LE
Any help would be greatly appreciated.
**Edit:** This seems to only occur when the UI is loaded. If the UI does not load, the above does not occur.
Thanks,
Jesse
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [8 June 2019 07:36 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/2 "2019-06-08T07:36:13Z")
> [@Jesse305](#):
>
> Node.js version: v12.4.0
I would start by installing a version of node that is recommended for node-red (8.x or 10.x). It may not help but will at least eliminate that as a possibility.
If it does solve it then one of the installed nodes is not compatible with v12.4.0
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [8 June 2019 09:58 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/3 "2019-06-08T09:58:38Z")
@colin I think you meant node.js 8.x or 10.x
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [8 June 2019 10:08 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/4 "2019-06-08T10:08:53Z")
Thanks @zenofmud, yes, I meant it should be 8 or 10, I have amended my previous post accordingly.
---
### Author:  [@Jesse305](https://discourse.nodered.org/u/Jesse305)
#### Post date: [8 June 2019 18:40 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/5 "2019-06-08T18:40:30Z")
Interesting suggestion...it seems like the UI portion of one of the following nodes is causing issues:
> "node-red-contrib-batcher": "latest",
> "node-red-contrib-semaphore": "latest",
> "node-red-node-ping": "latest",
> "node-red-node-smooth": "latest",
> "node-red-node-sqlite": "latest",
> "node-red-node-timeswitch": "latest"
I was on Node.js 9.11.2 when the issue started. I thought of upgrading to 10.16.0 but it persisted and then again on 12.4.0 as the original post indicates.
Based on yoru suggestion, I backtracked all the way to 8.16.0 and it appears to be working now...
> 8 Jun 14:29:07 - [info] Node-RED version: v0.20.5
> 8 Jun 14:29:07 - [info] Node.js version: v8.16.0
> 8 Jun 14:29:07 - [info] Linux 4.9.0-9-amd64 x64 LE
How would I go about troubleshooting which module is having this issue best? (Short of installing one at a time)
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [8 June 2019 19:03 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/6 "2019-06-08T19:03:23Z")
The error message is coming from node.js directly - it isn't been logged by Node-RED itself. So the only way to narrow it down will be to reinstall one node at a time.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [8 June 2019 20:36 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/7 "2019-06-08T20:36:42Z")
> [@knolleary](#):
>
> the only way to narrow it down will be to reinstall one node at a time.
It would be more efficient to do a binary search, so add half of them which then ties it down to that half or the other half, repeat the exercise halving the number each time and you will get there in a max of three iterations.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [6 July 2019 08:01 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/8 "2019-07-06T08:01:21Z")
@Jesse305 did you get to the bottom of this, or have you just stuck with node 8.x for the moment. The same problem has been reported again.
> [@Node-RED 0.20.7 released](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/2):
>
> Hi, Is there a known issue (yet) with timers/delays in 0.20.7? I upgraded earlier and my log file is a solid mountain of: (node:1192) TimeoutOverflowWarning: 3124648168 does not fit into a 32-bit signed integer. Timeout duration was set to 1. I'm not using setInterval(), timers, delays, or any timing things like that, this is a program that has been running for about a month with no issues.
---
### Author:  [@thatcadguy](https://discourse.nodered.org/u/thatcadguy)
#### Post date: [6 July 2019 15:20 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/9 "2019-07-06T15:20:32Z")
@Jesse305 I had the same problem and @knolleary appears to have found something related to adminAuth; I deleted ~/.node-red/.sessions.json and it went away.
[https://discourse.nodered.org/t/node-red-0-20-7-released/12955/11?u=thatcadguy](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/11)
---
### Author:  [@thatcadguy](https://discourse.nodered.org/u/thatcadguy)
#### Post date: [21 July 2019 01:55 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/11 "2019-07-21T01:55:57Z")
I commented incorrectly before, it's the sessions file that needs to be deleted not settings.
---
### Author:  [@mu3](https://discourse.nodered.org/u/mu3)
#### Post date: [21 July 2019 01:59 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/12 "2019-07-21T01:59:12Z")
Removed `.sessions.json`, still throws these errors 🤔
I use Node v12.6.
Can be related to macOS env?
---
### Author:  [@mu3](https://discourse.nodered.org/u/mu3)
#### Post date: [21 July 2019 05:59 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/13 "2019-07-21T05:59:36Z")
In my case the `sessionExpiryTime` was too big (3 month):
> [@Node-RED 0.20.7 released](https://discourse.nodered.org/t/12955/26):
>
> In my case the problem was with sessionExpiryTime: adminAuth: {... sessionExpiryTime: 3\*30\*24\*60\*60} Probably, it's calculated in microseconds so I was getting: 3\*30\*24\*60\*60\*1000 \> 2147483647 The problem solved by changing sessionExpiryTime to 20 days and removing the .sessions.json Should we really use 32-bit signed integer for this comparison?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [21 July 2019 11:39 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/14 "2019-07-21T11:39:15Z")
Surely this is a Node-RED bug in that the session handling should trap an input \>32bit - or is that in a dependent library?
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [21 July 2019 12:04 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/15 "2019-07-21T12:04:45Z")
Yes and it was fixed in response to the other thread that has been linked to. Not yet in a published release.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [21 July 2019 13:10 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/16 "2019-07-21T13:10:43Z")
Back to he beach Nick!
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [21 July 2019 14:58 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/17 "2019-07-21T14:58:49Z")
Yes Sir. [https://www.instagram.com/p/B0LrKZynIZv](https://www.instagram.com/p/B0LrKZynIZv)