Error starting after upgrade

sdetweil

@rmcon said in Error starting after upgrade:

Codename: bullseye
doing test run = true, NO updates will be applied!

this is the test run.

upgrade is a two.part process

everyone puts lots of energy into building their mirrors.

last thing my script needs to do is screw it up.
so test run let’s you get an idea if there are any issues you need to fix BEFORE making any changes

the second run (with the apply parameter)
actually DOES the update.

however, I will NOT upgrade a system already upgraded by default

IF you need to force the upgrade process over the same version, then change the parm apply to force

rmcon

@sdetweil
I did the test upgrade then followed it with the apply parameter.

@rmcon said in Error starting after upgrade:

Upgrade started - Sun Oct 15 18:19:04 PDT 2023
system is Linux raspberrypi 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
user requested to apply changes
doing test run = false

At this point, I think my only option is to try the force option. Worst case scenario, if I can’t revive the current version, I’ll try to remove MM and start fresh. I think I’ve got the important bits saved somewhere else to make the job a little easier.

I really do appreciate your help with this, as it is not my forte.

sdetweil

@rmcon show me the rest of the upgrade.log

sdetweil

@rmcon you can use my backup/restore scripts

https://github.com/sdetweil/MagicMirror-backup-restore

rmcon

@sdetweil
It was in the previous post, about 2/3 of the way down, just below the obnoxiously large text.

@rmcon said in Error starting after upgrade:

Upgrade started - Sun Oct 15 18:19:04 PDT 2023
system is Linux raspberrypi 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
user requested to apply changes
doing test run = false
[96mCheck current Node installation …[0m
[0mNode currently installed. Checking version number.
[0mMinimum Node version: [1mv20.8.0[0m
[0mInstalled Node version: [1mv20.8.0[0m
[92mNo Node.js upgrade necessary.[0m
[96mCheck current NPM installation …[0m
[0mNPM currently installed. Checking version number.
[0mMinimum npm version: [1mV10.1.0[0m
[0mInstalled npm version: [1mV10.1.0[0m
[92mNo npm upgrade necessary.[0m
saving custom.css
remote name = origin
local version 2.25.0 already same as master 2.25.0
restoring custom.css
removing git alias
Upgrade ended - Sun Oct 15 18:19:08 PDT 2023

Also, I appreciate the backup and restore info, will look into that before I move ahead.

sdetweil

@rmcon said in Error starting after upgrade:

local version 2.25.0 already same as master 2.25.0

yes you have to use force instead of apply

rmcon

@sdetweil

Force update complete. MM still not working properly, but it’s something different, which I’ll call progress.

[ERROR] (node:2061) UnhandledPromiseRejectionWarning: Error: Cannot find module ‘fetch’
(Full text below)

I see some answers for ‘node-fetch’ in topic #18055, but I’m not sure if that fix will work on this problem. I’m still digging around, but not seeing this exact problem so far. Thanks.

magicmirror@2.25.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

[15.10.2023 20:57.06.757] [LOG] Starting MagicMirror: v2.25.0
[15.10.2023 20:57.06.798] [LOG] Loading config …
[15.10.2023 20:57.06.803] [DEBUG] config template file not exists, no envsubst
[15.10.2023 20:57.06.851] [LOG] Loading module helpers …
[15.10.2023 20:57.06.884] [LOG] No helper found for module: alert.
[15.10.2023 20:57.07.124] [LOG] Initializing new module helper …
[15.10.2023 20:57.07.126] [LOG] Module helper loaded: updatenotification
[15.10.2023 20:57.07.145] [LOG] No helper found for module: clock.
[15.10.2023 20:57.08.647] [LOG] Initializing new module helper …
[15.10.2023 20:57.08.648] [LOG] Module helper loaded: calendar
[15.10.2023 20:57.08.650] [LOG] No helper found for module: MMM-MonthlyCalendar.
[15.10.2023 20:57.08.651] [LOG] No helper found for module: weather.
[15.10.2023 20:57.11.743] [ERROR] (node:2061) UnhandledPromiseRejectionWarning: Error: Cannot find module ‘fetch’
Require stack:

/home/rmco01/MagicMirror/modules/MMM-Wallpaper/node_helper.js
/home/rmco01/MagicMirror/js/app.js
/home/rmco01/MagicMirror/js/electron.js
/home/rmco01/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js
at node:internal/modules/cjs/loader:1084:15
at Function. (node:electron/js2c/browser_init:2:117419)
at Module._resolveFilename (/home/rmco01/MagicMirror/node_modules/module-alias/index.js:49:29)
at node:internal/modules/cjs/loader:929:27
at Function._load (node:electron/js2c/asar_bundle:2:13327)
at Module.require (node:internal/modules/cjs/loader:1150:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object. (/home/rmco01/MagicMirror/modules/MMM-Wallpaper/node_helper.js:11:15)
at Module._compile (node:internal/modules/cjs/loader:1271:14)
at Object…js (node:internal/modules/cjs/loader:1326:10)
at Module.load (node:internal/modules/cjs/loader:1126:32)
at node:internal/modules/cjs/loader:967:12
at Function._load (node:electron/js2c/asar_bundle:2:13327)
at Module.require (node:internal/modules/cjs/loader:1150:19)
at require (node:internal/modules/cjs/helpers:110:18)
at loadModule (/home/rmco01/MagicMirror/js/app.js:180:19)

(removed remainder, same spam messages as previous)

sdetweil

@rmcon said in Error starting after upgrade:

Cannot find module ‘fetch’
Require stack:

/home/rmco01/MagicMirror/modules/MMM-Wallpaper/node_helper.js

yes we removed some libs as fetch is built-in in node 18 up.

that module has a fix

go to the MMM-Wallpaper folder (check spelling)
git pull
to update

then restart mm

rmcon

@sdetweil
We’re up and running! Thank you so much for your patience. I have learned a lot from this go round and I’m hoping that the next update will go much smoother. I still don’t fully understand how to check the test run for compatibility with my configuration before applying the changes, but I have a little time to get smarter before the next update. Have a great rest of your week.

sdetweil

@rmcon great that you got it working

on the test run, mostly currently it’s looking for mm files you might have changed for some reason, and conflict w the new release.

most of the other issues I handle, upgrade node, npm and pm2 if needed.

and in this release on pi0, increase swap space and increase the node heap space.