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.

    strange boot issuse

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    9 Posts 4 Posters 2.1k Views 3 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.
    • J Offline
      jhwwhite
      last edited by jhwwhite

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • Mykle1M Offline
        Mykle1 Project Sponsor Module Developer
        last edited by

        That is incredibly hard to read. Please consider this:

        https://forum.magicmirror.builders/topic/4247/how-to-post-code-on-the-forum-for-absolute-beginners

        Create a working config
        How to add modules

        1 Reply Last reply Reply Quote 0
        • J Offline
          jhwwhite @bhepler
          last edited by jhwwhite

          Sorry for the delay. I was out of town and forgot my laptop charging cable.

          @bhepler said in strange boot issuse:

          @jhwwhite - I have a lot of questions, so bear with me.

          1. Did you ever get the MagicMirror to work the way you expected?
            Yes I did
          2. Do you ever see the Raspberry Pi’s desktop during the boot sequence?
            No. It goes strait to the Magic Mirror boot page
          3. Are you using the latest version of Raspbian full edition (not Lite)?
            It’s the full version I believe
          4. Once you see that command line, can you SSH into the Pi?
            Yes
          5. If 4 is true, can you run the pm2 log 0 command and let us know what the logs say?
            Sure
          0|mm       | > magicmirror@2.6.0 start /home/pi/MagicMirror
          0|mm       | > sh run-start.sh
          0|mm       | 
          0|mm       | 
          0|mm       | > magicmirror@2.6.0 start /home/pi/MagicMirror
          0|mm       | > sh run-start.sh
          0|mm       | 
          0|mm       | 
          0|mm       | > magicmirror@2.6.0 start /home/pi/MagicMirror
          0|mm       | > sh run-start.sh
          0|mm       | 
          0|mm       | 
          0|mm       | > magicmirror@2.6.0 start /home/pi/MagicMirror
          0|mm       | > sh run-start.sh
          0|mm       | 
          
          /home/pi/.pm2/logs/mm-error.log last 15 lines:
          0|mm       | 
          0|mm       | npm ERR! A complete log of this run can be found in:
          0|mm       | npm ERR!     /home/pi/.npm/_logs/2019-01-13T19_30_43_236Z-debug.log
          0|mm       | 
          0|mm       | (electron:3869): Gtk-WARNING **: cannot open display: :0
          0|mm       | npm ERR! code ELIFECYCLE
          0|mm       | npm ERR! errno 1
          0|mm       | npm ERR! magicmirror@2.6.0 start: `sh run-start.sh`
          0|mm       | npm ERR! Exit status 1
          0|mm       | npm ERR! 
          0|mm       | npm ERR! Failed at the magicmirror@2.6.0 start script.
          0|mm       | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
          0|mm       | 
          0|mm       | npm ERR! A complete log of this run can be found in:
          0|mm       | npm ERR!     /home/pi/.npm/_logs/2019-01-13T19_30_48_977Z-debug.log
          
          0|mm  | > magicmirror@2.6.0 start /home/pi/MagicMirror
          0|mm  | > sh run-start.sh
          0|mm  | (electron:3938): Gtk-WARNING **: cannot open display: :0
          0|mm  | npm
          0|mm  |  ERR! code ELIFECYCLE
          0|mm  | npm ERR! errno 1
          0|mm  | npm
          0|mm  |  ERR! magicmirror@2.6.0 start: `sh run-start.sh`
          0|mm  | npm ERR! Exit status 1
          0|mm  | npm
          0|mm  |  ERR! 
          0|mm  | npm ERR! Failed at the magicmirror@2.6.0 start script.
          0|mm  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
          0|mm  | npm ERR! A complete log of this run can be found in:
          0|mm  | npm ERR!     /home/pi/.npm/_logs/2019-01-13T19_30_54_950Z-debug.log
          0|mm  | > magicmirror@2.6.0 start /home/pi/MagicMirror
          0|mm  | > sh run-start.sh
          0|mm  | (electron:4002): Gtk-WARNING **: cannot open display: :0
          0|mm  | npm
          0|mm  |  ERR! code ELIFECYCLE
          0|mm  | npm ERR! errno 1
          0|mm  | npm
          0|mm  |  ERR! magicmirror@2.6.0 start: `sh run-start.sh`
          0|mm  | npm ERR! Exit status 1
          0|mm  | npm
          0|mm  |  ERR! 
          0|mm  | npm ERR! Failed at the magicmirror@2.6.0 start script.
          0|mm  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
          0|mm  | npm ERR! A complete log of this run can be found in:
          0|mm  | npm ERR!     /home/pi/.npm/_logs/2019-01-13T19_31_00_675Z-debug.log
          0|mm  | > magicmirror@2.6.0 start /home/pi/MagicMirror
          0|mm  | > sh run-start.sh
          0|mm  | (electron:4066): Gtk-WARNING **: cannot open display: :0
          0|mm  | npm
          0|mm  |  ERR!
          0|mm  |  code ELIFECYCLE
          0|mm  | npm 
          0|mm  | ERR! errno 1
          0|mm  | npm
          0|mm  |  ERR! magicmirror@2.6.0 start: `sh run-start.sh`
          0|mm  | npm ERR! Exit status 1
          0|mm  | npm 
          0|mm  | ERR! 
          0|mm  | npm ERR! Failed at the magicmirror@2.6.0 start script.
          0|mm  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
          0|mm  | npm ERR! A complete log of this run can be found in:
          0|mm  | npm ERR!
          
          

          It just keeps going on like that

          1 Reply Last reply Reply Quote 0
          • P Offline
            phreakinuts
            last edited by

            Are you able to bypass the automatic boot sequence, boot normally, and start MagicMirror manually?

            J 1 Reply Last reply Reply Quote 0
            • J Offline
              jhwwhite @phreakinuts
              last edited by

              @phreakinuts yeah. It’s the same issue

              pi@raspberrypi:~ $ pm2 stop mm
              
              [PM2] Applying action stopProcessId on app [mm](ids: 0)
              [PM2] [mm](0) ✓
              ┌─────────────┬────┬───────┬────────┬─────────┬──────┬────────┬──────────┐
              │ Name        │ id │ mode  │ status │ ↺       │ cpu  │ memory │
              ├─────────────┼────┼───────┼────────┼─────────┼──────┼────────┼──────────┤
              │ MagicMirror │ 1  │ 2.6.0 │ fork   │ online  │ 2961 │ 0%     │ 2.5 MB   │
              │ mm          │ 0  │ N/A   │ fork   │ stopped │ 2961 │ 0%     │ 0 B      │
              └─────────────┴────┴───────┴────────┴─────────┴──────┴────────┴──────────┘
               Use `pm2 show <id|name>` to get more details about an app
              pi@raspberrypi:~ $ pm2 delete mm
              [PM2] Applying action deleteProcessId on app [mm](ids: 0)
              [PM2] [mm](0) ✓
              ┌─────────────┬────┬───────┬────────┬────────┬──────┬────────┬──────────┐
              │ Name        │ id │ mode  │ status │ ↺      │ cpu  │ memory │
              ├─────────────┼────┼───────┼────────┼────────┼──────┼────────┼──────────┤
              │ MagicMirror │ 1  │ 2.6.0 │ fork   │ online │ 2961 │ 0%     │ 2.5 MB   │
              └─────────────┴────┴───────┴────────┴────────┴──────┴────────┴──────────┘
               Use `pm2 show <id|name>` to get more details about an app
              pi@raspberrypi:~ $ rm mm.sh
              
              
              

              Did I not do it right?

              1 Reply Last reply Reply Quote 0
              • P Offline
                phreakinuts
                last edited by

                What does it show when you simply try to run it in the MagicMirror directory.

                DISPLAY=:0 npm start

                How did you perform the update? Sounds like an odd issue to have, but attributed to the update. Did you verify that nothing broke with pm2 when you performed the update?

                1 Reply Last reply Reply Quote 0
                • bheplerB Offline
                  bhepler Module Developer
                  last edited by

                  Yeah, that looks right. If you restart your process, do you see the mirror? pm2 restart 0

                  1 Reply Last reply Reply Quote 0
                  • 1 / 1
                  • 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