Updating did nothing but gave fatal error warning.

Richard238

MM reports being 119 commits behind. OK!
Went to https://docs.magicmirror.builders/getting-started/upgrade-guide.html
Did the suggested backups OK
Went to :~/MagicMirror $ entered git pull && npm install --only=prod --omit=dev

Got this: fatal: Unable to read current working directory: No such file or directory

Looked at sdetweil’s script, not sure from the instructions if it need to be
run from :~/MagicMirror $ or elsewhere?

Thank you.

Richard238

I now have coloured icons in the calendar:

Code now looks like this:

/* Calendar: config.js set to  symbol: 'fa-light fa-calendar', */ 
.calendar .fa-calendar-day {
  color: #00d255 /* 55=Green FF=Blue */
}

/* Calendar: config.js set to  symbol: 'fa-light fa-trash-can', */ 
.calendar .fa-trash  {
  color: #C97F7F /* Brown */
}

mumblebaj

@Richard238 You can run Sam’s script from pretty much anywhere. I usually run it from the MagicMirror folder.

sdetweil

@Richard238 my script is made to run from anywhere… it 'assume’s you are NOT in the MagicMirror folder

so, its simple… open a command prompt and paste…

note that upgrade is a 2 part process… (You wouldn’t want me destroying your work for something u forgot about, right?)

so, 1st run TESTS the ability to apply the update, but makes NO changes to anything running.
it reports… files changed but might be overlayed… etc…
if all is good and u feel comfortable,
then you run it a second time with the ‘apply’ parameter

to actually DO the upgrade process

Richard238

Tried the script, and got this node error:

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.
A Node process is currently running. Can't upgrade.
Please quit all Node processes and restart the update.
running process(s) are
pi 15102 15101 0 Jan08 ? 00:00:00 node ./node_modules/.bin/electron js/electron.js
pi@magicmirror:~ $

sdetweil

@Richard238 right. MagicMirror is running. you have to stop it before u can update

as it appears we need to upgrade node and npm as well…

pm2 stop all

Richard238

@sdetweil And then rerun the script?

sdetweil

@Richard238 yes

Richard238

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:~ $

Richard238

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:~ $

Richard238

Then did

pm2 start all

and now have a black screen on the Pi, and ‘Unable to connect’ on the desktop browser.

SOLVED Updating did nothing but gave fatal error warning.