David Godin - Apr 05 23:20:15 signalk-server ru...
Don't know if it’s critical but I see the following in server logs on start. Those are the initial logs.
Apr 05 23:20:15 signalk-server running at 0.0.0.0:[object Object]
Apr 05 23:20:15 [object Object]
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338573 does not fit into a 32-bit signed integer. Timeout duration was set to 1. (Use
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338572 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338569 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338569 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338568 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 05 23:20:15 5 Apr 23:20:15 - [info] Welcome to Node-RED ===================
Apr 05 23:20:15 signalk-server running at 0.0.0.0:[object Object]
Apr 05 23:20:15 [object Object]
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338573 does not fit into a 32-bit signed integer. Timeout duration was set to 1. (Use
node --trace-warnings ... to show where the warning was created)Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338572 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338569 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338569 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 15 10:57:56 (node:4623) TimeoutOverflowWarning: 220105338568 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Apr 05 23:20:15 5 Apr 23:20:15 - [info] Welcome to Node-RED ===================
