A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
Updating did nothing but gave fatal error warning.
-
pi@magicmirror:~ $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" No LSB modules are available. doing test run = true, NO updates will be applied! 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.1.0 Node should be upgraded. Node.js upgrade defered, doing test run Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V7.11.2 Installed npm version: V7.11.2 No npm upgrade necessary. saving custom.css upgrading from version 2.18.0 to 2.19.0 fetching latest revisions there are 5 local files that are different than the master repo config/config.js.sample fonts/package-lock.json modules/default/newsfeed/newsfeed.js package-lock.json vendor/package-lock.json any *-lock.json files do not need to be saved do you want to save these files for later (Y/n)? Checking for modules with removed libraries processing dependency changes for active modules with package.json files processing for module MMM-MysqlQuery please wait ---------------------------------- skipped processing for MMM-MysqlQuery, doing test run processing complete for module MMM-MysqlQuery restoring custom.css test run, restoring files stashed pi@magicmirror:~ $ -
pi@magicmirror:~ $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply 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.1.0 Node should be upgraded. Installing Node.js ... gpg: WARNING: unsafe ownership on homedir '/home/pi/.gnupg' Reading package lists... Done Building dependency tree Reading state information... Done nodejs is already the newest version (17.3.1-deb-1nodesource1). The following package was automatically installed and is no longer required: python-colorzero Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 63 not upgraded. node version is Node.js installation Done! version=v16.1.0 Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V7.11.2 Installed npm version: V7.11.2 No npm upgrade necessary. saving custom.css upgrading from version 2.18.0 to 2.19.0 fetching latest revisions there are 2 local files that are different than the master repo config/config.js.sample modules/default/newsfeed/newsfeed.js do you want to save these files for later (Y/n)? updating MagicMirror runtime, please wait > magicmirror@2.19.0 install > echo "Installing vendor files ... > " && cd vendor && npm install --loglevel=error Installing vendor files ... changed 3 packages, and audited 10 packages in 22s found 0 vulnerabilities > magicmirror@2.19.0 postinstall > npm run install-fonts && echo "MagicMirror² installation finished successfully! > " > magicmirror@2.19.0 install-fonts > echo "Installing fonts ... > " && cd fonts && npm install --loglevel=error Installing fonts ... added 2 packages, removed 1 package, and audited 3 packages in 5s found 0 vulnerabilities MagicMirror² installation finished successfully! > magicmirror@2.19.0 prepare > [ -f node_modules/.bin/husky ] && husky install || echo no husky installed. no husky installed. added 3 packages, removed 4 packages, changed 35 packages, and audited 266 packages in 2m 20 packages are looking for funding run `npm fund` for details found 0 vulnerabilities npm notice npm notice New major version of npm available! 7.11.2 -> 8.6.0 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.6.0> npm notice Run `npm install -g npm@8.6.0` to update! npm notice Checking for modules with removed libraries processing dependency changes for active modules with package.json files processing for module MMM-MysqlQuery please wait ---------------------------------- npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: mmm-mysqlquery@1.0.0 npm ERR! Found: stylelint@8.4.0 npm ERR! node_modules/stylelint npm ERR! dev stylelint@"^8.3.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer stylelint@"14.x" from grunt-stylelint@0.18.0 npm ERR! node_modules/grunt-stylelint npm ERR! dev grunt-stylelint@"latest" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/pi/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-04-08T13_34_50_165Z-debug.log processing complete for module MMM-MysqlQuery restoring custom.css we stashed a set of files that appear changed from the latest repo versions. you should review them see installers/stashed_files for the list you can use git checkout stash@{0} -- filename to extract one file from the stash or git stash pop to restore them all WARNING.. WARNING.. either will overlay the file just installed by the update WARNING.. pi@magicmirror:~ $ -
Then did
pm2 start alland now have a black screen on the Pi, and ‘Unable to connect’ on the desktop browser. :-(
-
@Richard238 not pm2 start all
pm2 status
will show u the defined apps
pm2 start ??
where ?? is the name of the number of the app
(usually 0)pm2 stop all just is a shortcut
pm2 --help shows u all the things it can do.
but the black screen could be because of the module rebuild failure
pm2 logs – lines=100 might show more info
and then there’s this
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-latermy upgrade tries to handle the ones we know about
-
@Richard238 said in Updating did nothing but gave fatal error warning.:
MMM-MysqlQuery
MMM-MysqlQuery seems to be the issue, I’ve commented it out of config .js,
Will that be ok if I try pm2 start again? -
@Richard238 yes
-
OK that’s brought MM back to life, but my custom CSS seems to have been ignored.
That, and I need new weather modules?!
-
@Richard238 you need to change to the new combined weather module…(announced 2 releases ago)
supposedly change the module name field to weather and change the appid field name to apiKey
custom.css should still be there… I save and restore -
custom.css is still there, but the coloured icons I had beside calendar entries are no longer showing.
-
@sdetweil Weather module changes worked.
They needs adjusting, but it is now showing something so it’s a good start I can work from.
