-
Notifications
You must be signed in to change notification settings - Fork 31
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
NR stuck after Admin Update #315
Comments
Is there anything in the logs? Anything in the browser konsole? In fact this screencomes from the node-red UI which has NOTHING in common with Admin or any iobroker things ... we just start a node-re dprocess, rest is done by that one ... |
Absolutely nothing in the logs. As mentioned above, NR adapter even set to debug This is the browser console:
|
May be it helps if you increase the assigned RAM in your Adapter configuration. I increased it to 2048 and had much better performance. |
Thanks for the pointer, unfortunately this does not change anything. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
Since quite a while, I have the issue that the NR adapter suddenly "getting stuck / hangs" at loading the flows:
Already set it to debug, but nothing in the logs. Restarting the NR adapter helps. Also completely removed and reinstalled the NR adapter. Again, after some time it would hang.
Now I found some more context:
Apparently this happens when the Admin updater is updated. As recently there have been many Admin updates, I had many hanging NRs. With the latest update I really could identify it:
The text was updated successfully, but these errors were encountered: