Upgraded, failed back, now mirror constantly restarts

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

ember1205

Forgive me, but “can’t do” what, exactly?

I have reverted to the exact software, install, and configuration that was in place before running the upgrade by renaming the upgraded directory and then renaming the backed up directory back to the original name. Unless there are files downloaded and stored -outside- of the MagicMirror directory, this should have ensured a complete reversion to the working files.

sdetweil

@ember1205 but I see a current version of node and npm, which would not have been available in 2.13 timeframe…

the old install will not run on the new node and npm , and a new npm install on the old folder