new update/upgrade script, ready for testing

BKeyport · Jan 28, 2020, 10:30 PM

Update script not working for MMM-CalendarExt2 update. Is it me or you?

Test run using:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"

seems to walk through modules correctly. Live run

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply

does not.

Upgrade started - Tue Jan 28 14:25:31 PST 2020
system is Linux pihole 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
doing test run = true

saving custom.css
remote name = origin
upgrading from version 2.10.1 to 2.10.1
fetching latest revisions
git fetch rc=0
current branch = master
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   package-lock.json

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	0
	css/save_custom.css

no changes added to commit (use "git add" and/or "git commit -a")
there are 1 local files that are different than the master repo

   package-lock.json

save/restore files selection = n
restoring package-lock.json from repo
skipping restore for package-lock.json, doing test run
test merge result rc='' , if empty, no conflicts
skipping merge, only test run

processing dependency changes for active modules with package.json files
processing for module MMM-CalendarExt2 please wait
----------------------------------
skipped processing for MMM-CalendarExt2, doing test run
processing complete for module MMM-CalendarExt2
processing for module MMM-DarkSkyForecast please wait
----------------------------------
skipped processing for MMM-DarkSkyForecast, doing test run
processing complete for module MMM-DarkSkyForecast
processing for module MMM-DHT-Sensor please wait
----------------------------------
skipped processing for MMM-DHT-Sensor, doing test run
processing complete for module MMM-DHT-Sensor
processing for module MMM-RTSPStream please wait
----------------------------------
skipped processing for MMM-RTSPStream, doing test run
processing complete for module MMM-RTSPStream
processing for module MMM-Remote-Control please wait
----------------------------------
skipped processing for MMM-Remote-Control, doing test run
processing complete for module MMM-Remote-Control
restoring custom.css
removing git alias
Upgrade ended - Tue Jan 28 14:25:40 PST 2020

Upgrade started - Tue Jan 28 14:25:46 PST 2020
system is Linux pihole 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
user requested to apply changes
doing test run = false

saving custom.css
remote name = origin
local version 2.10.1 already same as master 2.10.1
restoring custom.css
removing git alias
Upgrade ended - Tue Jan 28 14:25:47 PST 2020

screen on live run is:

the log will be /home/pi/MagicMirror/installers/upgrade.log
No LSB modules are available.
doing test run = false
update log will be in /home/pi/MagicMirror/installers/upgrade.log

saving custom.css
local version 2.10.1 already same as master 2.10.1
restoring custom.css

sdetweil · Jan 28, 2020, 11:14 PM

@BKeyport gotta be me… I will look at in about 45 minutes, when I get home.

Thx for the report

sdetweil · Jan 29, 2020, 1:22 AM

@sdetweil >local version 2.10.1 already same as master 2.10.1

u are upgrading from/to the same version, so no work is done…

if u want to force it to apply changes (again) then use force as the parm

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force

BKeyport · Jan 29, 2020, 1:22 AM

@sdetweil Correct, but isn’t it supposed to run for modules, too?

sdetweil · Jan 29, 2020, 1:37 AM

@BKeyport not if it’s doing nothing

BKeyport · Jan 29, 2020, 2:43 AM

@sdetweil oh, gotcha.

Then I’ll manually update the module for now - would you be able to add that in at a later time? I’d love to be able to have a quick script to run through my modules and update 'em as they call for updates.

Thanks!

sdetweil · Jan 29, 2020, 3:12 AM

@BKeyport use force. It will do it.

bdream · Jul 3, 2020, 11:07 AM

@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 MagicMirror

looks 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!!!

sdetweil · Jul 3, 2020, 11:27 AM

@bdream something is wrong, 122 restarts 0 uptime.

do

pm2 stop 0
pm2 logs --lines=100

bdream · Jul 3, 2020, 11:35 AM

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