Autostarts but doesn't run, will run on restart

ember1205

Correct syntax would need to be:

  raspberry_pi=$(grep ^ID= /etc/os-release | cut -f2 -d=)
  if [ "$raspberry_pi." == "raspbian" ] ; then
   sleep 2
  fi

The RPi 3B+ is a little slower to initialize on Bullseye versus Buster. Any time a device is running a slightly heavier OS and needs a little more time to finish booting up, I could see this occurring. The question is, do you solve it with a fix that impacts everyone (“sleep 2” or similar), test for particular OS/HW combo’s, or is there another process to look for that would better indicate when the system should be finished initializing?

Right now, it looks for X and just “moves on” when it isn’t found and assumes some sort of mistake or something in the config. Great as a fail-safe, but creates a new occasional issue to be dealt with.

sdetweil

@ember1205 that test is for when MM is running under docker (with no X running) but using the docker host’s xorg for viewing…

ember1205

@sdetweil

The test I’m referring to checks to see if X is running. If not, it moves on to test for Lubuntu. If that also fails, it assumes server only and moves on.

I do recall seeing a specific Docker test at the very beginning of the script, but that’s a fair bit earlier than where I’ve added this check (which is right before the “pgrep Xorg” line).

sdetweil

@ember1205 yes… i am looking for a test that works if the system is slow…

i added the rm of ./config folder and my pi 0 now comes up instead of the chrome desktop
which was random before…

        if [ $(which $b). != '.' ]; then
             rm -rf ~/.config/$b 2>/dev/null   # add this line

ember1205

@sdetweil said in Autostarts but doesn't run, will run on restart:

… my pi 0 now comes up instead of the chrome desktop
which was random before…

Not sure I’m following what this should mean?

sdetweil

@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

ember1205

@sdetweil

Oh… now I follow.

sdetweil

@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

ember1205

@sdetweil

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 serveronly

Here’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

sdetweil

@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