wichtiges UPDATE für controller 7.2.2 im stable

[hioniq42]

Systemdata	Bitte Ausfüllen
Hardwaresystem:	VM on Synology
Arbeitsspeicher:	8GB
Festplattenart:	HDD
Betriebssystem:	Ubuntu
Node-Version:	16.18.1
Nodejs-Version:	16.18.1
NPM-Version:	8.19.2
Installationsart:	Skript
Image genutzt:	Nein

Dear Community,
I recently updated my system to the latest versions of node, nodeJS, JS-Controller, NPM etc. Since then, whenever I start the admin interface in any browser, it crashes the JS controller. The core system comes up again and everything else works fine (Scripts, IOT Integration, VIS, ...). I tried downgrades of the admin adapter, but it didn't help. I also searched the forum and GitHub but could not find anything similiar. Maybe someone out here has an idea.
Thank you!
Florian

[Thomas Braun]

@hioniq42

iobroker stop
iobroker fix
iobroker start

Then please post the output of

iobroker diag

[hioniq42]

@thomas-braun
Thank you for the quick response. I did the stop/fix/start several times before with no luck. This is the output from the diganose command (with stop/fix/start executed right before). Problem is still the same.

======================= SUMMARY =======================
                        v.2022-12-13


Operatingsystem:        Ubuntu 22.04.1 LTS
Installation:           microsoft
Timezone:               Europe/Berlin
User-ID:                1000
X-Server:               true

Pending OS-Updates:     0

Nodejs-Installation:    /usr/bin/nodejs         v16.18.1
                        /usr/bin/node           v16.18.1
                        /usr/bin/npm            8.19.2

ioBroker Core:          js-controller           4.0.24
                        admin                   6.2.23

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Pending iob updates:    1

Active repo(s): stable

Objects:                78677
States:                 73856

Size of iob-Database:

48M     /opt/iobroker/iobroker-data/objects.jsonl
17M     /opt/iobroker/iobroker-data/states.jsonl

I also had a look into the log messages right after calling the admin UI but for me there is no meaningful information except the fact that everything falls into pieces:

2022-12-19 21:34:45.885  - info: unifi.0 (387391) cleaned everything up...
2022-12-19 21:34:45.899  - info: fullybrowser.0 (388048) cleaned everything up...
2022-12-19 21:34:45.911  - info: javascript.0 (384789) Stop script script.js.Aktienkurse
2022-12-19 21:34:45.882  - error: sonnen.0 (386920) States database error: read ECONNRESET
2022-12-19 21:34:45.894  - info: admin.1 (384406) terminating http server on port 8080
2022-12-19 21:34:45.901  - info: simple-api.0 (388366) terminating http server on port 8087
2022-12-19 21:34:45.931  - info: info.0 (387970) cleaned everything up...
2022-12-19 21:34:45.923  - info: hm-rpc.2 (386075) binrpc -> 192.168.x.x:8701/ init ["xmlrpc_bin://192.168.x.x:12001",""]
2022-12-19 21:34:45.900  - info: hm-rpc.3 (386737) binrpc -> 192.168.x.x:2001/ init ["xmlrpc_bin://192.168.x.x:12002",""]
2022-12-19 21:34:45.903  - error: admin.2 (384556) States database error: read ECONNRESET
2022-12-19 21:34:45.943  - error: backitup.0 (388528) States database error: read ECONNRESET

I was wondering if there is a way to change the debug level of an instance through CLI?

thank you so far
Florian

[Homoran]

@hioniq42 warum jetzt hier auf englisch?

[hioniq42]

@homoran
Entschuldigung, das war reine Gewohnheit. Weiter auf deutsch :)

@Thomas-Braun
Mir ist im System-Log (/var/logs/syslog) noch folgendes aufgefallen:

21:34:45 iobroker systemd[1]: iobroker.service: Main process exited, code=dumped, status=11/SEGV

[hioniq42]

So, ein paar neue Erkenntnisse, nachdem ich mich durch die Coredumps gearbeitet habe, wo folgendes zu finden ist:

ProblemType: Crash
Architecture: amd64
Date: Tue Dec 20 11:07:29 2022
DistroRelease: Ubuntu 22.04
ExecutablePath: /usr/bin/node
ExecutableTimestamp: 1667561607
ProcCmdline: iobroker.js-controller
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  iobroker.js-con
 ...

Dass hier zwei Berechtigungsprobleme (Zeile 8&9) bestehen, überrascht mich. Müsste das nicht genau mit iobroker fix behoben werden?

[Thomas Braun]

@hioniq42 sagte in Admin GUI crashes JS Controller:

überrascht mich.

Mich nicht, wenn da mit sudo und/oder vollem root-Account herumgefuhrwerkt wurde.

[hioniq42]

@thomas-braun
Dafür habe ich einen Standard-User "iobroker" und sudo nur bei absoluter Notwendigkeit. Und ist doch auch etwas seltsam, dass dann nur bei der Admin GUI Probleme auftreten, sonst aber alles sauber läuft.

[Homoran]

@hioniq42 sagte in Admin GUI crashes JS Controller:

einen Standard-User "iobroker"

der Systemuser heisst bereits iobroker