restart loop without error

sdetweil

@efevee said in restart loop without error:

/dev/root 14812720 6866740 7281424 49% /

card is not full…

after the git pull, did u do npm install? and for any modules that have a package.json, do the same in each such module folder (the update script mentioned below does this all for you)

are u willing to try to update to the latest ? (2.9.0) with the new update script
see here https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing

because u have already attempted update, u will need to add force as a parameter on the end of the url
(just like the example with apply)

efevee

@sdetweil said in restart loop without error:

after the git pull, did u do npm install? and for any modules that have a package.json, do the same in each such module folder (the update script mentioned below does this all for you)

I did…

are u willing to try to update to the latest ? (2.9.0) with the new update script
see here https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing

Renamed folder and tried fresh install with another script mentioned on forum but it hanged with “apt-get update” when running as pi user

because u have already attempted update, u will need to add force as a parameter on the end of the url
(just like the example with apply)

Now upgrading to Buster, however have RPi image two weeks before this behaviour started (haven’t done anything inbetween). When buster fails to fix this issue will reimage sd card and either wait till the issue happens again or will force update to refresh MM as you suggest.

sdetweil

@efevee said in restart loop without error:

Renamed folder and tried fresh install with another script mentioned on forum but it hanged with “apt-get update” when running as pi user

was that my new update script?

https://forum.magicmirror.builders/topic/10171/anyone-want-to-try-updated-installer

sometimes the apt-get update takes a while, there is a apt-get upgrade right behind it to actually update the files…
apt-get update just updates the list of potential updates

efevee

Yes.
Was suprised process takes so long especially I have it all upgraded recently:

install starting  - Sun Dec 29 12:57:18 CET 2019
installing on armv7l processor system
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.11 (stretch) Release: 9.11 Codename: stretch
^[[96mUpdating packages ...^[[90m
Get:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB] Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB] Get:3$
apt-get update  completed ok
install starting  - Sun Dec 29 13:23:04 CET 2019
installing on armv7l processor system
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.11 (stretch) Release: 9.11 Codename: stretch
^[[96mUpdating packages ...^[[90m
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB] Hit:3 https://d$
apt-get update  completed ok

sdetweil

@efevee said in restart loop without error:

stretch

stretch is pretty old now… lots of updates

efevee

C’mon… Buster is only for a few months… :)
Nevertheless upgrade at 6%, will let you know how it looks like after it finishes.

sdetweil

@efevee ok, thx…

efevee

Upgraded to buster, took ages, but seems OK, already had two restarts to check if works constantly. Made sd card dump just in case…

pi@magicpi:~ $ pm2 status
┌─────┬────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id  │ name   │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├─────┼────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1   │ mm     │ N/A         │ N/A     │ fork    │ 1541     │ 15h    │ 89   │ online    │ 0%       │ 1.4mb    │ pi       │ disabled │
│ 0   │ pir    │ N/A         │ N/A     │ fork    │ 1515     │ 15h    │ 0    │ online    │ 0%       │ 1.5mb    │ pi       │ disabled │
└─────┴────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

wonder for how long will it work…

sdetweil

@efevee woohoo!.. thanks for the update…

keep an eye on the restarts
│ 1 │ mm │ N/A │ N/A │ fork │ 1541 │ 15h │ 89

efevee

think, yesterday after update was 87, two were done on purpose by me to check if it will bring up mm.

number is so high as I used pm2 resurrect to bring pir & mm sessions back from “old” stretch set-up as I have also upgraded pm2 itself…

will report anything suspicious :)