Error on Start (fresh install) - Electron Illegal Access

frosty_snow

@sdetweil
Thank you! I think that solved that problem.

Should the monitor that is connected (its connected via a microHDMI to HDMI and then an HDMI to DisplayPort adapter at the other end) automatically display once I’ve run pm2 start MagicMirror? Or do I need to take an additional step?

It indicates process successfully started, however the monitor doesn’t show anything.
I should note we’ve only ever ssh’d into the Pi from our desktops and I’ve never used a GUI connected to the Pi before, so very possible I’m not doing something correctly in that regard.

sdetweil

@frosty_snow it should show, the startup sets the linux xwindows DISPLAY=:0

unless there is another problem…

do
pm2 logs --lines=50

pm2 status to show whats running

pm2 stop all

pm2 --help
for more options

frosty_snow

Ok when I do pm2 status i do see that the status is “online” after I do the pm2 start MagicMirror. However yes it appears there is another issue, as my display simply remains blank (I’ve 3 screens, 2 connected to my desktop with the 3rd connected to the Rpi4).
The log files show the following errors, which would seem its related to this line 102. Is it possible I need to edit this?

/home/pi/.pm2/logs/MagicMirror-error.log last 50 lines:
0|MagicMir | ./run-start.sh: line 102:   841 Killed                  node server                                                                                                                                                             only
0|MagicMir | npm ERR! code ELIFECYCLE
0|MagicMir | npm ERR! errno 137
0|MagicMir | npm ERR! magicmirror@2.15.0 start: `./run-start.sh $1`
0|MagicMir | npm ERR! Exit status 137
0|MagicMir | npm ERR!
0|MagicMir | npm ERR! Failed at the magicmirror@2.15.0 start script.
0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely a                                                                                                                                                             dditional logging output above.
0|MagicMir |
0|MagicMir | npm ERR! A complete log of this run can be found in:
0|MagicMir | npm ERR!     /home/pi/.npm/_logs/2021-04-09T20_25_23_729Z-debug.log
0|MagicMir | ./run-start.sh: line 102:  2087 Killed                  node server                                                                                                                                                             only
0|MagicMir | npm ERR! code ELIFECYCLE
0|MagicMir | npm ERR! errno 137
0|MagicMir | npm ERR! magicmirror@2.15.0 start: `./run-start.sh $1`
0|MagicMir | npm ERR! Exit status 137
0|MagicMir | npm ERR!
0|MagicMir | npm ERR! Failed at the magicmirror@2.15.0 start script.
0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely a                                                                                                                                                             dditional logging output above.
0|MagicMir |
0|MagicMir | npm ERR! A complete log of this run can be found in:
0|MagicMir | npm ERR!     /home/pi/.npm/_logs/2021-04-09T20_27_20_593Z-debug.log
0|MagicMir | ./run-start.sh: line 102:   814 Killed                  node server                                                                                                                                                             only
0|MagicMir | npm ERR! code ELIFECYCLE
0|MagicMir | npm ERR! errno 137
0|MagicMir | npm ERR! magicmirror@2.15.0 start: `./run-start.sh $1`
0|MagicMir | npm ERR! Exit status 137
0|MagicMir | npm ERR!
0|MagicMir | npm ERR! Failed at the magicmirror@2.15.0 start script.
0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely a                                                                                                                                                             dditional logging output above.
0|MagicMir |
0|MagicMir | npm ERR! A complete log of this run can be found in:
0|MagicMir | npm ERR!     /home/pi/.npm/_logs/2021-04-09T20_53_27_407Z-debug.log

sdetweil

@frosty_snow ok, that is my run-start.sh script which is put in in the case where electron won’t run …

BUT it should start chromium-browser

can u do

which chromium

and

which cromium-browser

on a terminal window on the pi (or ssh session to the pi)

because electron won’t run, we launch MM in server mode
and then launch chrome over it…

i had a case where the previous server mode was still running, and so I don’t have to tell u how to correct that, I kill it…

pm2 job is to keep MM running… so, when the script ends, pm2 restarts it…
over and over…

oh by the way… the column on the pm2 status that looks like a circle with an arrow tip is the number of restarts… for your case at the moment, it should be going up

frosty_snow

@sdetweil
currently im only at 1 but it said 2 before i rebooted my pi
The below is the result of those cmds in the ssh session into the pi on my desktop

pi@raspberrypi:~ $ which chromium
pi@raspberrypi:~ $ which chromium-browser
/usr/bin/chromium-browser
pi@raspberrypi:~ $

I’ve rebooted the pi before trying to start MM up again

sdetweil

@frosty_snow ok, stop mm

pm2 stop 0

then do

cd ~/MagicMirror
bash -x ./run-start.sh  >somefile 2>&1
wait 10 seconds, then ctrl-c

and post or send me somefile

my email is the same userid at gmail.com

sdetweil

@frosty_snow correction , see I added a little on to the bash -x line to capture the bash output

sorry try again

frosty_snow

@sdetweil
I’d like to thank you so much for taking the time on this. I’ve figured out that it is a hardware issue. I switched up to a different monitor that is not display port and the MM is working correctly. I don’t know if its the Displayport that is the problem or not but I can use my other monitor for the actual MM build and just use this displayPort monitor as my secondary “reading” monitor.

Hope you have a lovely weekend and thank you again for working with me.

sdetweil

@frosty_snow cool…