Meldung: "ADAPTER_ALREADY_RUNNING" nach Neustart

[surfer09]

Hallo zusammen,

mir ist vor Kurzem aufgefallen, das nach einem Systemneustart immer diese Meldung ("ADAPTER_ALREADY_RUNNING") bei fast allen Adaptern auftaucht:
Hier mal ein kurzer Auszug aus dem LOG:

2022-01-15 08:36:58.697 - info: host.IO-Broker-Server instance system.adapter.info.0 started with pid 11744
2022-01-15 08:36:59.776 - error: info.0 (11744) info.0 already running
2022-01-15 08:36:59.777 - warn: info.0 (11744) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-01-15 08:37:00.314 - error: host.IO-Broker-Server instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:00.314 - info: host.IO-Broker-Server Restart adapter system.adapter.info.0 because enabled
2022-01-15 08:37:01.798 - info: host.IO-Broker-Server instance system.adapter.hm-rpc.1 started with pid 2232
2022-01-15 08:37:02.514 - info: hm-rpc.1 (2232) starting. Version 1.15.0 in I:/iobroker/node_modules/iobroker.hm-rpc, node: v14.18.1, js-controller: 3.3.22
2022-01-15 08:37:02.568 - info: hm-rpc.1 (2232) xmlrpc server is trying to listen on 0.0.0.0:2010
2022-01-15 08:37:02.568 - info: hm-rpc.1 (2232) xmlrpc client is trying to connect to 192.168.1.100:2010/ with ["http://192.168.1.14:2010","IO-Broker-Server:hm-rpc.1"]
2022-01-15 08:37:02.603 - info: hm-rpc.1 (2232) Connected
2022-01-15 08:37:02.638 - info: hm-rpc.1 (2232) xmlrpc <- listDevices ["IO-Broker-Server:hm-rpc.1"]
2022-01-15 08:37:02.679 - info: hm-rpc.1 (2232) xmlrpc -> 0 devices
2022-01-15 08:37:02.689 - info: host.IO-Broker-Server instance system.adapter.hs100.0 started with pid 11964
2022-01-15 08:37:02.993 - info: hm-rpc.1 (2232) xmlrpc <- newDevices 264
2022-01-15 08:37:03.029 - info: hm-rpc.1 (2232) new HMIP devices/channels after filter: 0
2022-01-15 08:37:03.202 - error: hs100.0 (11964) hs100.0 already running
2022-01-15 08:37:03.203 - warn: hs100.0 (11964) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-01-15 08:37:03.758 - error: host.IO-Broker-Server instance system.adapter.hs100.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:03.758 - info: host.IO-Broker-Server Restart adapter system.adapter.hs100.0 because enabled
2022-01-15 08:37:05.984 - info: host.IO-Broker-Server instance system.adapter.ping.0 started with pid 3520
2022-01-15 08:37:06.674 - info: ping.0 (3520) starting. Version 1.5.0 in I:/iobroker/node_modules/iobroker.ping, node: v14.18.1, js-controller: 3.3.22
2022-01-15 08:37:06.685 - info: host.IO-Broker-Server instance system.adapter.simple-api.0 started with pid 4368
2022-01-15 08:37:07.136 - error: simple-api.0 (4368) simple-api.0 already running
2022-01-15 08:37:07.137 - warn: simple-api.0 (4368) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-01-15 08:37:07.689 - error: host.IO-Broker-Server instance system.adapter.simple-api.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:07.689 - info: host.IO-Broker-Server Restart adapter system.adapter.simple-api.0 because enabled
2022-01-15 08:37:08.710 - info: host.IO-Broker-Server instance system.adapter.simple-api.0 started with pid 11468
2022-01-15 08:37:09.378 - info: simple-api.0 (11468) starting. Version 2.6.2 in I:/iobroker/node_modules/iobroker.simple-api, node: v14.18.1, js-controller: 3.3.22
2022-01-15 08:37:09.429 - info: simple-api.0 (11468) simpleAPI server listening on port 8087
2022-01-15 08:37:09.429 - info: simple-api.0 (11468) Allow states only when user is owner: false
2022-01-15 08:37:09.430 - info: simple-api.0 (11468) http server listening on port 8087
2022-01-15 08:37:10.702 - info: host.IO-Broker-Server instance system.adapter.deconz.0 started with pid 3008
2022-01-15 08:37:11.185 - error: deconz.0 (3008) deconz.0 already running
2022-01-15 08:37:11.743 - error: host.IO-Broker-Server instance system.adapter.deconz.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:11.743 - info: host.IO-Broker-Server Restart adapter system.adapter.deconz.0 because enabled
2022-01-15 08:37:14.280 - info: host.IO-Broker-Server instance system.adapter.mihome-vacuum.0 started with pid 11200
2022-01-15 08:37:14.700 - info: host.IO-Broker-Server instance system.adapter.squeezeboxrpc.0 started with pid 3620
2022-01-15 08:37:15.418 - error: squeezeboxrpc.0 (3620) squeezeboxrpc.0 already running
2022-01-15 08:37:15.419 - warn: squeezeboxrpc.0 (3620) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-01-15 08:37:15.972 - error: host.IO-Broker-Server instance system.adapter.squeezeboxrpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:15.972 - info: host.IO-Broker-Server Restart adapter system.adapter.squeezeboxrpc.0 because enabled
2022-01-15 08:37:18.699 - info: host.IO-Broker-Server instance system.adapter.upnp.0 started with pid 4160
2022-01-15 08:37:19.334 - error: upnp.0 (4160) upnp.0 already running
2022-01-15 08:37:19.335 - warn: upnp.0 (4160) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-01-15 08:37:19.983 - error: host.IO-Broker-Server instance system.adapter.upnp.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:19.983 - info: host.IO-Broker-Server Restart adapter system.adapter.upnp.0 because enabled
2022-01-15 08:37:21.798 - info: host.IO-Broker-Server instance system.adapter.web.0 started with pid 10204
2022-01-15 08:37:22.527 - info: web.0 (10204) starting. Version 3.4.16 in I:/iobroker/node_modules/iobroker.web, node: v14.18.1, js-controller: 3.3.22
2022-01-15 08:37:22.655 - info: web.0 (10204) socket.io server listening on port 8082
2022-01-15 08:37:22.657 - info: web.0 (10204) http server listening on port 8082
2022-01-15 08:37:22.667 - info: host.IO-Broker-Server instance system.adapter.yahka.0 started with pid 11636
2022-01-15 08:37:23.390 - error: yahka.0 (11636) yahka.0 already running
2022-01-15 08:37:23.391 - warn: yahka.0 (11636) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-01-15 08:37:23.942 - error: host.IO-Broker-Server instance system.adapter.yahka.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:23.943 - info: host.IO-Broker-Server Restart adapter system.adapter.yahka.0 because enabled
2022-01-15 08:37:26.683 - info: host.IO-Broker-Server instance system.adapter.yahka.2 started with pid 9348
2022-01-15 08:37:27.282 - error: yahka.2 (9348) yahka.2 already running
2022-01-15 08:37:27.282 - warn: yahka.2 (9348) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-01-15 08:37:27.826 - error: host.IO-Broker-Server instance system.adapter.yahka.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2022-01-15 08:37:27.826 - info: host.IO-Broker-Server Restart adapter system.adapter.yahka.2 because enabled
2022-01-15 08:37:30.342 - info: host.IO-Broker-Server instance system.adapter.info.0 started with pid 7240
2022-01-15 08:37:30.695 - info: host.IO-Broker-Server instance scheduled system.adapter.coronavirus-statistics.0 30 6 * * *
2022-01-15 08:37:30.698 - info: host.IO-Broker-Server instance system.adapter.coronavirus-statistics.0 started with pid 12212
2022-01-15 08:37:31.494 - info: coronavirus-statistics.0 (12212) starting. Version 0.8.7 in I:/iobroker/node_modules/iobroker.coronavirus-statistics, node: v14.18.1, js-controller: 3.3.22
2022-01-15 08:37:33.769 - info: host.IO-Broker-Server instance system.adapter.hs100.0 started with pid 12192
2022-01-15 08:37:34.533 - info: sql.0 (11496) enabled logging of hs100.0.192_168_1_188.power, Alias=false
2022-01-15 08:37:34.677 - info: host.IO-Broker-Server instance system.adapter.fritzbox.0 started with pid 9404

Ich habe mir zuerst nichts dabei gedacht, wollte jedoch mal einmal nachfragen, ob das so okay ist. Das System an sich macht so keine Probleme - nur halt nach dem Neustart erscheinen immer wieder diese Hinweise im LOG.

Systemdata	Bitte Ausfüllen
Hardwaresystem:	NUC
Arbeitsspeicher:	12GB
Festplattenart:	SSD
Betriebssystem:	Windows 10
Nodejs-Version:	14.18.1
NPM-Version:	6.14.15
Installationsart:	Manuell

[Homoran]

@surfer09 sagte in Meldung: "ADAPTER_ALREADY_RUNNING" nach Neustart:

nach einem Systemneustart immer diese Meldung ("ADAPTER_ALREADY_RUNNING") bei fast allen Adaptern auftaucht:

• was ist ein "Systemstart"?
  • wie führst du den aus?
• wirklich immer?
  • das deutet darauf hin, dass bei dem Systemstart" iobroker nicht beendet wird
  • oder dein ioB startet doppelt????

[surfer09]

@homoran: Mit Systemneustart meine ich einen kompletten Neustart vom Windows und somit logischerweise auch vom IOBroker.
Wo kann ich denn nachsehen, ob der IOBroker doppelt startet? Wenn ich den Windows Dienst stoppe, dann komme ich auch nicht mehr auf die Weboberfläche, somit gehe ich davon aus, dass dort nicht noch eine 2. Geschichte irgendwo im Hintergrund läuft. "iobroker status" liefert dann auch die Info, dass er nicht mehr läuft.

[Homoran]

@surfer09 sagte in Meldung: "ADAPTER_ALREADY_RUNNING" nach Neustart:

vom Windows

da kann ich nichts zu beitragen - Sorry