Read the statement by Michael Teeuw here.
MMM-Fuel black screen
-
@Arzeg also, the particular library is not used in many modules, so would not affect more than 2 or 3 out of hundreds
-
@sdetweil Okay.
Unfortunately, there is still an error with the workaround. I have requested a new API key (which works by calling it from the address bar of a browser) but now I get an error message from the module that the API key has expired.
0|mm | MMM-Fuel: Failed to retrieve prices FetchError: request to https://creativecommons.tankerkoenig.de/json/list.php?lat=51.40488&lng=8.06148&rad=5&type=all&apikey=xxxxxx-xxxxx-xxxxx-xxxxx&sort=dist failed, reason: certificate has expired 0|mm | at ClientRequest.<anonymous> (/home/pi/MagicMirror/modules/MMM-Fuel/node_modules/node-fetch/lib/index.js:1491:11) 0|mm | at ClientRequest.emit (events.js:200:13) 0|mm | at TLSSocket.socketErrorListener (_http_client.js:402:9) 0|mm | at TLSSocket.emit (events.js:200:13) 0|mm | at emitErrorNT (internal/streams/destroy.js:91:8) 0|mm | at emitErrorAndCloseNT (internal/streams/destroy.js:59:3) 0|mm | at processTicksAndRejections (internal/process/task_queues.js:84:9) { 0|mm | message: 'request to ' + 0|mm | 'https://creativecommons.tankerkoenig.de/json/list.php?lat=51.40488&lng=8.06148&rad=5&type=all&apikey=xxxxxxx-xxxxx-xxxxx-xxxxx-xxxxx&sort=dist ' + 0|mm | 'failed, reason: certificate has expired', 0|mm | type: 'system', 0|mm | errno: 'CERT_HAS_EXPIRED', 0|mm | code: 'CERT_HAS_EXPIRED' 0|mm | } -
@Arzeg said in MMM-Fuel black screen:
reason: certificate has expired
i don’t know how to fix that one
that is the server side certificate required to make https: work
there was a bug at one time (4 releases ago) where the runtime(electron) mis handled certificates, but we put a fix in for that
I opened this issue
https://github.com/fewieden/MMM-Fuel/issues/100
also opened on in MM
https://github.com/MichMich/MagicMirror/issues/2924 -
@sdetweil Thanks for your help. How can I check if electron is up to date. Possibly that is where the problem lies
-
@Arzeg we use version 19 in this release
at the commandline do
grep version ~/MagicMirror/node_modules/electron/package.json -
@sdetweil My version is: 6.1.12 how can i update this?
-
@Arzeg eh?
can’t be
should be this
grep version ~/MagicMirror/node_modules/electron/package.json "version": "19.0.15",the release upgrade moved us from 17 to 19 (I am incorrect here, see later posts)
hm… how did u upgrade?
manual or my script?
lets check the package.json requested version
grep \"electron\": ~/MagicMirror/package.json "electron": "^19.0.15" -
@sdetweil said in MMM-Fuel black screen:
the release upgrade moved us from 17 to 19
no, we were already on v19 with release
v2.20.0, now we are onv19.1.0(notv19.0.15) -
@sdetweil ehm … i copied your command:
grep version ~/MagicMirror/node_modules/electron/package.json "version": "6.1.12",But that’s weird, I completely rebuilt the mirror about half a year ago. I can’t imagine that in that time the versions have moved from 6 to 19.
-
@Arzeg weird try this updated
grep version /home/pi/MagicMirror/node_modules/electron/package.json "electron": "^6.1.12"please advise how you upgraded
manual (git pull & npm install )
or automated (my script) -
@sdetweil manual with pull and npm install
-
@Arzeg starting to look like it failed
can u do this
run my script
see https://github.com/sdetweil/MagicMirror_scripts
two passes
with no parameter, I want to see what it says
then with force (instead of the documented apply)
as u have 2.21 installed already and it would normally abort…then I want to see
~/MagicMirror/installers/upgrade.logIt may be too big to post here
you could attach it to the cert issue I opened
or email it to memy same userid at gmail (the userid I posted this message under)
-
@sdetweil
with no params:install log being saved to /home/pi/install.log Installing helper tools ... Updating packages ... [ <=> ] Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v16.9.1 Installed Node version: v16.15.1 No Node.js upgrade necessary. Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V7.11.2 Installed npm version: V8.11.0 No npm upgrade necessary. It seems like MagicMirror is already installed. To prevent overwriting, the installer will be aborted. Please rename the ~/MagicMirror folder and try again.with force:
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force No LSB modules are available. doing test run = false update log will be in /home/pi/MagicMirror/installers/upgrade.log Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v16.9.1 Installed Node version: v16.15.1 No Node.js upgrade necessary. Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V7.11.2 Installed npm version: V8.11.0 No npm upgrade necessary. upgrading from version 2.21.0 to 2.21.0 fetching latest revisions updating MagicMirror runtime, please wait npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer > magicmirror@2.21.0 postinstall > npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully! > " > magicmirror@2.21.0 install-vendor > echo "Installing vendor files ... > " && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier Installing vendor files ... up to date in 2s > magicmirror@2.21.0 install-fonts > echo "Installing fonts ... > " && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier Installing fonts ... up to date in 2s MagicMirror² installation finished successfully! > magicmirror@2.21.0 prepare > [ -f node_modules/.bin/husky ] && husky install || echo no husky installed. husky - Git hooks installed up to date, audited 754 packages in 58s 91 packages are looking for funding run `npm fund` for details 3 moderate severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. Checking for modules with removed libraries require for request in module MMM-Reddit not found in package.json package.json for module MMM-Reddit installing request for module MMM-Reddit npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /home/pi/MagicMirror/modules/MMM-Reddit/node_modules/ajv npm ERR! dest /home/pi/MagicMirror/modules/MMM-Reddit/node_modules/.ajv-s6Phgkfd npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/home/pi/MagicMirror/modules/MMM-Reddit/node_modules/ajv' -> '/home/pi/MagicMirror/modules/MMM-Reddit/node_modules/.ajv-s6Phgkfd' npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-10-02T16_46_07_715Z-debug-0.log processing dependency changes for active modules with package.json files processing for module MMM-Fuel please wait ---------------------------------- npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. added 537 packages, and audited 538 packages in 3m 89 packages are looking for funding run `npm fund` for details found 0 vulnerabilities processing complete for module MMM-Fuel processing for module MMM-Strava please wait ---------------------------------- npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated @stylelint/postcss-markdown@0.36.2: Use the original unforked package instead: postcss-markdown 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 441 packages, and audited 442 packages in 3m 81 packages are looking for funding run `npm fund` for details 2 moderate severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. processing complete for module MMM-Strava processing for module MMM-Todoist please wait ---------------------------------- npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer 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 50 packages, and audited 51 packages in 19s 3 packages are looking for funding run `npm fund` for details found 0 vulnerabilities processing complete for module MMM-TodoistThis was the second time i run the command with force, because at the first time, it stuck for about 30 minutes at the same point
⠸ reify:lodash: timing reify:audit Completed in 125567msso i decided to restart the script with force.
I restartet the mm and it works now! Thanks!
Do you still want to see the upgrade.log?
-
@Arzeg rerun with force again. I JUST uploaded a fix to the parameter order on npm i stall
-
@sdetweil Still works ;-)
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force No LSB modules are available. doing test run = false update log will be in /home/pi/MagicMirror/installers/upgrade.log Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v16.9.1 Installed Node version: v16.15.1 No Node.js upgrade necessary. Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V7.11.2 Installed npm version: V8.11.0 No npm upgrade necessary. (23) Failed writing body upgrading from version 2.21.0 to 2.21.0 fetching latest revisions updating MagicMirror runtime, please wait npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer > magicmirror@2.21.0 postinstall > npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully! > " > magicmirror@2.21.0 install-vendor > echo "Installing vendor files ... > " && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier Installing vendor files ... up to date in 2s > magicmirror@2.21.0 install-fonts > echo "Installing fonts ... > " && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier Installing fonts ... up to date in 2s MagicMirror² installation finished successfully! > magicmirror@2.21.0 prepare > [ -f node_modules/.bin/husky ] && husky install || echo no husky installed. husky - Git hooks installed up to date, audited 754 packages in 55s 91 packages are looking for funding run `npm fund` for details 3 moderate severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. Checking for modules with removed libraries require for request in module MMM-Reddit not found in package.json package.json for module MMM-Reddit installing request for module MMM-Reddit npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /home/pi/MagicMirror/modules/MMM-Reddit/node_modules/ajv npm ERR! dest /home/pi/MagicMirror/modules/MMM-Reddit/node_modules/.ajv-s6Phgkfd npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/home/pi/MagicMirror/modules/MMM-Reddit/node_modules/ajv' -> '/home/pi/MagicMirror/modules/MMM-Reddit/node_modules/.ajv-s6Phgkfd' npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-10-02T17_33_12_018Z-debug-0.log processing dependency changes for active modules with package.json files processing for module MMM-Fuel please wait ---------------------------------- npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. added 537 packages, and audited 538 packages in 2m 89 packages are looking for funding run `npm fund` for details found 0 vulnerabilities processing complete for module MMM-Fuel processing for module MMM-Strava please wait ---------------------------------- npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer npm WARN deprecated @stylelint/postcss-markdown@0.36.2: Use the original unforked package instead: postcss-markdown npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 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 441 packages, and audited 442 packages in 2m 81 packages are looking for funding run `npm fund` for details 2 moderate severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. processing complete for module MMM-Strava processing for module MMM-Todoist please wait ---------------------------------- npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one or more of: dev, optional, peer 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 50 packages, and audited 51 packages in 16s 3 packages are looking for funding run `npm fund` for details found 0 vulnerabilities processing complete for module MMM-Todoistoh, and electron is also now on version 19.1.0
-
@Arzeg I looked into your issue with
Error: Cannot find module 'fs/promises'.I installed the same node version as you
16.15.1and did a fresh install of MagicMirror and MMM-Fuel.The problem does not appear, the module is already available since node 14, see the documentation. https://nodejs.org/dist/latest-v16.x/docs/api/fs.html#promises-api
How did you install nodejs, which versions had you before on this system? How do you run the mirror? I currently assume that you might run the mirror in a way that it picks an older installation of nodejs on your system.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login