MM on Pi Zero fails after being off for a few days

kellogg76

Everything was stopped.

$ pm2 status
┌────┬────────────────────┬──────────┬──────┬──────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status   │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼──────────┼──────────┼──────────┤
│ 0  │ mmstart            │ fork     │ 1780 │ stopped  │ 0%       │ 0b       │
└────┴────────────────────┴──────────┴──────┴──────────┴──────────┴──────────┘

sdetweil

@kellogg76 pm2 info 0

kellogg76

@sdetweil

Describing process with id 0 - name mmstart
┌───────────────────┬──────────────────────────────────────┐
│ status            │ stopped                              │
│ name              │ mmstart                              │
│ version           │ N/A                                  │
│ restarts          │ 1780                                 │
│ uptime            │ 0                                    │
│ script path       │ /home/pi/mmstart.sh                  │
│ script args       │ N/A                                  │
│ error log path    │ /home/pi/.pm2/logs/mmstart-error.log │
│ out log path      │ /home/pi/.pm2/logs/mmstart-out.log   │
│ pid path          │ /home/pi/.pm2/pids/mmstart-0.pid     │
│ interpreter       │ bash                                 │
│ interpreter args  │ N/A                                  │
│ script id         │ 0                                    │
│ exec cwd          │ /home/pi                             │
│ exec mode         │ fork_mode                            │
│ node.js version   │ N/A                                  │
│ node env          │ N/A                                  │
│ watch & reload    │ ✘                                    │
│ unstable restarts │ 0                                    │
│ created at        │ 2020-03-28T19:51:14.338Z             │
└───────────────────┴──────────────────────────────────────┘
Divergent env variables from local env
┌────────────────┬──────────────────────────────────────┐
│ SSH_CONNECTION │ 192.168.1.148 54823 192.168.1.166 22 │
│ XDG_SESSION_ID │ c2                                   │
│ SSH_CLIENT     │ 192.168.1.148 54823 22               │
│ SSH_TTY        │ /dev/pts/1                           │
└────────────────┴──────────────────────────────────────┘

Add your own code metrics: http://bit.ly/code-metrics
Use `pm2 logs mmstart [--lines 1000]` to display logs
Use `pm2 env 0` to display environment variables
Use `pm2 monit` to monitor CPU and Memory usage mmstart

sdetweil

@kellogg76 said in MM on Pi Zero fails after being off for a few days:

/home/pi/mmstart.sh

can u show that file

kellogg76

@sdetweil

#!/bin/bash
cd ~/MagicMirror
node serveronly &
sleep 30
xinit /home/pi/chromium_start.sh

sdetweil

@kellogg76 said in MM on Pi Zero fails after being off for a few days:

xinit /home/pi/chromium_start.sh

and that one?

kellogg76

@sdetweil

#!/bin/sh
unclutter &
xset -dpms # disable DPMS (Energy Star) features.
xset s off # disable screen saver
xset s noblank # don’t blank the video device
matchbox-window-manager &
chromium-browser -–incognito --start-fullscreen -–kiosk http://localhost:8080/

sdetweil

@kellogg76 weird…

and if you do pm2 start 0 it works ok?

kellogg76

@sdetweil it works in as much as I can see the magic mirror on another computer when I point to the correct IP, but the pi itself does not display anything at all, it sits at a terminal prompt or if I reboot and let it try to start on its own it’ll switch from prompt to black screen with mouse pointer as if it’s trying to start, then it loops back to a prompt and cycles between the two states.

sdetweil

weird… seems like chrome is having trouble.

if you type

chromium-browser  --app=https://cnn.com

does it come up?

in 2.10, i created a similar script for
pi0w(armv6l) as electron doesn’t exist anymore

try this script

curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/run-start.sh >~/MagicMirror/run-start.sh
chmod +x ~/MagicMirror/run-start.sh

then

cd ~/MagicMirror
./run-start.sh