Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 3.2 jetzt im Latest!

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    js-controller 3.2 jetzt im Latest!

    This topic has been deleted. Only users with topic management privileges can see it.
    • crunchip
      crunchip Forum Testing Most Active @apollon77 last edited by

      @apollon77 ok, hab mal weiter geblättert im Admin log, 4 min früher,
      ein Auszug,
      jedochch seh im seq keine einzige Meldung... no connection to databases possible
      muss mir das mal in Ruhe genauer ansehen

      2021-02-14 20:46:12.665 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:46:13.884 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:46:13.900 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:46:13.903 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:46:13.906 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
2021-02-14 20:46:38.051 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:46:40.589 - info: socketio.0 (6039) <==Disconnect system.user.admin from ::ffff:10.1.20.164 vis.0
2021-02-14 20:46:43.948 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:46:43.952 - info: host.IoBroker iobroker _restart
2021-02-14 20:46:44.731 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:46:45.502 - warn: weatherunderground.0 (6739) force terminate
2021-02-14 20:46:46.565 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:46:46.575 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:46:46.577 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:46:46.579 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
2021-02-14 20:46:46.733 - info: host.IoBroker instance system.adapter.weatherunderground.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-02-14 20:47:14.474 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:47:16.603 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:47:16.631 - info: host.IoBroker iobroker _restart
2021-02-14 20:47:17.349 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:47:18.893 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:47:18.904 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:47:18.905 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:47:18.907 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
2021-02-14 20:47:26.057 - error: unifi.0 (6522) Error: Login required. Check username and password.
2021-02-14 20:47:43.588 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:47:48.937 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:47:48.942 - info: host.IoBroker iobroker _restart
2021-02-14 20:47:49.723 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:47:51.400 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:47:51.407 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:47:51.409 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:47:51.411 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
2021-02-14 20:48:00.096 - info: host.IoBroker instance system.adapter.dwd.0 started with pid 9005
2021-02-14 20:48:11.651 - info: host.IoBroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-02-14 20:48:15.562 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:48:21.440 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:48:21.460 - info: host.IoBroker iobroker _restart
2021-02-14 20:48:22.477 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:48:24.365 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:48:24.380 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:48:24.387 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:48:24.389 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
2021-02-14 20:48:50.992 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:48:53.409 - info: host.IoBroker instance system.adapter.coronavirus-statistics.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-02-14 20:48:54.429 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:48:54.433 - info: host.IoBroker iobroker _restart
2021-02-14 20:48:55.012 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:48:56.599 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:48:56.607 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:48:56.609 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:48:56.610 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
2021-02-14 20:49:24.274 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:49:25.745 - info: javascript.0 (5438) script.js.common.System.Statusmeldungen.Status_Lichtzählen1: Auslösender Schalter: sonoff.0.Kueche.POWER: true
2021-02-14 20:49:25.790 - info: javascript.0 (5438) script.js.common.System.Statusmeldungen.Status_Lichtzählen1: Text: Buerolicht ,Esstisch ,Kueche ,Sofa
2021-02-14 20:49:25.792 - info: javascript.0 (5438) script.js.common.System.Statusmeldungen.Status_Lichtzählen1: Anzahl Lichter: 19 # davon Lichter an: 4
2021-02-14 20:49:26.628 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:49:26.632 - info: host.IoBroker iobroker _restart
2021-02-14 20:49:27.116 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:49:28.726 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:49:28.732 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:49:28.733 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:49:28.735 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
2021-02-14 20:49:48.141 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:49:58.750 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:49:58.754 - info: host.IoBroker iobroker _restart
2021-02-14 20:49:59.363 - info: host.IoBroker iobroker Starting node restart.js
      apollon77 1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 @crunchip last edited by

        @crunchip Also das wird versucht einen controller zu starten während noch einer läuft.

        crunchip 1 Reply Last reply Reply Quote 0
        • crunchip
          crunchip Forum Testing Most Active @apollon77 last edited by

          @apollon77 sollte aber nicht sein, da ist doch was faul
          denn ich hatte ja wie oben geschrieben, zwecks der main.js auslesen, ein iobroker stop(20:40Uhr) im putty abgesetzt, kurz gewartet(aber nicht kontrolliert, ob noch was läuft), die zwei benötigten Befehle in putty eingegeben und anschliessend iobroker gestartet. Nach rund 5min mit strg c im putty Fenster gestoppt.

          hab das mal stark zusammen gestückelt, auch wenns blöd zu lesen ist, aber ich hoffe man erkennt etwas

          **iobroker per putty gestoppt 20:40
2021-02-14 20:40:26.162 - info: host.IoBroker received SIGTERM
2021-02-14 20:40:37.032 - info: host.IoBroker All instances are stopped.
**ab hier wird von mir iobroker per putty gestartet
2021-02-14 20:40:56.178 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
**ab hier kommen vermehrt, diese  Meldungen
2021-02-14 20:42:57.497 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:42:57.501 - info: host.IoBroker iobroker _restart
**ab hier kackt der simple-api ab
2021-02-14 20:45:33.243 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-14 20:45:33.334 - error: simple-api.0 (5962) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-02-14 20:45:33.352 - error: simple-api.0 (5962) unhandled promise rejection: Cannot read property 'common' of null
2021-02-14 20:45:33.362 - error: simple-api.0 (5962) TypeError: Cannot read property 'common' of null
at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/db-objects-jsonl/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3607:37)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-02-14 20:45:33.365 - error: simple-api.0 (5962) Cannot read property 'common' of null
2021-02-14 20:45:33.624 - info: simple-api.0 (5962) terminating http server on port 8087
2021-02-14 20:45:33.627 - info: simple-api.0 (5962) terminating
2021-02-14 20:45:33.632 - warn: simple-api.0 (5962) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-02-14 20:45:34.674 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2021-02-14 20:45:34.675 - error: host.IoBroker Caught by controller[0]: TypeError: Cannot read property 'common' of null
2021-02-14 20:45:34.676 - error: host.IoBroker Caught by controller[0]: at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/db-objects-jsonl/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3607:37)
2021-02-14 20:45:34.677 - error: host.IoBroker Caught by controller[0]: at runMicrotasks ()
2021-02-14 20:45:34.678 - error: host.IoBroker Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-02-14 20:45:34.684 - error: host.IoBroker instance system.adapter.simple-api.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-02-14 20:45:34.689 - info: host.IoBroker Restart adapter system.adapter.simple-api.0 because enabled
2021-02-14 20:45:39.325 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:45:39.341 - info: host.IoBroker iobroker _restart
2021-02-14 20:45:40.025 - info: host.IoBroker iobroker Starting node restart.js
**ab hier ist es dann die letzte dieser Meldungen
2021-02-14 20:49:58.750 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:49:58.754 - info: host.IoBroker iobroker _restart
2021-02-14 20:49:59.363 - info: host.IoBroker iobroker Starting node restart.js
2021-02-14 20:50:03.249 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-14 20:50:03.275 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-14 20:50:03.277 - info: host.IoBroker hostname: IoBroker, node: v12.20.1
2021-02-14 20:50:03.279 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b48
**ab hier kommen, die send kill Befehle (warum auch immer)
2021-02-14 20:50:17.462 - info: host.IoBroker stopInstance system.adapter.admin.0 send kill signal
2021-02-14 20:50:17.463 - info: host.IoBroker stopInstance system.adapter.alexa2.0 send kill signal
2021-02-14 20:50:17.464 - info: host.IoBroker stopInstance system.adapter.backitup.0 send kill signal
2021-02-14 20:50:17.464 - info: host.IoBroker stopInstance system.adapter.ble.0 send kill signal
2021-02-14 20:50:17.465 - info: host.IoBroker stopInstance system.adapter.broadlink2.0 send kill sig
.
.
.

2021-02-14 20:50:26.391 - info: host.IoBroker instance system.adapter.simple-api.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2021-02-14 20:50:26.449 - info: host.IoBroker instance system.adapter.shuttercontrol.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2021-02-14 20:50:26.751 - info: host.IoBroker instance system.adapter.history.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2021-02-14 20:50:26.752 - info: host.IoBroker All instances are stopped.
2021-02-14 20:50:33.477 - error: host.IoBroker No connection to databases possible, restart
2021-02-14 20:50:33.481 - info: host.IoBroker iobroker _restart
2021-02-14 20:50:33.829 - info: host.IoBroker iobroker Starting node restart.js
** AB da läuft iobroker erst wieder normal

          oder hängt das ganze mit der putty Action zusammen, das da etwas schief gelaufen ist, denn wie schon im anderen Thread geschrieben, kam diese error Meldung in putty am Ende.

          This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which wa                                                   s not handled with .catch(). The promise rejected with the reason:
TypeError: Cannot read property 'common' of null
    at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/db-objects-jsonl/node_m                                                   odules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3607:37)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

^C================================== > LOG REDIRECT system.adapter.logparser.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.logparser.0 => false [system.adapter.logparser.0.logging]
================================== > LOG REDIRECT system.adapter.javascript.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.seq.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.javascript.0 => false [system.adapter.javascript.0.logging]
================================== > LOG REDIRECT system.adapter.seq.0 => false [system.adapter.seq.0.logging]
================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]

          nichts alledem, findet sich im seq keine einzige dieser Meldung (error: host.IoBroker No connection to databases possible, restart)

          apollon77 1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 @crunchip last edited by

            @crunchip zwei befehle?? Haftbedingungen Main.js UND Controller.js gestartet?? Wenn ja ist’s genau das. 😉 nur eins von beiden. - welches ist aber egal ...

            crunchip 1 Reply Last reply Reply Quote 0
            • crunchip
              crunchip Forum Testing Most Active @apollon77 last edited by crunchip

              @apollon77 nein, hatte nur main.js gestartet

              root@IoBroker:/opt/iobroker/node_modules/iobroker.sonoff# cd /opt/iobroker/node_modules/iobroker.js-controller
root@IoBroker:/opt/iobroker/node_modules/iobroker.js-controller# iobroker stop
root@IoBroker:/opt/iobroker/node_modules/iobroker.js-controller# node --prof main.js

              danach in nem 2. putty Fenster iobroker gestartet, nach rund 5min mit strg c im 1. putty Fenster gestoppt, mehr hatte ich nicht gemacht

              da ich keinen Plan hab von der Materie, wollte ich nachfragen, bzw zeigen, was da so gelaufen ist, nicht das am Ende ein vermeintliches Problem mit dem js-controller besteht, oder der "Auslöser" am "node --prof main.js" lag, ansonsten Haken wir das Thema einfach ab😉

              also, ich habe das ganze jetzt nochmal mit der controller.js gemacht, selbige mehrmalige ERROR Meldungen, nachdem ich iobroker gestartet habe

              2021-02-15 10:45:43.408 - info: host.IoBroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-02-15 10:45:48.165 - error: host.IoBroker No connection to databases possible, restart
2021-02-15 10:45:48.169 - info: host.IoBroker iobroker _restart
2021-02-15 10:45:48.856 - info: host.IoBroker iobroker Starting node restart.js
2021-02-15 10:45:50.519 - info: host.IoBroker iobroker.js-controller version 3.2.16 js-controller starting
2021-02-15 10:45:50.530 - info: host.IoBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-02-15 10:45:50.531 - info: host.IoBroker hostname: IoBroker, node: v12.20.2

              im admin log sieht es so aus

              zigbee.0	2021-02-15 10:55:09.194	warn	(18784) Failed to ping 0x7cb03eaa0a047179 Classic A60 W clear - LIGHTIFY
unifi.0	2021-02-15 10:55:06.003	error	(18250) Error: Login required. Check username and password.
wiffi-wz.0	2021-02-15 10:54:35.299	warn	(18543) State "wiffi-wz.0.info.connection" has no existing object, this might lead to an error in future versions
host.IoBroker	2021-02-15 10:54:12.564	error	instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
zigbee.0	2021-02-15 10:54:10.020	warn	(18269) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
zigbee.0	2021-02-15 10:54:10.015	error	(18269) zigbee.0 already running
host.IoBroker	2021-02-15 10:54:08.150	error	instance system.adapter.yeelight-2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
wled.0	2021-02-15 10:54:04.883	error	(18232) Cannot read property 'error' of undefined
wled.0	2021-02-15 10:54:04.881	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
wled.0	2021-02-15 10:54:04.881	error	at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:352:25)
wled.0	2021-02-15 10:54:04.881	error	at process.exit (internal/process/per_thread.js:168:15)
wled.0	2021-02-15 10:54:04.881	error	at process.emit (events.js:314:20)
wled.0	2021-02-15 10:54:04.881	error	at Object.onceWrapper (events.js:421:26)
wled.0	2021-02-15 10:54:04.881	error	at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8620:22)
wled.0	2021-02-15 10:54:04.881	error	at Wled.emit (events.js:314:20)
wled.0	2021-02-15 10:54:04.881	error	at Wled.onUnload (/opt/iobroker/node_modules/iobroker.wled/main.js:97:13)
wled.0	2021-02-15 10:54:04.881	error	(18232) TypeError: Cannot read property 'error' of undefined
wled.0	2021-02-15 10:54:04.877	error	(18232) unhandled promise rejection: Cannot read property 'error' of undefined
wled.0	2021-02-15 10:54:04.874	error	(18232) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
yeelight-2.0	2021-02-15 10:54:04.748	warn	(18243) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
yeelight-2.0	2021-02-15 10:54:04.746	error	(18243) yeelight-2.0 already running
unifi.0	2021-02-15 10:54:04.312	warn	(18250) slow connection to states DB. Still waiting ...
yeelight-2.0	2021-02-15 10:54:03.957	warn	(18243) slow connection to states DB. Still waiting ...
wled.0	2021-02-15 10:54:02.234	warn	(18232) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
wled.0	2021-02-15 10:54:02.229	error	(18232) wled.0 already running
host.IoBroker	2021-02-15 10:54:00.693	error	instance system.adapter.wiffi-wz.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
host.IoBroker	2021-02-15 10:53:59.837	error	instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
wiffi-wz.0	2021-02-15 10:53:59.332	warn	(18206) get state error: Connection is closed.
wiffi-wz.0	2021-02-15 10:53:59.331	warn	(18206) Could not check object existence of state wiffi-wz.0.info.connection: Cannot check object existence of "wiffi-wz.0.info.connection": Connection is closed.
wiffi-wz.0	2021-02-15 10:53:59.330	error	(18206) Cannot check object existence of "wiffi-wz.0.info.connection": Connection is closed.
wiffi-wz.0	2021-02-15 10:53:59.327	error	(18206) Cannot read property 'on' of undefined
wiffi-wz.0	2021-02-15 10:53:59.326	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
wiffi-wz.0	2021-02-15 10:53:59.326	error	at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:352:25)
wiffi-wz.0	2021-02-15 10:53:59.326	error	at process.exit (internal/process/per_thread.js:168:15)
wiffi-wz.0	2021-02-15 10:53:59.326	error	at process.emit (events.js:314:20)
wiffi-wz.0	2021-02-15 10:53:59.326	error	at Object.onceWrapper (events.js:421:26)
wiffi-wz.0	2021-02-15 10:53:59.326	error	at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8607:29)
wiffi-wz.0	2021-02-15 10:53:59.326	error	at Object.adapter_unload [as unload] (/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:59:10)
wiffi-wz.0	2021-02-15 10:53:59.326	error	(18206) TypeError: Cannot read property 'on' of undefined
wiffi-wz.0	2021-02-15 10:53:59.319	error	(18206) unhandled promise rejection: Cannot read property 'on' of undefined
wiffi-wz.0	2021-02-15 10:53:59.318	error	(18206) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
wiffi-wz.0	2021-02-15 10:53:57.918	warn	(18206) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
wiffi-wz.0	2021-02-15 10:53:57.916	error	(18206) wiffi-wz.0 already running
web.0	2021-02-15 10:53:57.827	warn	(18195) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
web.0	2021-02-15 10:53:57.825	error	(18195) web.0 already running
wiffi-wz.0	2021-02-15 10:53:57.477	warn	(18206) slow connection to states DB. Still waiting ...
web.0	2021-02-15 10:53:56.958	warn	(18195) slow connection to states DB. Still waiting ...
vis.0	2021-02-15 10:53:55.292	warn	(18184) slow connection to states DB. Still waiting ...
weatherunderground.0	2021-02-15 10:53:54.180	warn	(18173) slow connection to states DB. Still waiting ...
text2command.0	2021-02-15 10:53:53.261	warn	(18156) slow connection to states DB. Still waiting ...
telegram.0	2021-02-15 10:53:50.482	warn	(18102) slow connection to states DB. Still waiting ...
vis-inventwo.0	2021-02-15 10:53:49.033	warn	(18060) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
vis-inventwo.0	2021-02-15 10:53:49.031	error	(18060) vis-inventwo.0 already running
              apollon77 1 Reply Last reply Reply Quote 0
              • G
                goschi @apollon77 last edited by goschi

                @apollon77 Hi,
                ich habe ein Problem mit dem Start der graphische Oberfläche des“ iobokers admin“ . Habe unter Windows-10 den iobroker installiert. Auf dem Firefox Browser erschien nach der Installation die graphische Oberfläche des iobroker admin. Nachdem ich verschiedene Updates vorgenommen hatte, (z.B. js-controller 3.2) erreichte ich die die graphische Oberfläche nicht mehr.
                Es ist nicht mehr möglich über einen Browser mit der Eingabe von http://192.168.178.xxx:8081 den iobroker admin vom eigenen und keinem anderen PC zu erreichen. Die IP Adressen wurden geprüft, ich kann sie alle anpingen, d.h das Netzwerk ist ok, die Adressen stimmen.
                Dann habe ich versuch, die Viren-Schutzprogramme zu stoppen und auch den iobroker aus-und eingeschaltet. Ein anderer Browser wurde auch schon ausprobiert. Alles ohne Erfolg, dabei hatte es nach der Installation schon mal funktioniert.
                Kann es sein, dass sich die Portadresse 8081 geändert hat?
                oder mir irgend ein Wind-10 Programm den Zugriff verweigert ?
                Auch habe ich festgestellt, dass das Putty Programm die Meldung: Network error: Connection refused bringt, obwohl der Ping auf den anderen PC funktioniert.
                Für ihre Unterstützung wäre ich sehr dankbar.

                arteck apollon77 2 Replies Last reply Reply Quote 0
                • arteck
                  arteck Developer Most Active @goschi last edited by

                  @goschi iobroker stop und dann

                  1 Reply Last reply Reply Quote 0
                  • apollon77
                    apollon77 @crunchip last edited by

                    @crunchip Ehrlich: wenn es auch passiert wenn du nicht dieses Debug zeug sammelst, dann checken wir ... sonst erstmal egal und ich schiebe es darauf 🙂

                    G 1 Reply Last reply Reply Quote 1
                    • apollon77
                      apollon77 @goschi last edited by

                      @goschi Formal ist der Thread hier für controller 3.2 und nicht 3.1 🙂
                      Am Ende ist da irgendwas mit dem Filesystem und windows blockt Zugriff auf File und das gefällt npm nicht ... hat erstmanichts mit dem controller zu tun ... aber ja mal versuchen mit gestopptem iobroker, sonst bitte neuen Thread anlegen oder den 3.1er stable nehmen

                      1 Reply Last reply Reply Quote 0
                      • G
                        goschi @apollon77 last edited by

                        @apollon77 said in js-controller 3.2 jetzt im Latest!:

                        @crunchip Ehrlich: wenn es auch passiert wenn du nicht dieses Debug zeug sammelst, dann checken wir ... sonst erstmal egal und ich schiebe es darauf 🙂

                        ich habe es heraus gefunden: Du musst den Kapasky Internet Security kurz abschalten. Pffensichtlich hat sich dieser quer gestellt. Danke für die Unterstützung .

                        1 Reply Last reply Reply Quote 0
                        • T
                          TechMo last edited by

                          Moin,

                          LetsEncrypt meckert bei mir leider mit 3.2.16:

                          2021-02-17 22:20:12.448  - info: admin.0 (465) https server listening on port 8081
2021-02-17 22:20:12.449  - info: admin.0 (465) Use link "https://localhost:8081" to configure.
2021-02-17 22:20:13.222  - info: admin.0 (465) terminating https server on port 8081
2021-02-17 22:20:13.320  - error: host.iobroker Caught by controller[0]: invalid maintainer contact info: meineMail

                          Habe auch schon verschiedene Mail-Addressen versucht. Hat noch jemand das Problem?

                          apollon77 1 Reply Last reply Reply Quote 0
                          • apollon77
                            apollon77 @TechMo last edited by

                            @techmo "meineMail" ist aber keine gültige email adresse oder?!

                            T 1 Reply Last reply Reply Quote 0
                            • T
                              TechMo @apollon77 last edited by

                              @apollon77 Habe ich ersetzt. Da steht sonst eine normale Mail-Adresse. Und habe auch schon mehrere versucht.

                              apollon77 1 Reply Last reply Reply Quote 0
                              • apollon77
                                apollon77 @TechMo last edited by

                                @techmo Dann zeig mal log mit ner email

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  TechMo @apollon77 last edited by

                                  @apollon77

                                  2021-02-17 22:20:12.448  - info: admin.0 (465) https server listening on port 8081
2021-02-17 22:20:12.449  - info: admin.0 (465) Use link "https://localhost:8081" to configure.
2021-02-17 22:20:13.222  - info: admin.0 (465) terminating https server on port 8081
2021-02-17 22:20:13.320  - error: host.iobroker Caught by controller[0]: invalid maintainer contact info: tbtechmo@gmail.com
                                  apollon77 2 Replies Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 @TechMo last edited by

                                    @techmo BTW: ist der Fehler-log länger?

                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 @TechMo last edited by apollon77

                                      @techmo Und könnte es sein das die E-Mail zur Domain passen muss die du registrierst?

                                      also generell laut greenlock:

                                      • valid email

                                        You MUST set maintainerEmail to a valid address
                                        MX records must validate (dig MX example.com for 'john@example.com')

                                      ok, also der code schaut echt nur das die domain eMX records hat

                                      https://git.rootprojects.org/root/greenlock.js/src/branch/master/utils.js#L70-L79

                                      ... das sollte für gmail.com an sich gegeben sein - es sei denn der kann sie nicht auflösen

                                      PS: Welche node.js version nut? <10.6.0?

                                      T 1 Reply Last reply Reply Quote 0
                                      • T
                                        TechMo @apollon77 last edited by

                                        @apollon77 said in js-controller 3.2 jetzt im Latest!:

                                        https://git.rootprojects.org/root/greenlock.js/src/branch/master/utils.js#L70-L79

                                        ; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> mX gmail.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33437
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;gmail.com.			IN	MX

;; ANSWER SECTION:
gmail.com.		3468	IN	MX	40 alt4.gmail-smtp-in.l.google.com.
gmail.com.		3468	IN	MX	20 alt2.gmail-smtp-in.l.google.com.
gmail.com.		3468	IN	MX	5 gmail-smtp-in.l.google.com.
gmail.com.		3468	IN	MX	30 alt3.gmail-smtp-in.l.google.com.
gmail.com.		3468	IN	MX	10 alt1.gmail-smtp-in.l.google.com.

;; Query time: 22 msec
;; SERVER: fe80::1%2#53(fe80::1%2)
;; WHEN: Fri Feb 19 09:51:09 CET 2021
;; MSG SIZE  rcvd: 161

                                        scheint kein Problem zu sein.
                                        Habe es auch mit einer web.de-Mail versucht.

                                        Bisher ging es auch mit einer mail, die nicht zur domain passt. Dann ging es ja irgendwann mit der alten js.controller-Version nicht mehr und jetzt mit der neuen Version kommt der Fehler.

                                        node.js ist v12.18.3.

                                        Welche version von greenlock ist denn "Standard", also mit welcher funktioniert es, vlt habe ich dort eine zu alte/neue, die da einen Bug hat?

                                        Thomas Braun apollon77 2 Replies Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @TechMo last edited by

                                          @TechMo
                                          Aktualisier mal Node auf die aktuelle 12er-Version. Ich meine da sei was geändert worden.

                                          apollon77 1 Reply Last reply Reply Quote 0
                                          • apollon77
                                            apollon77 @Thomas Braun last edited by

                                            @thomas-braun Die nodejs Frage war nur relevant falls <10.6

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            696
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            70
                                            575
                                            107737
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo