Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
@sdetweil
Hi Sam! I run your update script an my Pi0
Seems it works fine :ok_hand: but my screen show up only the standard Raspian Desktop :crying_face:pm2 restart MagicMirrorlooks good
[PM2] Applying action restartProcessId on app [MagicMirror](ids: 0) [PM2] [MagicMirror](0) ✓ ┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐ │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ ├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤ │ 0 │ MagicMirror │ default │ 2.12.0 │ fork │ 19770 │ 0s │ 122… │ online │ 0% │ 2.5mb │ pi │ enabled │ └─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘what is I’m doing wrong?
Many thanks!!!
-
-
here is
pi@RasPiZeroW:~/MagicMirror $ pm2 logs --lines=100 [TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option) /home/pi/.pm2/pm2.log last 100 lines: PM2 | 2020-07-03T13:25:00: PM2 log: App [MagicMirror:0] exited with code [1] via signal [SIGINT] PM2 | 2020-07-03T13:25:00: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2020-07-03T13:25:01: PM2 log: App [MagicMirror:0] online : : PM2 | 2020-07-03T13:28:36: PM2 log: [Watch] Stop watching MagicMirror PM2 | 2020-07-03T13:28:36: PM2 log: Stopping app:MagicMirror id:0 PM2 | 2020-07-03T13:28:37: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2020-07-03T13:28:37: PM2 log: pid=29676 msg=process killed/home/pi/.pm2/logs/MagicMirror-out.log last 100 lines: 0|MagicMir | 0|MagicMir | > magicmirror@2.12.0 start /home/pi/MagicMirror 0|MagicMir | > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js 0|MagicMir | 0|MagicMir | : :/home/pi/.pm2/logs/MagicMirror-error.log last 100 lines: 0|MagicMir | npm ERR! errno ENOENT 0|MagicMir | npm ERR! magicmirror@2.12.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js` 0|MagicMir | npm ERR! spawn ENOENT 0|MagicMir | npm ERR! 0|MagicMir | npm ERR! Failed at the magicmirror@2.12.0 start script. 0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 0|MagicMir | 0|MagicMir | npm ERR! A complete log of this run can be found in: 0|MagicMir | npm ERR! /home/pi/.npm/_logs/2020-07-03T11_27_39_492Z-debug.log 0|MagicMir | sh: 1: ./node_modules/.bin/electron: not found 0|MagicMir | npm ERR! code ELIFECYCLE 0|MagicMir | npm ERR! syscall spawn 0|MagicMir | npm ERR! file sh 0|MagicMir | npm ERR! errno ENOENT 0|MagicMir | npm ERR! magicmirror@2.12.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js` 0|MagicMir | npm ERR! spawn ENOENT 0|MagicMir | npm ERR! 0|MagicMir | npm ERR! Failed at the magicmirror@2.12.0 start script. 0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 0|MagicMir | : : 0|MagicMir | 0|MagicMir | npm ERR! A complete log of this run can be found in: 0|MagicMir | npm ERR! /home/pi/.npm/_logs/2020-07-03T11_28_26_351Z-debug.log -
@bdream hm. looks like my upgrade script failed to restore the start script change
edit package.json
change the start line to"start": "./run-start.sh",then
pm2 flush pm2 start 0I see the bug, but am on my phone right now and will have to fix it later
-
@sdetweil it dose not work
if I change to
"start": " ./run-start.sh",also as
"start": "DISPLAY=\"${DISPLAY:=:0}\" ./run-start.sh",I get an web explorer showing an error
ERR_CONNECTION_REFUSEDlocalhos refused connection.
-
@bdream notice the 1st has a space in front of the ./, I edited that space out
-
@bdream also. let’s try this
stop everything
then
cd ~/MagicMirror npm run serverthe server side should start.
-
@sdetweil said in new update/upgrade script, ready for testing:
space in front of the ./,
That is also not helpful
@sdetweil said in new update/upgrade script, ready for testing:
stop everything
How to stop everything?
Is this enough?pm2 stop 0 -
@sdetweil said in new update/upgrade script, ready for testing:
npm run server
I get this:
pi@RasPiZeroW:~ $ cd MagicMirror/ pi@RasPiZeroW:~/MagicMirror $ npm run server > magicmirror@2.12.0 server /home/pi/MagicMirror > node ./serveronly internal/modules/cjs/loader.js:638 throw err; ^ Error: Cannot find module 'proxy-addr' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15) at Function.Module._load (internal/modules/cjs/loader.js:562:25) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/pi/MagicMirror/node_modules/express/lib/utils.js:22:17) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! magicmirror@2.12.0 server: `node ./serveronly` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the magicmirror@2.12.0 server script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2020-07-03T13_58_48_248Z-debug.log -
@bdream I have opened issue
https://github.com/MichMich/MagicMirror/issues/2069I cannot debug more myself at this time. in hospital, sorry
-
@sdetweil Sam! You are in hospital :face_with_head-bandage:
So you have to focus on yourself!
Wish you all the best and fast recovery!
Hope you are back soon! -
@bdream knee replacement. lots of sitting around and exercising! just not near my computer system
-
@sdetweil sounds hard to you. far away from your computer.
near time you have to walk and walk all will go as before and better.
All the best! -
@bdream if u rename the mm folder to mm. save and the reinstall does it work?
-
i fixed the upgrade script… if u wanted to force use it again, use “force” instead of “apply”
let me know how it goes
-
@sdetweil Get well soon!
-
A couple of quick questions…
-
The “UpdateNotification” module is able to detect that there is a new version of MM available. Is this logged somewhere or easily accessible from the command line? I’m interested in writing a script that can assess the new version, possibly run a ‘test upgrade’ and then send me a IFTTT or pushover notification that a new version is available and an upgrade test succeeded (or failed).
-
Is the new upgrade script bundled with MM yet? I thought that was the intent, but did not see it up through 2.10.x
-
-
@ember1205 the scripts were removed from the mm base. I maintain them on my github page https://github.com/sdetweil/MagicMirror_scripts
the update cycle is 90days, 1st of the month
if u look at my upgrade-script I check the versions using curl, line 173
-
@sdetweil said in new update/upgrade script, ready for testing:
Where’s a good place to discuss the scripts? I’m wondering how feasible and useful it might be to add to the upgrade-script.sh one.
-
@ember1205 you could create an issue on the repo
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