-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delay in Instance Status Updates at Driver-Level #1949
Comments
Need to check if in staging when we deploy |
verified this isn't an issue on Staging, but is still a problem locally. Downgrading the priority label |
Debugging with Nick, tracked down to |
Tracked to status polling trying to reach an ipv6 address, rather than localhost:
|
We need to check settings.js to see what it's binding to. We've run into this on normal Node-RED recently (I'll try and find the issue I discussed it with DCJ in ) |
This was a WebSockets issue, but it feels the same: It's down to how newer versions of NodeJS order DNS results and I think NR defaults to binding to And the OS returns both |
Forgot to mention I'm running node v18, Nick was on an older version, and also concluded this was a Node version issue. |
I can think of 2 fixes for this
|
I have verified (with Ben) that 1. does fix the issue for me locally. |
Current Behavior
In reviewing #1926 I have significant delays (> 5 minutes) of retrieving status updates. This seems to be happening at the
localfs
driver level, rather than linked to polling - @Pezmc and I were logging inside theliveState()
function found in/forge/db/models/Project.js
and this will[ regualrly reporting "starting" as the status, despite the Node-RED logs reporting "started flows" around 5 minutes ago.Expected Behavior
The status should be reflected to it's Live condition.
Steps To Reproduce
Restart an instance of Node-RED within FlowForge, when running the
localfs
driverEnvironment
The text was updated successfully, but these errors were encountered: