After update, nothing happens.

pi@pi_mirror:~ $ pm2 stop all
[PM2] Applying action stopProcessId on app [all](ids: 0)
[PM2] [mm](0) ✓
┌──────┬──────┬─────────┬───┬─────┬────────┐
│ Name │ mode │ status  │ ↺ │ cpu │ memory │
├──────┼──────┼─────────┼───┼─────┼────────┤
│ mm   │ fork │ stopped │ 0 │ 0%  │ 0 B    │
└──────┴──────┴─────────┴───┴─────┴────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@pi_mirror:~ $ cd ~/MagicMirror__RL1
pi@pi_mirror:~/MagicMirror__RL1 $ git pull origin develop
remote: Enumerating objects: 8, done.
remote: Counting objects: 100% (8/8), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 8 (delta 1), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (8/8), done.
From https://github.com/MichMich/MagicMirror
 * branch            develop    -> FETCH_HEAD
   a4ab0cb..da00c16  develop    -> origin/develop
Updating a4ab0cb..da00c16
Fast-forward
 CHANGELOG.md | 1 +
 js/module.js | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)
pi@pi_mirror:~/MagicMirror__RL1 $ npm install --only=prod

> magicmirror@2.14.0-develop install /home/pi/MagicMirror__RL1
> echo "Installing vendor files ...
" && cd vendor && npm install --loglevel=error

Installing vendor files ...

audited 24 packages in 1.991s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities


> magicmirror@2.14.0-develop postinstall /home/pi/MagicMirror__RL1
> npm run install-fonts && echo "MagicMirror installation finished successfully! 
"


> magicmirror@2.14.0-develop install-fonts /home/pi/MagicMirror__RL1
> echo "Installing fonts ...
" && cd fonts && npm install --loglevel=error

Installing fonts ...

audited 1 package in 1.03s
found 0 vulnerabilities

MagicMirror installation finished successfully! 

audited 1149 packages in 36.561s

16 packages are looking for funding
  run `npm fund` for details

found 1 low severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details
pi@pi_mirror:~/MagicMirror__RL1 $ npm start

> magicmirror@2.14.0-develop start /home/pi/MagicMirror__RL1
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

/home/pi/MagicMirror__RL1/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror__RL1/node_modules/electron/dist/electron)
pi@pi_mirror:~/MagicMirror__RL1 $

sdetweil

@sdetweil the new install used the master branch, so on electron 6. the old folder is on develop, so electron 8.5

sdetweil

@Richard238 ok. 1st time seeing this…

just to make sure
from the old folder
grep version node_modules/electron/package.json

Richard238

@sdetweil said in After update, nothing happens.:

grep version node_modules/electron/package.json

pi@pi_mirror:~/MagicMirror__RL1 $ grep version node_modules/electron/package.json
“type”: “version”,
“version”: “8.5.3”
pi@pi_mirror:~/MagicMirror__RL1 $

sdetweil

@sdetweil one more diag command

lsb_release -a

Richard238

pi@pi_mirror:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
pi@pi_mirror:~ $

sdetweil

@Richard238 ok, thx. problem is new electron won’t run on Jessie anymore…

I don’t know if this will work.

from. the old mm folder

rm -rf node_modules/electron
npm install electron@6.1.12
then npm start

Richard238

@sdetweil said in After update, nothing happens.:

npm install electron@6.1.12

Sam, you’re a genius!

That’s fixed it.
This will only happen again in the not too distant future I’m sure, so would I be better off installing a newer OS?
And then how do I recreate my MM on said new OS?

I’m going to logoff for now, thanks again for your help today.
More tomorrow I’m sure.
Kind regards,
Richard.

sdetweil

@Richard238

copy your MagicMirror folder to save it somewhere
u can zip it to to save space

install buster on your sd card
run the installer to get things setup
restore you MM zip file
erase the node_modules folder
npm install (this should put on the newer electron)
npm start

Richard238

Old MM FTPd to NAS.
Installing new OS now, on a different SD card so I can go back if absolutely necessary.
My plan is to build a new MM as the old one had a lot of clutter - old unused modules etc.
Taking the opportunity for a fresh start. I’ll let you know how it goes…

Richard238

@Richard238 said in After update, nothing happens.:

Old MM FTPd to NAS.
Installing new OS now, on a different SD card so I can go back if absolutely necessary.
My plan is to build a new MM as the old one had a lot of clutter - old unused modules etc.
Taking the opportunity for a fresh start. I’ll let you know how it goes…

14:24
All done.
MM back just as it was with custom CSS, but this time using only the modules installed that I actually need.
MM accessible from any LAN attached device as I don’t have it setup as a mirror anywhere.
The terminal window is showing a constatnt log of what’s happening. Is that correct - I don’t remember it from MM_OLD?

And will the update notification module do anything now, or do I need to do anything?

sdetweil

@Richard238 edit the config.js, there us a new logLevel setting, make sure debug is not included

sdetweil

@Richard238 updatenotification will continue to advise things that have changed…

are u at 2.14 w 8.5 electron?

Richard238

I copied my config.js into the new install, and deleted all the old commented-out module junk I was no longer using.
Added the 'loglevel: [… ’ line, doesn’t yet seem to have made any difference. Reboot required perhaps?

2.14? Package.Json = “version” : “2.14.0”

Electron is 8.5

pi@magicmirror:~/MagicMirror $ grep version node_modules/electron/package.json
  "version": "8.5.5"
pi@magicmirror:~/MagicMirror $