Error starting after upgrade

wwats

No, unfortunately not. i see:

sdetweil

d

to delete it

then node -v

wwats

@sdetweil ok i did. I still have version 16.13.1 :-(
Am I perhaps in the wrong directory?
I have to run the script in the lowest directory directly at pi@raspberrypi:~ $, right?

sdetweil

@wwats try this from the n info

Remove the installed Node.js (does not affect the cached versions). This can be useful to revert to the system version of node (if in a different location)

sudo n prune
sudo n uninstall

wwats

@sdetweil ok this was sucessfull… and what do I have to do now? reinstall? How?
Thank you very much and sorry, I’m not an IT specialist…

sdetweil

@wwats and what does
node -v
show now?

wwats

@sdetweil

pi@raspberrypi:~ $ node -v
-bash: /usr/local/bin/node: Datei oder Verzeichnis nicht gefunden

sdetweil

@wwats can u do

ls -laF /usr/local/bin/node

wwats

@sdetweil no… :
pi@raspberrypi:~ $ ls -laF /usr/local/bin/node
ls: Zugriff auf ‘/usr/local/bin/node’ nicht möglich: Datei oder Verzeichnis nicht gefunden

sdetweil

@wwats ok, try this

which node

on my desktop returns

/usr/local/bin/node

and there is a file there…

wwats

@sdetweil i’m very sorry but i don’t understand this and what i have exactly to do… Can you explain it in a different way?

sdetweil

@wwats

type the command

which node

and show the output

wwats

@sdetweil
ok i understand - output is
/usr/bin/node

maybe is this important: i work directly on my raspberry with ssh

sdetweil

@wwats ok, lets run this

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

wwats

@sdetweil
Everything works :thumbs_up: :thumbs_up: ! Thank You very much - so the mirror is running again. Can I something do for You?

sdetweil

@wwats said in Error starting after upgrade:

Can I something do for You

no… i just like to help…

wwats

@sdetweil said in Error starting after upgrade:

@wwats said in Error starting after upgrade:

Can I something do for You

no… i just like to help…

thank you so much :folded_hands_light_skin_tone:

rmcon

Sam,

I’m having similar problems since the recent upgrade. Big disclaimer here that I’m also not the savviest with technology, but was able to get the MM up and running with 95% of what I envisioned and I’m adventurous enough to try and find solutions before asking questions.

I have been searching and attempting various ways to fix my issues, which I fear may have made this more complex to solve (i.e. attempted to reinstall the newest upgrades both using your script and manually, everything I found short of using the “force” option). My previous attempts have been working directly on the Pi with keyboard, currently attempting via SSH with same results so far.

I’m at a crossroads in my mind now and I’m hoping you can provide steering. Have I gunked this up so much that I should remove and reinstall MM (keeping copes of the previously working config.js, custom.css, and modules folders that I saved on the Pi desktop to try and make the reinstall easier) or can this be fixed? Second concern is that now I’m very hesitant to attempt future upgrades after dealing with this issue (and being far beyond my own capabilities). Any tips or tricks to avoid this in the future?

I tried the steps above in this thread with the following results:

“n” and “nvm”, got messages that “command not found” (both in the main folder and MM folder)
“sudo n prune” and “sudo n uninstall”, similar message “sudo n: command not found” (both in main and MM folders)
“node -v” gave me “v20.8.0” (I have ran your script for the node update several times now)
“ls-laf…” method to find the usr/bin location didn’t work (“no such file or directory”, both main and MM folders attempted), but “which node” DID work, showed “/usr/bin/node”

Just re-ran the script you linked above and still seeing the same results, posted below. (I used “npm start”, was using pm2 to auto start MM before the upgrade.)

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

[10.10.2023 03:10.39.346] [LOG] Starting MagicMirror: v2.25.0
[10.10.2023 03:10.39.359] [LOG] Loading config …
[10.10.2023 03:10.39.371] [DEBUG] config template file not exists, no envsubst
[10.10.2023 03:10.39.384] [LOG] Loading module helpers …
[10.10.2023 03:10.39.391] [LOG] No helper found for module: alert.
[10.10.2023 03:10.39.463] [LOG] Initializing new module helper …
[10.10.2023 03:10.39.465] [LOG] Module helper loaded: updatenotification
[10.10.2023 03:10.39.473] [LOG] No helper found for module: clock.
[10.10.2023 03:10.39.490] [ERROR] (node:26678) UnhandledPromiseRejectionWarning: Error: Cannot find module ‘digest-fetch’
Require stack:

/home/rmco01/MagicMirror/modules/default/calendar/calendarfetcher.js
/home/rmco01/MagicMirror/modules/default/calendar/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/default/calendar/calendarfetcher.js:9:16)
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 Object. (/home/rmco01/MagicMirror/modules/default/calendar/node_helper.js:9:25)
(Use electron --trace-warnings ... to show where the warning was created)
[10.10.2023 03:10.39.492] [ERROR] (node:26678) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[26678:1010/031040.523164:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information

I understand that the weblink and MESA-LOADER messages are from some relegated elements which aren’t around anymore and just nuisance messages.

My previous efforts were trying to find a solution to the “digest-fetch” module, since that appears to be the main problem that I see. I have previously attempted to fix the “envsubst” debug message using guidance in other threads, which either didn’t work, or has been undone by my repeated attempts to solve this problem.

Apologies for the long and rambling note, just wanted to give as much detail that may be useful. Thank you!

sdetweil

@rmcon said in Error starting after upgrade:

Cannot find module ‘digest-fetch’

this is the prior release code

which means you didn’t run the upgrade

either my script or the manual upgrade

note my script is 2 part, test and run a second time w a parameter to actually do the upgrade

rmcon

@sdetweil

I’m a little confused regarding the two separate scripts. I thought the updates were necessary, not optional and didn’t understand why would there be a test run script if the changes need to be applied. In other words, I figured the first script that doesn’t actually apply changes was just extra effort… Is the intent to make sure the update works with the user’s specific MM configuration?

I tried the trial run the first time and I don’t recall if I could tell there were any changes, so I tried the second script to actually make changes.

So, I just tried running the “test” script again, the one thing I did differently is to say “No” when asked if I wanted to keep 23 files that are different than the master (last time I said “Yes”).

Just tried starting MM again, getting the same error. Since the test run didn’t give me any better results, I went ahead and tried the script to apply changes. Same result as before.

The current version is 2.25.0, right? I see that stated in the terminal window:
rmco01@raspberrypi:~/MagicMirror $ npm start

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

[10.10.2023 19:39.57.465] [LOG] Starting MagicMirror: v2.25.0
[10.10.2023 19:39.57.476] [LOG] Loading config …
[10.10.2023 19:39.57.485] [DEBUG] config template file not exists, no envsubst
[10.10.2023 19:39.57.495] [LOG] Loading module helpers …
[10.10.2023 19:39.57.507] [LOG] No helper found for module: alert.
[10.10.2023 19:39.57.568] [LOG] Initializing new module helper …
[10.10.2023 19:39.57.569] [LOG] Module helper loaded: updatenotification
[10.10.2023 19:39.57.578] [LOG] No helper found for module: clock.
[10.10.2023 19:39.57.592] [ERROR] (node:7168) UnhandledPromiseRejectionWarning: Error: Cannot find module ‘digest-fetch’
Require stack:

/home/rmco01/MagicMirror/modules/default/calendar/calendarfetcher.js
/home/rmco01/MagicMirror/modules/default/calendar/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

(remainder truncated since it appears to be the same as previously reported)

Is there some other step that I’m missing? When you say “run a second time w a parameter to actually do the upgrade,” the parameter you’re referring to is “apply” at the end of the link/script, correct? Or am I supposed to do something else in MM or the config file to make it take effect?