Puppeteer startet nicht mehr

[Homoran]

@jensen sagte in Plötzlich ReferenceError: request is not defined:

Sind die Sachen die hier diskutiert werden auch die Ursache, daß Puppeteer nicht mehr funktioniert?

Was steht denn bei puppetier im (debug-) Log?

[Jensen]

@homoran
Der Adapter startet gar nicht mehr.

[Homoran]

@jensen sagte in Plötzlich ReferenceError: request is not defined:

@homoran
Der Adapter startet gar nicht mehr.

und

@homoran sagte in Plötzlich ReferenceError: request is not defined:

Was steht denn bei puppetier im (debug-) Log?

beim Versuch zu starten?

[Jensen]

@homoran

2024-06-18 09:23:35.235  - info: puppeteer.0 (12032) starting. Version 0.3.0 in C:/ioBroker/node_modules/iobroker.puppeteer, node: v18.19.1, js-controller: 5.0.19
2024-06-18 09:23:35.247  - debug: puppeteer.0 (12032) Additional arguments: []
2024-06-18 09:23:35.253  - error: puppeteer.0 (12032) 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().
2024-06-18 09:23:35.253  - error: puppeteer.0 (12032) unhandled promise rejection: Could not find Chrome (ver. 126.0.6478.61). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
 2. your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
2024-06-18 09:23:35.254  - error: puppeteer.0 (12032) Error: Could not find Chrome (ver. 126.0.6478.61). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
 2. your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
    at ChromeLauncher.resolveExecutablePath (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ProductLauncher.js:295:27)
    at ChromeLauncher.executablePath (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:209:25)
    at ChromeLauncher.computeLaunchArguments (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:89:37)
    at async ChromeLauncher.launch (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ProductLauncher.js:70:28)
    at async PuppeteerAdapter.onReady (C:\ioBroker\node_modules\iobroker.puppeteer\build\main.js:38:20)
2024-06-18 09:23:35.254  - error: puppeteer.0 (12032) Could not find Chrome (ver. 126.0.6478.61). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
 2. your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
2024-06-18 09:23:35.258  - info: puppeteer.0 (12032) terminating
2024-06-18 09:23:35.258  - warn: puppeteer.0 (12032) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-06-18 09:23:35.771  - info: puppeteer.0 (12032) terminating

[Homoran]

@jensen ich hab das mal abgetrennt.

Bitte Threadtitel anpassen

[Jensen]

@Homoran
hier noch ein Log

2024-06-18 09:31:33.525 - info: host.IpsServerWB instance system.adapter.puppeteer.0 started with pid 15660
2024-06-18 09:31:35.556 - debug: puppeteer.0 (15660) Redis Objects: Use Redis connection: 127.0.0.1:9001
2024-06-18 09:31:35.588 - debug: puppeteer.0 (15660) Objects client ready ... initialize now
2024-06-18 09:31:35.589 - debug: puppeteer.0 (15660) Objects create System PubSub Client
2024-06-18 09:31:35.590 - debug: puppeteer.0 (15660) Objects create User PubSub Client
2024-06-18 09:31:35.637 - debug: puppeteer.0 (15660) Objects client initialize lua scripts
2024-06-18 09:31:35.642 - debug: puppeteer.0 (15660) Objects connected to redis: 127.0.0.1:9001
2024-06-18 09:31:35.674 - debug: puppeteer.0 (15660) Redis States: Use Redis connection: 127.0.0.1:9000
2024-06-18 09:31:35.693 - debug: puppeteer.0 (15660) States create System PubSub Client
2024-06-18 09:31:35.694 - debug: puppeteer.0 (15660) States create User PubSub Client
2024-06-18 09:31:35.721 - debug: puppeteer.0 (15660) States connected to redis: 127.0.0.1:9000
2024-06-18 09:31:35.823 - info: puppeteer.0 (15660) starting. Version 0.3.0 in C:/ioBroker/node_modules/iobroker.puppeteer, node: v18.19.1, js-controller: 5.0.19
2024-06-18 09:31:35.833 - debug: puppeteer.0 (15660) Additional arguments: []
2024-06-18 09:31:35.839 - error: puppeteer.0 (15660) 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().
2024-06-18 09:31:35.839 - error: puppeteer.0 (15660) unhandled promise rejection: Could not find Chrome (ver. 126.0.6478.61). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
2024-06-18 09:31:35.840 - error: puppeteer.0 (15660) Error: Could not find Chrome (ver. 126.0.6478.61). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
at ChromeLauncher.resolveExecutablePath (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ProductLauncher.js:295:27)
at ChromeLauncher.executablePath (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:209:25)
at ChromeLauncher.computeLaunchArguments (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:89:37)
at async ChromeLauncher.launch (C:\ioBroker\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ProductLauncher.js:70:28)
at async PuppeteerAdapter.onReady (C:\ioBroker\node_modules\iobroker.puppeteer\build\main.js:38:20)
2024-06-18 09:31:35.840 - error: puppeteer.0 (15660) Could not find Chrome (ver. 126.0.6478.61). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile\.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
2024-06-18 09:31:35.845 - info: puppeteer.0 (15660) terminating
2024-06-18 09:31:35.845 - warn: puppeteer.0 (15660) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-06-18 09:31:36.348 - info: puppeteer.0 (15660) terminating
2024-06-18 09:31:36.432 - error: host.IpsServerWB instance system.adapter.puppeteer.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-06-18 09:31:36.432 - info: host.IpsServerWB Restart adapter system.adapter.puppeteer.0 because enabled

[Jensen]

Ich habe die in den Fehlermeldungen angegebene Installation wiederholt.
npx puppeteer browsers install chrome
Dann habe ich die Verzeichnisse überprüft und festgestellt, daß die vorherige Version unter
C:\Windows\System32\config\systemprofile.cache\puppeteer
lag, aber die neue im Benutzerverzeichnis
C:\Users\blablabla.cache\puppeteer
Dann habe ich den Inhalt vom Benutzerverzeichnis in das Systemverzeichnis kopiert,
und seitdem läuft wieder alles.
Vielleicht hätte eine Neuinstallation des Adapters auch zu diesem Ergebnis geführt, aber ich bin erst mal froh, daß ich wieder Images erzeugen kann, da ich das oft benutze.

[Homoran]

@jensen sagte in Puppeteer startet nicht mehr:

die in den Fehlermeldungen

dafür sind logs da!

[Thomas Braun]

@jensen sagte in Puppeteer startet nicht mehr:

Dann habe ich die Verzeichnisse überprüft und festgestellt, daß die vorherige Version unter
C:\Windows\System32\config\systemprofile.cache\puppeteer
lag, aber die neue im Benutzerverzeichnis
C:\Users\blablabla.cache\puppeteer

npm Kommandos werden immer im cwd (current working directory) ausgeführt. Deswegen ist es wichtig dabei im passenden Verzeichnis zu stehen.

Dann habe ich den Inhalt vom Benutzerverzeichnis in das Systemverzeichnis kopiert,
und seitdem läuft wieder alles.

Macht man nicht, weil da symlinks nicht berücksichtigt werden.

[Homoran]

@thomas-braun sagte in Puppeteer startet nicht mehr:

Windows

[Thomas Braun]

@homoran

Gilt auch für Windooze.