new update/upgrade script, ready for testing

[sdetweil]

@sdetweil and if it is pm2, then show pm2 logs --lines=100
(will have to ctrl-c to get out)

[bobwilliams]

in mm.sh file
cd ~ / MagicMirror
DISPLAY =: 0 npm start

pi@raspberrypi:~ $ pm2 logs mm
[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)

did not quite understand how this is done

[sdetweil]

@bobwilliams ok… do

pm2 stop 0
then

cd ~/MagicMirror
npm start

you should get a bunch of messages

[bobwilliams]

pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@2.9.0 start /home/pi/MagicMirror
sh run-start.sh

pi@raspberrypi:~/MagicMirror $

[sdetweil]

@bobwilliams ok, lets do the upgrade again , now that I fixed the parm…

bash -c  "$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)" force

need force as u have 2.9.0 already, and we are gonna do it again

[bobwilliams]

writes update wait … wait 10 minutes

should it be long?

[sdetweil]

@bobwilliams no longer than before i don’t think

[sdetweil]

@sdetweil do

tail ~/MagicMirror/installers/upgrade.log -n 30

[bobwilliams]

it seems like the mirror is running but does not show in the browser

[sdetweil]

@bobwilliams we were waiting for the upgrade to finish… it does not START the mirror

[bobwilliams]

What do we do?

[sdetweil]

@bobwilliams lets reboot pi

sudo shutdown now -r

[bobwilliams]

continue tomorrow … it’s too late … it’s time to sleep))))

[sdetweil]

@bobwilliams ok…

[sdetweil]

@bobwilliams and one thing to try, is to reinstall again…

mv MagicMirror MagicMirror.save

then use my updated installer

bash -c "$(curl -sL https://www.dropbox.com/s/rlh710ng0zwv3vp/raspberry.sh?dl=0)"

so we can see if the install works, and then work on the update again..

[bobwilliams]

Well, let’s start reinstalling

[bobwilliams]

Installation was successful, but the mirror did not start

[sdetweil]

@bobwilliams can you show me the pm2 logs

[bobwilliams]

no longer, I removed raspbian, and put it all over again …

[bobwilliams]

I think the problem was not in your script, but in my system