NEWS
Fataler Fehler nach Update (ioBroker Windows)
-
Hi
wollte heute meine ioBroker Version mit Hilfe des Win-Installers auf die neuest Version heben.
Das Upgrade ist leider fehlgeschlagen und ich bekomme seitdem keine Version mehr installiert (Auch ohne Import alter Konfigurationen nicht bzw. Uninstall/Install. Das Windows-Service iobroker scheint in der Service-Liste auch nicht mehr auf.)nodeJS wurde beim ersten Update mitaktualisiert.
Folgendes zeigt das Logfile:
---------------------------------------------------------------------------------------------------- Npm prefix path exists: C:\Users\Superuser\AppData\Roaming\npm ---> OK ---------------------------------------------------------------------------------------------------- Executing: ---------------------------------------------------------------------------------------------------- @echo off SET PATH=C:\Program Files\nodejs;%PATH:&=^&% "C:\Program Files\nodejs\npx" --yes @iobroker/install@latest ---------------------------------------------------------------------------------------------------- Windows installation starting... (fixing = false) NPM version: 10.8.2 npm warn config production Use `--omit=dev` instead. npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 549 packages, and audited 578 packages in 1m 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. Write "iobroker start" to start the ioBroker npm install dotenv@^16.4.5 --force --loglevel error --production --save --prefix "C:/ioBroker" up to date, audited 578 packages in 6s 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. npm install windows-shortcuts@^0.1.6 --force --loglevel error --production --save --prefix "C:/ioBroker" up to date, audited 578 packages in 4s 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements 'winget' is not recognized as an internal or external command, operable program or batch file. Error when installing GIT: Error: Command failed: winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements Register ioBroker as Service Written iobnodevars.bat successfully. Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Command line.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Start ioBroker Service.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Admin.lnk" created! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Stop ioBroker Service.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Restart ioBroker Service.lnk" created with Admin flag! The process cannot access the file because it is being used by another process. Creation of Windows service failed! Starting Windows service failed! ============================= Running Admin shell ============================= ioBroker service name: ioBroker The service name is invalid. More help is available by typing NET HELPMSG 2185. ioBroker service installed and started. Go to http://localhost:8081 to open the admin UI. To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller" ---------------------------------------------------------------------------------------------------- ioBroker installation/fixing completed! ---------------------------------------------------------------------------------------------------- Waiting for ioBroker service ... ioBroker service ioBroker not started (timeout)!Bitte um Tipps, was ich tun könnte?!
Danke
Markus -
Hi
wollte heute meine ioBroker Version mit Hilfe des Win-Installers auf die neuest Version heben.
Das Upgrade ist leider fehlgeschlagen und ich bekomme seitdem keine Version mehr installiert (Auch ohne Import alter Konfigurationen nicht bzw. Uninstall/Install. Das Windows-Service iobroker scheint in der Service-Liste auch nicht mehr auf.)nodeJS wurde beim ersten Update mitaktualisiert.
Folgendes zeigt das Logfile:
---------------------------------------------------------------------------------------------------- Npm prefix path exists: C:\Users\Superuser\AppData\Roaming\npm ---> OK ---------------------------------------------------------------------------------------------------- Executing: ---------------------------------------------------------------------------------------------------- @echo off SET PATH=C:\Program Files\nodejs;%PATH:&=^&% "C:\Program Files\nodejs\npx" --yes @iobroker/install@latest ---------------------------------------------------------------------------------------------------- Windows installation starting... (fixing = false) NPM version: 10.8.2 npm warn config production Use `--omit=dev` instead. npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 549 packages, and audited 578 packages in 1m 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. Write "iobroker start" to start the ioBroker npm install dotenv@^16.4.5 --force --loglevel error --production --save --prefix "C:/ioBroker" up to date, audited 578 packages in 6s 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. npm install windows-shortcuts@^0.1.6 --force --loglevel error --production --save --prefix "C:/ioBroker" up to date, audited 578 packages in 4s 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements 'winget' is not recognized as an internal or external command, operable program or batch file. Error when installing GIT: Error: Command failed: winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements Register ioBroker as Service Written iobnodevars.bat successfully. Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Command line.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Start ioBroker Service.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Admin.lnk" created! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Stop ioBroker Service.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Restart ioBroker Service.lnk" created with Admin flag! The process cannot access the file because it is being used by another process. Creation of Windows service failed! Starting Windows service failed! ============================= Running Admin shell ============================= ioBroker service name: ioBroker The service name is invalid. More help is available by typing NET HELPMSG 2185. ioBroker service installed and started. Go to http://localhost:8081 to open the admin UI. To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller" ---------------------------------------------------------------------------------------------------- ioBroker installation/fixing completed! ---------------------------------------------------------------------------------------------------- Waiting for ioBroker service ... ioBroker service ioBroker not started (timeout)!Bitte um Tipps, was ich tun könnte?!
Danke
Markus -
Hi
wollte heute meine ioBroker Version mit Hilfe des Win-Installers auf die neuest Version heben.
Das Upgrade ist leider fehlgeschlagen und ich bekomme seitdem keine Version mehr installiert (Auch ohne Import alter Konfigurationen nicht bzw. Uninstall/Install. Das Windows-Service iobroker scheint in der Service-Liste auch nicht mehr auf.)nodeJS wurde beim ersten Update mitaktualisiert.
Folgendes zeigt das Logfile:
---------------------------------------------------------------------------------------------------- Npm prefix path exists: C:\Users\Superuser\AppData\Roaming\npm ---> OK ---------------------------------------------------------------------------------------------------- Executing: ---------------------------------------------------------------------------------------------------- @echo off SET PATH=C:\Program Files\nodejs;%PATH:&=^&% "C:\Program Files\nodejs\npx" --yes @iobroker/install@latest ---------------------------------------------------------------------------------------------------- Windows installation starting... (fixing = false) NPM version: 10.8.2 npm warn config production Use `--omit=dev` instead. npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 549 packages, and audited 578 packages in 1m 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. Write "iobroker start" to start the ioBroker npm install dotenv@^16.4.5 --force --loglevel error --production --save --prefix "C:/ioBroker" up to date, audited 578 packages in 6s 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. npm install windows-shortcuts@^0.1.6 --force --loglevel error --production --save --prefix "C:/ioBroker" up to date, audited 578 packages in 4s 72 packages are looking for funding run `npm fund` for details 29 vulnerabilities (22 moderate, 6 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements 'winget' is not recognized as an internal or external command, operable program or batch file. Error when installing GIT: Error: Command failed: winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements Register ioBroker as Service Written iobnodevars.bat successfully. Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Command line.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Start ioBroker Service.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Admin.lnk" created! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Stop ioBroker Service.lnk" created with Admin flag! Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Restart ioBroker Service.lnk" created with Admin flag! The process cannot access the file because it is being used by another process. Creation of Windows service failed! Starting Windows service failed! ============================= Running Admin shell ============================= ioBroker service name: ioBroker The service name is invalid. More help is available by typing NET HELPMSG 2185. ioBroker service installed and started. Go to http://localhost:8081 to open the admin UI. To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller" ---------------------------------------------------------------------------------------------------- ioBroker installation/fixing completed! ---------------------------------------------------------------------------------------------------- Waiting for ioBroker service ... ioBroker service ioBroker not started (timeout)!Bitte um Tipps, was ich tun könnte?!
Danke
Markus@markusma sagte in Fataler Fehler nach Update (ioBroker Windows):
winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements
'winget' is not recognized as an internal or external command,dir fehlt winget, das musst du installieren
https://learn.microsoft.com/de-de/windows/package-manager/winget/ -
@markusma sagte in Fataler Fehler nach Update (ioBroker Windows):
winget install --id Git.Git -e --source winget --silent --force --disable-interactivity --accept-source-agreements --accept-package-agreements
'winget' is not recognized as an internal or external command,dir fehlt winget, das musst du installieren
https://learn.microsoft.com/de-de/windows/package-manager/winget/@oliverio said in Fataler Fehler nach Update (ioBroker Windows):
dir fehlt winget, das musst du installieren
Das auch, das ist aber nicht der Grund für das Problem, dass der Service nicht mehr startet bzw. installiert wird.
@markusma said in Fataler Fehler nach Update (ioBroker Windows):
Bitte um Tipps, was ich tun könnte?!
Ein Fix ist unterwegs, bis da hin kannst du das Problem (hoffentlich) so lösen:
Im ioBroker Cmd Fenster folgendes eingeben:
curl -L --output .\install_test.js --url https://raw.githubusercontent.com/Gaspode69/ioBroker/Gaspode69-Win-Install-Service/install/windows/install.js node install_test.jsansonsten, am Besten den Windows Installer Thread abonnieren, da werden aktuelle Probleme in der Regel als erstes besprochen:
https://forum.iobroker.net/post/958230 -
@oliverio said in Fataler Fehler nach Update (ioBroker Windows):
dir fehlt winget, das musst du installieren
Das auch, das ist aber nicht der Grund für das Problem, dass der Service nicht mehr startet bzw. installiert wird.
@markusma said in Fataler Fehler nach Update (ioBroker Windows):
Bitte um Tipps, was ich tun könnte?!
Ein Fix ist unterwegs, bis da hin kannst du das Problem (hoffentlich) so lösen:
Im ioBroker Cmd Fenster folgendes eingeben:
curl -L --output .\install_test.js --url https://raw.githubusercontent.com/Gaspode69/ioBroker/Gaspode69-Win-Install-Service/install/windows/install.js node install_test.jsansonsten, am Besten den Windows Installer Thread abonnieren, da werden aktuelle Probleme in der Regel als erstes besprochen:
https://forum.iobroker.net/post/958230@gaspode said in Fataler Fehler nach Update (ioBroker Windows):
Ein Fix ist unterwegs
Die Korrektur ist inzwischen Online, d.h. der ioBroker Fixer sollte den Service jetzt wieder korrekt anlegen.
Danke an @apollon77 und @Bluefox für das schnelle releasen der Korrektur.
@mcm1957
Und Danke, dass du mich immer so schnell auf Windows Probleme aufmerksam machst. :) -
@gaspode said in Fataler Fehler nach Update (ioBroker Windows):
Ein Fix ist unterwegs
Die Korrektur ist inzwischen Online, d.h. der ioBroker Fixer sollte den Service jetzt wieder korrekt anlegen.
Danke an @apollon77 und @Bluefox für das schnelle releasen der Korrektur.
@mcm1957
Und Danke, dass du mich immer so schnell auf Windows Probleme aufmerksam machst. :) -
@gaspode said in Fataler Fehler nach Update (ioBroker Windows):
Ein Fix ist unterwegs
Die Korrektur ist inzwischen Online, d.h. der ioBroker Fixer sollte den Service jetzt wieder korrekt anlegen.
Danke an @apollon77 und @Bluefox für das schnelle releasen der Korrektur.
@mcm1957
Und Danke, dass du mich immer so schnell auf Windows Probleme aufmerksam machst. :)@gaspode sagte in Fataler Fehler nach Update (ioBroker Windows):
Die Korrektur ist inzwischen Online, d.h. der ioBroker Fixer sollte den Service jetzt wieder korrekt anlegen.
Super, gerade heruntergeladen. Ist Version gleich geblieben? 3.3.0
Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@gaspode sagte in Fataler Fehler nach Update (ioBroker Windows):
Die Korrektur ist inzwischen Online, d.h. der ioBroker Fixer sollte den Service jetzt wieder korrekt anlegen.
Super, gerade heruntergeladen. Ist Version gleich geblieben? 3.3.0
@sigi234 said in Fataler Fehler nach Update (ioBroker Windows):
Super, gerade heruntergeladen. Ist Version gleich geblieben? 3.3.0
Die Korrektur ist im Script-Teil, der per npx aufgerufen wird, d.h. der Windows Installer hat sich nicht geändert und braucht nicht erneut heruntergeladen zu werden.
Support us
682
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge