instance crashes sporadically after js-controller update 5.0.8 #954
Comments
|
Exactly the same behavior here. |
|
Same here:
|
|
Same here, after Update vom Node v16 to v18 |
|
Same here after... just a new install on Proxmox. My old Pi4- bullseye, with all upgrades until friday works fine with hm-rpc (homematic ip) is current the slave so i have a workaround for me. |
|
same here without docker or proxmox |
|
Very strange all on different node versions and also different controller versions .. currently I have no clue why this happens |
|
But all 3.69.7 on CCU? Did you do an update recently or such? |
|
PS: And a js-controller downgrade fixes the issue again? |
|
for me i have not made an update neither on the ccu nor on the iobroker |
|
The CCU version is indeed the only common thing. In my case the issue started last Friday after upgrading to js-controller 5.0.8 an node.js 18.16.1 with these versions: Even the restore to the backup of the day before hasn't change the behavior, which is really curios because everything was working at this point. So same issue with: It is really bad as the RPC is my most important adapter and the workaround is now a restarting every 15 min by a cron job. |
The only update I made was the js-controller from 5.0.6 to 5.0.8. |
|
Half an hour ago I restarted the CCU (debmatic system) and after that the hm.rega and hm.rpc instances as well. So far no errors in the iobroker log and the hm.rpc instances are running. Can anyone else possibly confirm this? |
|
The error still occurs..... |
|
I think I'm chasing the same error. I added
to ioBroker.hm-rpc/src/main.ts here's the stack of the error:
I'll try to follow the trace and see where this error comes from... |
|
Same here, CCU 3.67.10.20230225 |
|
same here CCU3 3.69.7 |
|
same here
OS: Raspbian |
|
Please disable Sentry. Gruß//Lucky |
|
I can confirm this, after 3h no errors |
|
I can confirm this too. (Thanks! @Lucky-ESA) |
|
Thanks for the feedback we will update the sentry plugin. Maybe there has been an intact version in between |
|
I have the same error on my system (with js-controller 5.0.8). |
i was running latest sentry 7.6.0 while trying to find errors for other adapters but it didn't help. Unfortunately wasn't able to find the point where things get changed, i have their http.js in mind |
|
I could narrow the problem a bit. The error occurs only with Homatic-IP devices. If you start a fresh instance of HM-RPC all devices from the CCU are discovered and entered under "Objects" - BUT only channel 0 could be read from the CCU with all the variables and their states. Even all other channels are discovered and show up under objects - they are all empty. And during the collection / discovery from the ccu the log shows the "Unexpected endLine: 0Column: 0Char:" error. hm-rpc: 1.15.18 Maybe this can help to localize the problem. rejoiced too early - after about 6 houres without any errors, suddenly the HM-RPC instance for HM-RF devices throw this error... |
|
maybe related getsentry/sentry-javascript#8552 |
|
@kago76 why did you close this issue? Is the problem fixed with enabled sentry? |
|
Oh. sorry. I should have asked if I could close the ticket. Yes. No problems with enabled sentry. Running Versions: hm-rpc version: 1.15.19 Should I reopen the ticket? |
|
if it is about issues with sentry enabled AND Node.js 20 (especially) then we need to wait for the next Node.js versio to be relese becaus ethere was a bug that will be fixed in next Node.js 20 version. This issue potentially also hits Node.sj 18 and will be fixed 2 weeks after Nodejs 20 in next Nodejs 18 version too |
|
@kago76 on my system with node 18.17.1 the issue is still active with activated sentry.
I World recommend to reopen the issue until the New nodejs Version is available as @Apollon77 mentioned |
|
node 20.5.1 has been released 2days ago. The fix didn't make it into that release and as far as i see it it would not help anyway. Overseen my message on discord? |
|
2h without problems so far. The only change i do: set the (callback?) adapter port to 49150 in hm-rpc.1 (hm ip). Mein Englisch ist echt zu mies... rpc.1 is meine höchste Instanz, als ich damals dort sentry deaktiviert habe, hat rpc.0 nach 2 Stunden gesponnen. Dort ebenfalls deaktiviert, gibt es mit hm-rega weiter. Das zu damals und weshalb ich die Instanz angebe, Einzige Einstellungsänderung seit dem ist das ich den Adapter-Port gesetzt habe, weil nach einem Systemreboot hm-rpc.1 sich zwar auf verbunden gesetzt hat, aber erste ein Adapter-Restart nach 2-3 Minuten hat eine tatsächliche Verbindung hervorgebracht. Ein ioBroker restart hatte nicht den selben negativen Effekt wie ein vm- oder hostreboot. |
|
same probleme here:
NodeJS Version: v18.18.2 |
|
@ticaki Thanks for your hint. I set the "adapter port" in the configuration to 49150 and did not have any of these errors since then (2 days). As you changed your config long ago: Did this fix your problem permanently? |
This was referenced Dec 19, 2024
|
i have set the port. However, the problem still exists |
No Problem with hm so far. |
|
@EuloTV: Hier eine Liste der Dinge, die das Problem im System eines Freundes behoben haben: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After update iobroker from host version 5.0.6 to 5.0.8 today the hm-rpc instance crashes sporadically.
Iobroker logs shows:
Ping error [iobroker01:hm-rpc.1:a7781d05ba65b12d48a3e7392faac4e6]: Unexpected endLine: 0Column: 0Char:and
Cannot call init: [http://192.168.193.42:12010, ""] Unexpected endLine: 0Column: 0Char:Versions:
The text was updated successfully, but these errors were encountered: