Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Fehler nach Update der Script engine

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.0k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.0k

Fehler nach Update der Script engine

Fehler nach Update der Script engine

Scheduled Pinned Locked Moved Unsolved Error/Bug
script engine
2 Posts 2 Posters 139 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • ChaotC Offline
    ChaotC Offline
    Chaot
    wrote on last edited by
    #1

    Ich habe gerade ein Update der Script engine (4.3.3) durchgeführt.
    Unmittelbar nach dem Update kam dieser Eintrag im Log:

    javascript.1	2019-11-22 06:44:08.244	error	(5512) Cannot install open-fin-ts-js-client: 254
    javascript.1	2019-11-22 06:44:08.232	error	npm ERR! /home/iobroker/.npm/_logs/2019-11-22T05_44_08_222Z-debug.log
    javascript.1	2019-11-22 06:44:08.232	error	(5512) npm ERR! A complete log of this run can be found in:
    javascript.1	2019-11-22 06:44:08.229	error	(5512)
    javascript.1	2019-11-22 06:44:08.222	error	npm ERR! enoent
    javascript.1	2019-11-22 06:44:08.222	error	npm ERR! enoent This is related to npm not being able to find a file.
    javascript.1	2019-11-22 06:44:08.222	error	(5512) npm ERR! enoent ENOENT: no such file or directory, access '/opt/iobroker/node_modules/iobroker.javascript/node_modules/xml2js-parser'
    javascript.1	2019-11-22 06:44:08.218	error	(5512) npm ERR! errno -2
    javascript.1	2019-11-22 06:44:08.216	error	npm ERR! path /opt/iobroker/node_modules/iobroker.javascript/node_modules/xml2js-parser
    javascript.1	2019-11-22 06:44:08.216	error	npm ERR! syscall access
    javascript.1	2019-11-22 06:44:08.216	error	(5512) ERR! code ENOENT
    javascript.1	2019-11-22 06:44:08.215	error	(5512) npm
    javascript.1	2019-11-22 06:44:08.108	error	(5512) WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.javascript/node_modules/xml2js-parser
    javascript.1	2019-11-22 06:44:08.103	error	(5512) npm
    host.ioBroker	2019-11-22 06:44:04.379	info	iobroker exit 0
    host.ioBroker	2019-11-22 06:44:03.368	info	iobroker Adapter "javascript" updated
    

    Kann das zusammenhängen?

    ioBroker auf NUC unter Proxmox; VIS: 12" Touchscreen und 17" Touch; Lichtsteuerung, Thermometer und Sensoren: Tasmota (39); Ambiente Beleuchtung: WLED (9); Heizung: DECT Thermostate (9) an Fritz 6690; EMS-ESP; 1 Echo V2; 3 Echo DOT; 1 Echo Connect; 2 Echo Show 5; Unifi Ap-Ac Lite.

    C 1 Reply Last reply
    0
    • ChaotC Chaot

      Ich habe gerade ein Update der Script engine (4.3.3) durchgeführt.
      Unmittelbar nach dem Update kam dieser Eintrag im Log:

      javascript.1	2019-11-22 06:44:08.244	error	(5512) Cannot install open-fin-ts-js-client: 254
      javascript.1	2019-11-22 06:44:08.232	error	npm ERR! /home/iobroker/.npm/_logs/2019-11-22T05_44_08_222Z-debug.log
      javascript.1	2019-11-22 06:44:08.232	error	(5512) npm ERR! A complete log of this run can be found in:
      javascript.1	2019-11-22 06:44:08.229	error	(5512)
      javascript.1	2019-11-22 06:44:08.222	error	npm ERR! enoent
      javascript.1	2019-11-22 06:44:08.222	error	npm ERR! enoent This is related to npm not being able to find a file.
      javascript.1	2019-11-22 06:44:08.222	error	(5512) npm ERR! enoent ENOENT: no such file or directory, access '/opt/iobroker/node_modules/iobroker.javascript/node_modules/xml2js-parser'
      javascript.1	2019-11-22 06:44:08.218	error	(5512) npm ERR! errno -2
      javascript.1	2019-11-22 06:44:08.216	error	npm ERR! path /opt/iobroker/node_modules/iobroker.javascript/node_modules/xml2js-parser
      javascript.1	2019-11-22 06:44:08.216	error	npm ERR! syscall access
      javascript.1	2019-11-22 06:44:08.216	error	(5512) ERR! code ENOENT
      javascript.1	2019-11-22 06:44:08.215	error	(5512) npm
      javascript.1	2019-11-22 06:44:08.108	error	(5512) WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.javascript/node_modules/xml2js-parser
      javascript.1	2019-11-22 06:44:08.103	error	(5512) npm
      host.ioBroker	2019-11-22 06:44:04.379	info	iobroker exit 0
      host.ioBroker	2019-11-22 06:44:03.368	info	iobroker Adapter "javascript" updated
      

      Kann das zusammenhängen?

      C Offline
      C Offline
      cburghardt
      wrote on last edited by
      #2

      @Chaot steht ja in der Meldung: check permissions. Da passen die Rechte nicht. Am einfachsten dürfte es sein, wenn du den fixer laufen lässt.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      Support us

      ioBroker
      Community Adapters
      Donate

      594

      Online

      32.4k

      Users

      81.3k

      Topics

      1.3m

      Posts
      Community
      Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
      ioBroker Community 2014-2025
      logo
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Recent
      • Tags
      • Unread 0
      • Categories
      • Unreplied
      • Popular
      • GitHub
      • Docu
      • Hilfe