# 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:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![mu3](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mu3/32/4332_2.png) [@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")

</div>

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?

---

_[View the full topic](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966)._