Read the statement by Michael Teeuw here.
Autostarts but doesn't run, will run on restart
-
@ember1205 you had another problem where chrome comes up to the white screen w the icons. that is the chrome desktop.
i added the delete of the config folder to the run start script to get it back to just MagicMirror
-
Oh… now I follow.
-
@ember1205 can u try this on the reboot problem
add this
xprop -root # add this line xorg=$(pgrep Xorg)then do the reboot test with the debugging still turned on
-
I removed the check I was running that was ensuring it would start correctly and put in the line you asked. I believe the log info you want is this:
0|mm | + '[' -f ./untrack-css.sh ']' 0|mm | + grep docker /proc/1/cgroup -qa 0|mm | + '[' -z :0 ']' 0|mm | ++ uname -m 0|mm | + arch=armv7l 0|mm | + false=false 0|mm | ++ grep -i serveronly: 0|mm | ++ awk -F: '{print tolower($2)}' 0|mm | ++ tr -d ',"'\''\r' 0|mm | ++ grep -v '^[[:blank:]]*//' config/config.js 0|mm | ++ sed -e 's/^[[:space:]]*//' 0|mm | + serveronly=local 0|mm | + serveronly=local 0|mm | + xprop -root 0|mm | xprop: unable to open display ':0' 0|mm | ++ pgrep Xorg 0|mm | + xorg= 0|mm | + '[' . == . ']' 0|mm | ++ pgrep X 0|mm | + xorg= 0|mm | ++ uname 0|mm | + mac=Linux 0|mm | + '[' local. '!=' false. -o armv7l == armv6l ']' 0|mm | + '[' local. == true. ']' 0|mm | + '[' . == . -a Linux '!=' Darwin ']' 0|mm | + node serveronlyHere’s the rest that goes with it “just in case”:
/home/pi/.pm2/pm2.log last 100 lines: PM2 | 2022-05-11T08:48:46: PM2 log: PM2 successfully stopped PM2 | 2022-05-11T08:49:03: PM2 log: =============================================================================== PM2 | 2022-05-11T08:49:03: PM2 log: --- New PM2 Daemon started ---------------------------------------------------- PM2 | 2022-05-11T08:49:03: PM2 log: Time : Wed May 11 2022 08:49:03 GMT-0400 (Eastern Daylight Time) PM2 | 2022-05-11T08:49:03: PM2 log: PM2 version : 4.4.1 PM2 | 2022-05-11T08:49:03: PM2 log: Node.js version : 16.15.0 PM2 | 2022-05-11T08:49:03: PM2 log: Current arch : arm PM2 | 2022-05-11T08:49:03: PM2 log: PM2 home : /home/pi/.pm2 PM2 | 2022-05-11T08:49:03: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid PM2 | 2022-05-11T08:49:03: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock PM2 | 2022-05-11T08:49:03: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock PM2 | 2022-05-11T08:49:03: PM2 log: Application log path : /home/pi/.pm2/logs PM2 | 2022-05-11T08:49:03: PM2 log: Worker Interval : 30000 PM2 | 2022-05-11T08:49:03: PM2 log: Process dump file : /home/pi/.pm2/dump.pm2 PM2 | 2022-05-11T08:49:03: PM2 log: Concurrent actions : 2 PM2 | 2022-05-11T08:49:03: PM2 log: SIGTERM timeout : 1600 PM2 | 2022-05-11T08:49:03: PM2 log: =============================================================================== PM2 | 2022-05-11T08:49:04: PM2 log: App [mm:0] starting in -fork mode- PM2 | 2022-05-11T08:49:04: PM2 log: App [mm:0] online /home/pi/.pm2/logs/mm-out.log last 100 lines: 0|mm | 0|mm | > magicmirror@2.13.0 start 0|mm | > ./run-start.sh 0|mm | 0|mm | [2022-05-11 08:49:14.433] [LOG] Starting MagicMirror: v2.13.0 0|mm | [2022-05-11 08:49:14.450] [LOG] Loading config ... 0|mm | [2022-05-11 08:49:14.465] [LOG] Loading module helpers ... 0|mm | [2022-05-11 08:49:15.909] [LOG] Initializing new module helper ... 0|mm | [2022-05-11 08:49:15.914] [LOG] Module helper loaded: MMM-ImagesPhotos 0|mm | [2022-05-11 08:49:15.923] [LOG] No helper found for module: alert. 0|mm | [2022-05-11 08:49:16.037] [LOG] Initializing new module helper ... 0|mm | [2022-05-11 08:49:16.040] [LOG] Module helper loaded: updatenotification 0|mm | [2022-05-11 08:49:16.044] [LOG] No helper found for module: clock. 0|mm | [2022-05-11 08:49:16.351] [LOG] Initializing new module helper ... 0|mm | [2022-05-11 08:49:16.353] [LOG] Module helper loaded: calendar 0|mm | [2022-05-11 08:49:16.401] [LOG] No helper found for module: currentweather. 0|mm | [2022-05-11 08:49:16.576] [LOG] No helper found for module: weatherforecast. 0|mm | [2022-05-11 08:49:16.578] [LOG] All module helpers loaded. 0|mm | [2022-05-11 08:49:18.093] [LOG] Starting server on port 8080 ... 0|mm | [2022-05-11 08:49:18.123] [LOG] Server started ... 0|mm | [2022-05-11 08:49:18.126] [LOG] Connecting socket for: MMM-ImagesPhotos 0|mm | [2022-05-11 08:49:18.127] [LOG] Starting node helper for: MMM-ImagesPhotos 0|mm | [2022-05-11 08:49:18.130] [LOG] Connecting socket for: updatenotification 0|mm | [2022-05-11 08:49:18.132] [LOG] Connecting socket for: calendar 0|mm | [2022-05-11 08:49:18.134] [LOG] Starting node helper for: calendar 0|mm | [2022-05-11 08:49:18.135] [LOG] Sockets connected & modules started ... 0|mm | [2022-05-11 08:49:18.137] [LOG] 0|mm | Ready to go! Please point your browser to: http://0.0.0.0:8080 -
@ember1205 said in Autostarts but doesn't run, will run on restart:
0|mm | + xprop -root
0|mm | xprop: unable to open display ‘:0’thanks… x not up yet…
weird, never seen this on any other system pi otherwise…
I have 3 pi3, 2 pi4, pi 0w and pi02w and jetson nano, odroid, chromebox, plus desktops…i’ll add another environment variable check
u add it to the mm.sh used to launch…let me test it…
thanks for your help
-
Happy to have broken it. Again. lol
-
@ember1205 ok, do this
cd ~/MagicMirror curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/test/run-start.sh >run-start.shedit the MagicMirror/installers/mm.sh
add a line before the npm start
export wait_for_x=1(or true, or ANYTHING)
the value can be anythingedit the run-start.sh and add the -x on the 1st line again
do the pm2 flush
pm2 restartjust to test
then do the reboot test -
@sdetweil said in Autostarts but doesn't run, will run on restart:
export wait_for_x=1
That isn’t the mm.sh that my system launches from, though… Mine is ~/mm.sh
Does the one you’re referencing get called from one of the other scripts?
-
@ember1205 whatever script…
if you used my setup script it uses the one already in installers
-
Ok… Modified the ~/mm.sh script
pm2 restart mm failed to start Chromium correctly - landed on the Chrome Desktop.
Purged the config directory and started mm without issue.Restarted the mirror and everything came up clean multiple times, but there is clearly still something weird happening with Chromium in that I have to continue wiping the config directory before it will start up correctly.
