Upgraded, failed back, now mirror constantly restarts

ember1205

My MM install has been running reasonably well for a while and I have not pushed any updates to it in probably 18 months. I recently applied the most recent updates for Raspbian and things were still running correctly for maybe around a week.

Yesterday, I decided I was going to attempt an upgrade using one of the scripts. So, I did an rsync of the running directory to a second directory on the local device then ran the upgrade script.

Upon starting the mirror, it started complaining about an out-of-date module (MMM-ImagesPhotos). That module wasn’t installed from the original source, so updating it was not going to be something I could do without a bunch of research. So, I stopped the mirror, did an rm-rf on the MM directory, then renamed the backup directory back to its original name.

I -thought- it was running properly, but today it keeps restarting Chromium browser every minute or two. Where do I even begin?

ember1205

After a LOT of different attempts at upgrades, fail-backs, new installs, etc., I believe I finally corrected the issue…

It appears that PM2 was either somehow corrupted during an update attempt or just simply too far out of date. Attempting to run PM2 with certain command options (like stop or even status) was resulting in errors indicating some sort of circular reference. After doing a forced upgrade to the latest version, it stopped showing these errors and the mirror is to running as expected.

I did make some additional changes that include copying the core MM directory off to another linux host where I now run the mirror as a server. The RPi is now purely a client and it loads noticeably quicker as a result.

sdetweil

@ember1205

look for the messages output from npm start
if using pm2 then pm2 logs --lines will show them

restart likely means pm2, as thats its job. keep app running
you could have kept the new folder too…

i would have liked to see the upgrade log…

ember1205

Error on my part… I still have the upgraded directory.

There is no info from the logs that I can tell that shows any sort of crash or anything. And the line from the npm logs just shows the run-start.sh command.

sdetweil

@ember1205 what device is this? p0?

the upgrade log is MagicMirror/installers/upgrade.log

also show output of
uname -a

ember1205

pi 3B+

uname -a output

Linux raspberrypi 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux

How do I post the log? Far too large to go into a post, and isn’t a support file type to attach.

sdetweil

@ember1205 email to me…

same userid at gmail

ember1205

Email sent…

sdetweil

@ember1205 how did u restore the changes to package.json? the script stashed the old package.json file so that the upgrade could continue

ember1205

Umm… git stash pop?

I renamed the upgraded install to “MM-Upgraded” and then renamed my copied directory back to “MagicMirror”. Neither of them works properly at this point and the copied directory was never touched during the upgrade process.

sdetweil

@ember1205 ok, can’t do that… poackage.json is version specific

u might not need it as that run-start.sh was for older configs…
restore with
git checkout package.json

MMM-ImagesPhotos update was because of the missing request lib… removed in 2.16 (you were on 2.13)

I dont see anything else in the upgrade that should be problematic…

try with the default package.json