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).
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.
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
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)
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.
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.
@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.
