Skip to content
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

Open
Sineos opened this issue Jul 15, 2022 · 5 comments
Open

NR stuck after Admin Update #315

Sineos opened this issue Jul 15, 2022 · 5 comments

Comments

@Sineos
Copy link

Sineos commented Jul 15, 2022

Since quite a while, I have the issue that the NR adapter suddenly "getting stuck / hangs" at loading the flows:

grafik

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:

  1. NR (v3.3.1) is loading nicely
  2. Updated Admin to 6.2.1
  3. NR stuck
  4. NR restarted --> Works
@Apollon77
Copy link
Contributor

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

@Sineos
Copy link
Author

Sineos commented Jul 15, 2022

Absolutely nothing in the logs. As mentioned above, NR adapter even set to debug
I just reproduced it by downgrading to Admin 6.1.12

This is the browser console:

Diese Seite verwendet die nicht standardisierte Eigenschaft "zoom". Stattdessen sollte calc() in den entsprechenden Eigenschaftswerten oder "transform" zusammen mit "transform-origin: 0 0" verwendet werden. 192.168.178.22:8083
[email protected] bootstrap.jsx:19:8
[2022-07-15T14:56:08.987Z] Try to connect instrument.ts:124:32
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://sentry.iobroker.net/api/58/envelope/?sentry_key=43643152dab3481db69950ba866ee9d6&sentry_version=7. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).
Stored version: , new version: 6.1.12 instrument.ts:124:32
Connected: true instrument.ts:124:32
[ADAPTERS] getAdapters instrument.ts:124:32
[ADAPTERS] getAdaptersInfo instrument.ts:124:32
[ADAPTERS] admin instrument.ts:124:32
[ADAPTERS] getAdapters instrument.ts:124:32
[ADAPTERS] getAdaptersInfo instrument.ts:124:32
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://sentry.iobroker.net/api/58/envelope/?sentry_key=43643152dab3481db69950ba866ee9d6&sentry_version=7. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null). 2
[ADAPTERS] admin instrument.ts:124:32
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://sentry.iobroker.net/api/58/envelope/?sentry_key=43643152dab3481db69950ba866ee9d6&sentry_version=7. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null). 4
JQMIGRATE: Migrate is installed, version 3.3.0 vendor.js:4:711
Node-RED: 2.2.2 red.min.js:16:23891
Versions red.min.js:16:23927
jQuery 3.5.1 red.min.js:16:23962
jQuery UI 1.12.1 red.min.js:16:23995
ACE 1.4.12 red.min.js:16:24045
D3 3.0.3 red.min.js:16:24139
Palette editor disabled red.min.js:16:19573
Projects disabled red.min.js:16:19693
Die Ressource von "http://192.168.178.22:1880/vendor/jquery.fancytree-all.min.js" wurde wegen eines MIME-Typ-Konfliktes ("text/html") blockiert (X-Content-Type-Options: nosniff). 192.168.178.22:1880
Laden fehlgeschlagen für das <script> mit der Quelle "http://192.168.178.22:1880/vendor/jquery.fancytree-all.min.js". 192.168.178.22:1880:1:1
Die Ressource von "http://192.168.178.22:1880/selectID.js" wurde wegen eines MIME-Typ-Konfliktes ("text/html") blockiert (X-Content-Type-Options: nosniff). 192.168.178.22:1880
Laden fehlgeschlagen für das <script> mit der Quelle "http://192.168.178.22:1880/selectID.js". 192.168.178.22:1880:1:1
Source-Map-Fehler: Error: request failed with status 404
Ressourcen-Adresse: http://192.168.178.22:1880/vendor/vendor.js?v=2.2.2
Source-Map-Adresse: purify.min.js.map
[ADAPTERS] getAdapters instrument.ts:124:32
[ADAPTERS] getAdaptersInfo instrument.ts:124:32
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://sentry.iobroker.net/api/58/envelope/?sentry_key=43643152dab3481db69950ba866ee9d6&sentry_version=7. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null). 2
[ADAPTERS] admin instrument.ts:124:32
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://sentry.iobroker.net/api/58/envelope/?sentry_key=43643152dab3481db69950ba866ee9d6&sentry_version=7. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null). 2
system.adapter.admin.0 instrument.ts:124:32
system.adapter.discovery.0 instrument.ts:124:32
system.adapter.fritzbox.0 instrument.ts:124:32
system.adapter.hm-rpc.0 instrument.ts:124:32
system.adapter.influxdb.0 instrument.ts:124:32
system.adapter.modbus.0 instrument.ts:124:32
system.adapter.modbus.1 instrument.ts:124:32
system.adapter.mqtt.0 instrument.ts:124:32
system.adapter.node-red.0 instrument.ts:124:32
system.adapter.solarlog.0 instrument.ts:124:32
system.adapter.sonoff.0 instrument.ts:124:32
system.adapter.sourceanalytix.0 instrument.ts:124:32
system.adapter.viessmann.0 instrument.ts:124:32
system.adapter.wiffi-wz.0 instrument.ts:124:32
system.adapter.yeelight-2.0 instrument.ts:124:32
getInstances: 4 instrument.ts:124:32
Please add to "system.adapter.node-red" common.adminUI={"config":"materialize","tab":"html"} instrument.ts:124:32
system.adapter.admin.0 instrument.ts:124:32
system.adapter.discovery.0 instrument.ts:124:32
system.adapter.fritzbox.0 instrument.ts:124:32
system.adapter.hm-rpc.0 instrument.ts:124:32
system.adapter.influxdb.0 instrument.ts:124:32
system.adapter.modbus.0 instrument.ts:124:32
system.adapter.modbus.1 instrument.ts:124:32
system.adapter.mqtt.0 instrument.ts:124:32
system.adapter.node-red.0 instrument.ts:124:32
system.adapter.solarlog.0 instrument.ts:124:32
system.adapter.sonoff.0 instrument.ts:124:32
system.adapter.sourceanalytix.0 instrument.ts:124:32
system.adapter.viessmann.0 instrument.ts:124:32
system.adapter.wiffi-wz.0 instrument.ts:124:32
system.adapter.yeelight-2.0 instrument.ts:124:32
getInstances: 86 instrument.ts:124:32

@mickym2
Copy link
Contributor

mickym2 commented Jul 30, 2022

May be it helps if you increase the assigned RAM in your Adapter configuration. I increased it to 2048 and had much better performance.

@Sineos
Copy link
Author

Sineos commented Jul 30, 2022

Thanks for the pointer, unfortunately this does not change anything.
In fact, I usually have it set to 3072. The low value comes from me completely uninstalling / deleting every NR related file and completely reinstalling the adapter.
This was my last attempt before filing this ticket here.

@stale
Copy link

stale bot commented May 9, 2023

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.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

@stale stale bot added the wontfix label May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants