Read the statement by Michael Teeuw here.
Mirror not starting after update
-
@sdetweil
Sorry I didn’t know that, I thought that it were better to save/restore these files. Next time i will answer that question with no. -
@xIExodusIx BUT their presence in the list SHOULD have made you think…
what did I change? and is it still important…
that is why I recommend running the test pass to find those things…
my hope is to never break a running mirror…
-
@sdetweil
Sorry, I thougt they were important so thought it were better to save/restore them.
I never changed anything in them, I can not code, I’m too stupid for coding!
The question will you save tells me they are important otherwise they were maybe orverwritten so it is better to save them.
I did not know that they were KEY-files for each new versions of MM and had (must) to be replaced by new ones.
I never will answer that quesion with yes again.
Now I will start to install my MM from scratch again for get it work. This will be my last attemp. When this does not work this time I will give up my MagicMirror project.Thanks for helping.
-
@xIExodusIx you do not need to start over…
jut use the command I gave to restore the 2 files and do the npm install again
all will be well…
-
@sdetweil
I did that, but my MM won’t show up!
And now it’s to late I already killed my USB-Boot-Stick by writing the working MM-Image from yesterday to it. -
Mirror is running now. I used
cd ~/MagicMirror git checkout package.json git checkout package-lock.json rm -rf node_modules npm run install-mmI didn‘t change anything there but this fixed my main problem.
But I still have this error message when I use pm2 start whatever. But it may be cosmetics…
Thanks for your help one again!
Chris
-
So it’s up and running with MM 2.29.
I think I will never touch it again, only make OS updates/upgrades and nothing else. -
S sdetweil has marked this topic as solved on
