MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Error on Start (fresh install) - Electron Illegal Access

    Scheduled Pinned Locked Moved Troubleshooting
    11 Posts 2 Posters 1.3k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F Offline
      frosty_snow @sdetweil
      last edited by

      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
      
      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @frosty_snow
        last edited by

        @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

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        F 1 Reply Last reply Reply Quote 0
        • F Offline
          frosty_snow @sdetweil
          last edited by

          @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

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sdetweil @frosty_snow
            last edited by 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

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            S F 2 Replies Last reply Reply Quote 0
            • S Offline
              sdetweil @sdetweil
              last edited by

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

              sorry try again

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • F Offline
                frosty_snow @sdetweil
                last edited by

                @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.

                S 1 Reply Last reply Reply Quote 1
                • S Offline
                  sdetweil @frosty_snow
                  last edited by

                  @frosty_snow cool…

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  1 Reply Last reply Reply Quote 0
                  • 1
                  • 2
                  • 1 / 2
                  • First post
                    Last post
                  Enjoying MagicMirror? Please consider a donation!
                  MagicMirror created by Michael Teeuw.
                  Forum managed by Sam, technical setup by Karsten.
                  This forum is using NodeBB as its core | Contributors
                  Contact | Privacy Policy