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 :)
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…
C’mon… Buster is only for a few months… :)
Nevertheless upgrade at 6%, will let you know how it looks like after it finishes.
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 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.
Official RPi script, however some time ago (two or three MM versions ago)
From “strange” tweaks I only have only log2ram to extend SD card life:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 14812720 6866740 7281424 49% /
devtmpfs 342320 0 342320 0% /dev
tmpfs 473904 0 473904 0% /dev/shm
tmpfs 473904 6576 467328 2% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 473904 0 473904 0% /sys/fs/cgroup
log2ram 40960 328 40632 1% /var/log
tmpfs 30720 0 30720 0% /home/pi/.pm2/logs
tmpfs 51200 4 51196 1% /tmp
/dev/mmcblk0p1 42137 22855 19282 55% /boot
tmpfs 51200 4 51196 1% /var/hdd.log
tmpfs 94780 0 94780 0% /run/user/1000
tmpfs 94780 0 94780 0% /run/user/0
I/m over SSH, having RPi connected to HDMI monitor so I ran as below.
Ended with command line prompt, no change on display… MM didn’t run.
pi@magicpi:~/MagicMirror $ DISPLAY=:0 npm start
> magicmirror@2.9.0 start /home/pi/MagicMirror
> sh run-start.sh
Starting MagicMirror: v2.9.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: MMM-WeeklySchedule.
Initializing new module helper ...
Module helper loaded: MMM-DarkSkyForecast
Initializing new module helper ...
Module helper loaded: MMM-xiaomi
Initializing new module helper ...
Module helper loaded: newsfeed
No helper found for module: MMM-AirQuality.
Initializing new module helper ...
Module helper loaded: MMM-NetworkScanner
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
All module helpers loaded.
Starting server on port 8080 ...
Server started ...
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: MMM-DarkSkyForecast
====================== Starting node_helper for module [MMM-DarkSkyForecast]
Connecting socket for: MMM-xiaomi
Starting xiaomi helper
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-NetworkScanner
Starting module: MMM-NetworkScanner
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Sockets connected & modules started ...
pi@magicpi:~/MagicMirror $
Hi,
Have restart loop with MM v2.9.0.
Running RPi3:
Linux magicpi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
Logs show nothing special:
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: MMM-NetworkScanner
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: MMM-Remote-Control
1|mm | All module helpers loaded.
1|mm | Starting server on port 8080 ...
1|mm | Server started ...
1|mm | Connecting socket for: calendar
1|mm | Starting node helper for: calendar
1|mm | Connecting socket for: MMM-DarkSkyForecast
1|mm | ====================== Starting node_helper for module [MMM-DarkSkyForecast]
1|mm | Connecting socket for: MMM-xiaomi
1|mm | Starting xiaomi helper
1|mm | Connecting socket for: newsfeed
1|mm | Starting module: newsfeed
1|mm | Connecting socket for: MMM-NetworkScanner
1|mm | Starting module: MMM-NetworkScanner
1|mm | Connecting socket for: MMM-Remote-Control
1|mm | Starting node helper for: MMM-Remote-Control
1|mm | Sockets connected & modules started ...
1|mm | > magicmirror@2.9.0 start /home/pi/MagicMirror
1|mm | > sh run-start.sh
1|mm | Starting MagicMirror: v2.9.0
1|mm | Loading config ...
1|mm | Loading module helpers ...
1|mm | No helper found for module: alert.
1|mm | No helper found for module: clock.
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: calendar
1|mm | No helper found for module: MMM-WeeklySchedule.
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: MMM-DarkSkyForecast
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: MMM-xiaomi
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: newsfeed
1|mm | No helper found for module: MMM-AirQuality.
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: MMM-NetworkScanner
1|mm | Initializing new module helper ...
1|mm | Module helper loaded: MMM-Remote-Control
1|mm | All module helpers loaded.
1|mm | Starting server on port 8080 ...
1|mm | Server started ...
1|mm | Connecting socket for: calendar
1|mm | Starting node helper for: calendar
1|mm | Connecting socket for: MMM-DarkSkyForecast
1|mm | ====================== Starting node_helper for module [MMM-DarkSkyForecast]
1|mm | Connecting socket for: MMM-xiaomi
1|mm | Starting xiaomi helper
1|mm | Connecting socket for: newsfeed
1|mm | Starting module: newsfeed
1|mm | Connecting socket for: MMM-NetworkScanner
1|mm | Starting module: MMM-NetworkScanner
1|mm | Connecting socket for: MMM-Remote-Control
1|mm | Starting node helper for: MMM-Remote-Control
1|mm | Sockets connected & modules started ...
Versions as below:
pi@magicpi:~/MagicMirror $ node -v
v10.18.0
pi@magicpi:~/MagicMirror $ npm -v
6.13.4
How to troubleshoot ? Where / how to look for error?
Tried with sample config.js bu ended same way, with reboot loop…
check file by:
sudo nano ~/.config/lxsession/LXDE-pi/autostart
if it includes:
@xscreensaver -no-splash
then just comment it by adding #
#@xscreensaver -no-splash
if it doesn’t work install xscreensaver:
sudo apt-get install xscreensaver
downloaded ttf fonts from google, then copied to:
/usr/share/fonts/truetype
executed
fc-cache -fv
pm2 restart mm
it fixed the issue, however it means that MagicMirror has bug in its newest version…