• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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 [ERR_STREAM_DESTROYED]

Scheduled Pinned Locked Moved Unsolved Troubleshooting
7 Posts 2 Posters 2.0k 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.
  • J Offline
    jorgnyg
    last edited by Jan 10, 2020, 11:20 PM

    After some MM up-time on the rpi zero I get the following error.

    /home/pi/.pm2/logs/mm-error.log last 15 lines:
    0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
    0|mm       |     at process.emit (events.js:198:13)
    0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
    0|mm       | events.js:174
    0|mm       |       throw er; // Unhandled 'error' event
    0|mm       |       ^
    0|mm       | 
    0|mm       | Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
    0|mm       |     at doWrite (_stream_writable.js:411:19)
    0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
    0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
    0|mm       |     at Console.con.(anonymous function) [as log] (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
    0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
    0|mm       |     at process.emit (events.js:198:13)
    0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
    

    Seems like it’s loosing internet connections or something, since modules fails to fetch new data after the error.

    Can’t find additional error code other than the added output, so how can I debug this? Anyone facing the same problem?

    S 3 Replies Last reply Jan 11, 2020, 12:25 AM Reply Quote 0
    • S Offline
      sdetweil @jorgnyg
      last edited by Jan 11, 2020, 12:25 AM

      @jorgnyg once it fails, that code is dead…

      this is probably a timing error, because the 0 is slower than the rest

      will look at it…

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @jorgnyg
        last edited by Jan 11, 2020, 12:26 AM

        @jorgnyg can u do

        pm2 logs --lines=100
        (note two dashes)

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        J 1 Reply Last reply Jan 11, 2020, 8:47 AM Reply Quote 0
        • J Offline
          jorgnyg @sdetweil
          last edited by jorgnyg Jan 11, 2020, 8:48 AM Jan 11, 2020, 8:47 AM

          @sdetweil Yes I agree with the timing error fault. we just have to figure out where.

          Log output here:
          :::

          TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option)
          /home/pi/.pm2/pm2.log last 100 lines:
          PM2        | 2020-01-10T22:33:44: PM2 log: Stopping app:mm id:0
          PM2        | 2020-01-10T22:33:45: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:46: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:47: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:47: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:47: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:47: PM2 log: pid=3185 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-10T22:33:47: PM2 log: Process with pid 3185 still alive after 1600ms, sending it SIGKILL now...
          PM2        | 2020-01-10T22:33:49: PM2 log: App [mm:0] exited with code [0] via signal [SIGKILL]
          PM2        | 2020-01-10T22:33:49: PM2 log: pid=3185 msg=process killed
          PM2        | 2020-01-10T22:35:20: PM2 log: App [mm:0] starting in -fork mode-
          PM2        | 2020-01-10T22:35:20: PM2 log: App [mm:0] online
          PM2        | 2020-01-11T00:06:25: PM2 log: Stopping app:mm id:0
          PM2        | 2020-01-11T00:06:27: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:27: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:27: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:27: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:28: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:29: PM2 log: pid=4479 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:06:29: PM2 log: Process with pid 4479 still alive after 1600ms, sending it SIGKILL now...
          PM2        | 2020-01-11T00:06:31: PM2 log: App [mm:0] exited with code [0] via signal [SIGKILL]
          PM2        | 2020-01-11T00:06:31: PM2 log: pid=4479 msg=process killed
          PM2        | 2020-01-11T00:07:12: PM2 log: App [mm:0] starting in -fork mode-
          PM2        | 2020-01-11T00:07:12: PM2 log: App [mm:0] online
          PM2        | 2020-01-11T00:11:39: PM2 log: Stopping app:mm id:0
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:41: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: pid=11984 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T00:11:42: PM2 log: Process with pid 11984 still alive after 1600ms, sending it SIGKILL now...
          PM2        | 2020-01-11T00:11:45: PM2 log: App [mm:0] exited with code [0] via signal [SIGKILL]
          PM2        | 2020-01-11T00:11:45: PM2 log: pid=11984 msg=process killed
          PM2        | 2020-01-11T00:22:43: PM2 log: App [mm:0] starting in -fork mode-
          PM2        | 2020-01-11T00:22:43: PM2 log: App [mm:0] online
          PM2        | 2020-01-11T09:32:55: PM2 log: ===============================================================================
          PM2        | 2020-01-11T09:32:55: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
          PM2        | 2020-01-11T09:32:55: PM2 log: Time                 : Sat Jan 11 2020 09:32:55 GMT+0100 (Central European Standard Time)
          PM2        | 2020-01-11T09:32:55: PM2 log: PM2 version          : 4.2.1
          PM2        | 2020-01-11T09:32:55: PM2 log: Node.js version      : 10.18.1
          PM2        | 2020-01-11T09:32:55: PM2 log: Current arch         : arm
          PM2        | 2020-01-11T09:32:55: PM2 log: PM2 home             : /home/pi/.pm2
          PM2        | 2020-01-11T09:32:55: PM2 log: PM2 PID file         : /home/pi/.pm2/pm2.pid
          PM2        | 2020-01-11T09:32:55: PM2 log: RPC socket file      : /home/pi/.pm2/rpc.sock
          PM2        | 2020-01-11T09:32:55: PM2 log: BUS socket file      : /home/pi/.pm2/pub.sock
          PM2        | 2020-01-11T09:32:55: PM2 log: Application log path : /home/pi/.pm2/logs
          PM2        | 2020-01-11T09:32:55: PM2 log: Worker Interval      : 30000
          PM2        | 2020-01-11T09:32:55: PM2 log: Process dump file    : /home/pi/.pm2/dump.pm2
          PM2        | 2020-01-11T09:32:55: PM2 log: Concurrent actions   : 2
          PM2        | 2020-01-11T09:32:55: PM2 log: SIGTERM timeout      : 1600
          PM2        | 2020-01-11T09:32:55: PM2 log: ===============================================================================
          PM2        | 2020-01-11T09:32:57: PM2 log: App [mm:0] starting in -fork mode-
          PM2        | 2020-01-11T09:32:57: PM2 log: App [mm:0] online
          PM2        | 2020-01-11T09:41:08: PM2 log: Stopping app:mm id:0
          PM2        | 2020-01-11T09:41:10: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:11: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:12: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:12: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:12: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:12: PM2 log: pid=827 msg=failed to kill - retrying in 100ms
          PM2        | 2020-01-11T09:41:12: PM2 log: Process with pid 827 still alive after 1600ms, sending it SIGKILL now...
          PM2        | 2020-01-11T09:41:14: PM2 log: App [mm:0] exited with code [0] via signal [SIGKILL]
          PM2        | 2020-01-11T09:41:14: PM2 log: pid=827 msg=process killed
          
          /home/pi/.pm2/logs/mm-out.log last 100 lines:
          0|mm       | [22:35:42.053] [LOG] Starting node helper for: MMM-Trello
          0|mm       | [22:35:42.064] [LOG] Sockets connected & modules started ...
          0|mm       | [22:35:42.072] [LOG]
          0|mm       | Ready to go! Please point your browser to: http://localhost:8080
          0|mm       | Starting chromium browser now, have patience, it takes a minute
          0|mm       | 
          0|mm       | > magicmirror@2.10.0 start /home/pi/MagicMirror
          0|mm       | > ./run-start.sh
          0|mm       | 
          0|mm       | [00:07:26.988] [LOG] Starting MagicMirror: v2.10.0
          0|mm       | [00:07:27.103] [LOG] Loading config ...
          0|mm       | [00:07:27.142] [LOG] Loading module helpers ...
          0|mm       | [00:07:27.161] [LOG] No helper found for module: alert.
          0|mm       | [00:07:27.174] [LOG] No helper found for module: clock.
          0|mm       | [00:07:31.751] [LOG] Initializing new module helper ...
          0|mm       | [00:07:31.760] [LOG] Module helper loaded: calendar
          0|mm       | [00:07:31.776] [LOG] No helper found for module: compliments.
          0|mm       | [00:07:31.792] [LOG] No helper found for module: currentweather.
          0|mm       | [00:07:31.801] [LOG] No helper found for module: weatherforecast.
          0|mm       | [00:07:32.012] [LOG] Initializing new module helper ...
          0|mm       | [00:07:32.022] [LOG] Module helper loaded: MMM-Spotify
          0|mm       | [00:07:35.649] [LOG] Initializing new module helper ...
          0|mm       | [00:07:35.658] [LOG] Module helper loaded: MMM-Trello
          0|mm       | [00:07:35.668] [LOG] All module helpers loaded.
          0|mm       | [00:07:35.675] [LOG] Starting server on port 8080 ...
          0|mm       | [00:07:35.808] [LOG] Server started ...
          0|mm       | [00:07:35.822] [LOG] Connecting socket for: calendar
          0|mm       | [00:07:35.832] [LOG] Starting node helper for: calendar
          0|mm       | [00:07:35.844] [LOG] Connecting socket for: MMM-Spotify
          0|mm       | [00:07:35.870] [LOG] [SPOTIFY_AUTH] Token is expired. It will be refreshed
          0|mm       | [00:07:35.881] [LOG] [SPOTIFY_AUTH] Token refreshing...
          0|mm       | [00:07:36.004] [LOG] Connecting socket for: MMM-Trello
          0|mm       | [00:07:36.018] [LOG] Starting node helper for: MMM-Trello
          0|mm       | [00:07:36.022] [LOG] Sockets connected & modules started ...
          0|mm       | [00:07:36.031] [LOG]
          0|mm       | Ready to go! Please point your browser to: http://localhost:8080
          0|mm       | Starting chromium browser now, have patience, it takes a minute
          0|mm       | 
          0|mm       | > magicmirror@2.10.0 start /home/pi/MagicMirror
          0|mm       | > ./run-start.sh
          0|mm       | 
          0|mm       | [00:22:57.441] [LOG] Starting MagicMirror: v2.10.0
          0|mm       | [00:22:57.555] [LOG] Loading config ...
          0|mm       | [00:22:57.593] [LOG] Loading module helpers ...
          0|mm       | [00:22:57.611] [LOG] No helper found for module: alert.
          0|mm       | [00:22:57.624] [LOG] No helper found for module: clock.
          0|mm       | [00:23:00.940] [LOG] Initializing new module helper ...
          0|mm       | [00:23:00.950] [LOG] Module helper loaded: calendar
          0|mm       | [00:23:00.961] [LOG] No helper found for module: compliments.
          0|mm       | [00:23:00.972] [LOG] No helper found for module: currentweather.
          0|mm       | [00:23:00.983] [LOG] No helper found for module: weatherforecast.
          0|mm       | [00:23:01.192] [LOG] Initializing new module helper ...
          0|mm       | [00:23:01.214] [LOG] Module helper loaded: MMM-Spotify
          0|mm       | [00:23:04.094] [LOG] Initializing new module helper ...
          0|mm       | [00:23:04.102] [LOG] Module helper loaded: MMM-Trello
          0|mm       | [00:23:04.113] [LOG] All module helpers loaded.
          0|mm       | [00:23:04.120] [LOG] Starting server on port 8080 ...
          0|mm       | [00:23:04.248] [LOG] Server started ...
          0|mm       | [00:23:04.259] [LOG] Connecting socket for: calendar
          0|mm       | [00:23:04.271] [LOG] Starting node helper for: calendar
          0|mm       | [00:23:04.283] [LOG] Connecting socket for: MMM-Spotify
          0|mm       | [00:23:04.305] [LOG] [SPOTIFY_AUTH] Token is fresh.
          0|mm       | [00:23:04.314] [LOG] Connecting socket for: MMM-Trello
          0|mm       | [00:23:04.324] [LOG] Starting node helper for: MMM-Trello
          0|mm       | [00:23:04.336] [LOG] Sockets connected & modules started ...
          0|mm       | [00:23:04.341] [LOG]
          0|mm       | Ready to go! Please point your browser to: http://localhost:8080
          0|mm       | Starting chromium browser now, have patience, it takes a minute
          0|mm       | 
          0|mm       | > magicmirror@2.10.0 start /home/pi/MagicMirror
          0|mm       | > ./run-start.sh
          0|mm       | 
          0|mm       | [09:33:18.789] [LOG] Starting MagicMirror: v2.10.0
          0|mm       | [09:33:18.865] [LOG] Loading config ...
          0|mm       | [09:33:18.904] [LOG] Loading module helpers ...
          0|mm       | [09:33:18.924] [LOG] No helper found for module: alert.
          0|mm       | [09:33:18.936] [LOG] No helper found for module: clock.
          0|mm       | [09:33:22.347] [LOG] Initializing new module helper ...
          0|mm       | [09:33:22.358] [LOG] Module helper loaded: calendar
          0|mm       | [09:33:22.371] [LOG] No helper found for module: compliments.
          0|mm       | [09:33:22.381] [LOG] No helper found for module: currentweather.
          0|mm       | [09:33:22.392] [LOG] No helper found for module: weatherforecast.
          0|mm       | [09:33:22.559] [LOG] Initializing new module helper ...
          0|mm       | [09:33:22.568] [LOG] Module helper loaded: MMM-Spotify
          0|mm       | [09:33:25.558] [LOG] Initializing new module helper ...
          0|mm       | [09:33:25.567] [LOG] Module helper loaded: MMM-Trello
          0|mm       | [09:33:25.578] [LOG] All module helpers loaded.
          0|mm       | [09:33:25.585] [LOG] Starting server on port 8080 ...
          0|mm       | [09:33:25.742] [LOG] Server started ...
          0|mm       | [09:33:25.755] [LOG] Connecting socket for: calendar
          0|mm       | [09:33:25.772] [LOG] Starting node helper for: calendar
          0|mm       | [09:33:25.780] [LOG] Connecting socket for: MMM-Spotify
          0|mm       | [09:33:25.813] [LOG] [SPOTIFY_AUTH] Token is expired. It will be refreshed
          0|mm       | [09:33:25.820] [LOG] [SPOTIFY_AUTH] Token refreshing...
          0|mm       | [09:33:26.055] [LOG] Connecting socket for: MMM-Trello
          0|mm       | [09:33:26.066] [LOG] Starting node helper for: MMM-Trello
          0|mm       | [09:33:26.077] [LOG] Sockets connected & modules started ...
          0|mm       | [09:33:26.085] [LOG]
          0|mm       | Ready to go! Please point your browser to: http://localhost:8080
          0|mm       | Starting chromium browser now, have patience, it takes a minute
          
          /home/pi/.pm2/logs/mm-error.log last 100 lines:
          0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
          0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
          0|mm       |     at Console.con.(anonymous function) [as log] (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
          0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
          0|mm       |     at process.emit (events.js:198:13)
          0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
          0|mm       | ./run-start.sh: line 67: 24163 Aborted                 (core dumped) chromium-browser -noerrdialogs -kiosk -start_maximized --disable-infobars --app=http://localhost:$port --ignore-certificate-errors-spki-list --ignore-ssl-errors --ignore-certificate-errors 2> /dev/null
          0|mm       | npm ERR! code ELIFECYCLE
          0|mm       | npm ERR! errno 134
          0|mm       | npm ERR! magicmirror@2.10.0 start: `./run-start.sh`
          0|mm       | npm ERR! Exit status 134
          0|mm       | npm ERR! 
          0|mm       | npm ERR! Failed at the magicmirror@2.10.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/2020-01-10T19_57_51_885Z-debug.log
          0|mm       | events.js:174
          0|mm       |       throw er; // Unhandled 'error' event
          0|mm       |       ^
          0|mm       | 
          0|mm       | Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
          0|mm       |     at doWrite (_stream_writable.js:411:19)
          0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
          0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
          0|mm       |     at Console.con.(anonymous function) [as log] (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
          0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
          0|mm       |     at process.emit (events.js:198:13)
          0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
          0|mm       | ./run-start.sh: line 67:  4392 Aborted                 (core dumped) chromium-browser -noerrdialogs -kiosk -start_maximized --disable-infobars --app=http://localhost:$port --ignore-certificate-errors-spki-list --ignore-ssl-errors --ignore-certificate-errors 2> /dev/null
          0|mm       | npm ERR! code ELIFECYCLE
          0|mm       | npm ERR! errno 134
          0|mm       | npm ERR! magicmirror@2.10.0 start: `./run-start.sh`
          0|mm       | npm ERR! Exit status 134
          0|mm       | npm ERR! 
          0|mm       | npm ERR! Failed at the magicmirror@2.10.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/2020-01-10T20_56_57_189Z-debug.log
          0|mm       | events.js:174
          0|mm       |       throw er; // Unhandled 'error' event
          0|mm       |       ^
          0|mm       | 
          0|mm       | Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
          0|mm       |     at doWrite (_stream_writable.js:411:19)
          0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
          0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
          0|mm       |     at Console.con.(anonymous function) [as log] (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
          0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
          0|mm       |     at process.emit (events.js:198:13)
          0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
          0|mm       | events.js:174
          0|mm       |       throw er; // Unhandled 'error' event
          0|mm       |       ^
          0|mm       | 
          0|mm       | Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
          0|mm       |     at doWrite (_stream_writable.js:411:19)
          0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
          0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
          0|mm       |     at Console.con.(anonymous function) [as log] (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
          0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
          0|mm       |     at process.emit (events.js:198:13)
          0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
          0|mm       | events.js:174
          0|mm       |       throw er; // Unhandled 'error' event
          0|mm       |       ^
          0|mm       | 
          0|mm       | Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
          0|mm       |     at doWrite (_stream_writable.js:411:19)
          0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
          0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
          0|mm       |     at Console.con.(anonymous function) [as log] (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
          0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
          0|mm       |     at process.emit (events.js:198:13)
          0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
          0|mm       | events.js:174
          0|mm       |       throw er; // Unhandled 'error' event
          0|mm       |       ^
          0|mm       | 
          0|mm       | Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
          0|mm       |     at doWrite (_stream_writable.js:411:19)
          0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
          0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
          0|mm       |     at Console.con.(anonymous function) [as log] (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
          0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
          0|mm       |     at process.emit (events.js:198:13)
          0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
          0|mm       | events.js:174
          0|mm       |       throw er; // Unhandled 'error' event
          0|mm       |       ^
          0|mm       | 
          0|mm       | Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
          0|mm       |     at doWrite (_stream_writable.js:411:19)
          0|mm       |     at writeOrBuffer (_stream_writable.js:399:5)
          0|mm       |     at Socket.Writable.write (_stream_writable.js:299:11)
          0|mm       |     at Console.con.(anonymous function) [as log] 
          (/home/pi/MagicMirror/node_modules/console-stamp/main.js:150:46)
          0|mm       |     at process.<anonymous> (/home/pi/MagicMirror/js/app.js:40:10)
          0|mm       |     at process.emit (events.js:198:13)
          0|mm       |     at process._fatalException (internal/bootstrap/node.js:497:27)
          

          :::

          1 Reply Last reply Reply Quote 0
          • J Offline
            jorgnyg
            last edited by Jan 11, 2020, 10:01 AM

            Some additional logs from /home/pi/.npm/_logs

            0 info it worked if it ends with ok
            1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
            2 info using npm@6.13.4
            3 info using node@v10.18.1
            4 verbose run-script [ 'prestart', 'start', 'poststart' ]
            5 info lifecycle magicmirror@2.10.0~prestart: magicmirror@2.10.0
            6 info lifecycle magicmirror@2.10.0~start: magicmirror@2.10.0
            7 verbose lifecycle magicmirror@2.10.0~start: unsafe-perm in lifecycle true
            8 verbose lifecycle magicmirror@2.10.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
            9 verbose lifecycle magicmirror@2.10.0~start: CWD: /home/pi/MagicMirror
            10 silly lifecycle magicmirror@2.10.0~start: Args: [ '-c', './run-start.sh' ]
            11 silly lifecycle magicmirror@2.10.0~start: Returned: code: 134  signal: null
            12 info lifecycle magicmirror@2.10.0~start: Failed to exec start script
            13 verbose stack Error: magicmirror@2.10.0 start: `./run-start.sh`
            13 verbose stack Exit status 134
            13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
            13 verbose stack     at EventEmitter.emit (events.js:198:13)
            13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
            13 verbose stack     at ChildProcess.emit (events.js:198:13)
            13 verbose stack     at maybeClose (internal/child_process.js:982:16)
            13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
            14 verbose pkgid magicmirror@2.10.0
            15 verbose cwd /home/pi/MagicMirror
            16 verbose Linux 4.19.75+
            17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
            18 verbose node v10.18.1
            19 verbose npm  v6.13.4
            20 error code ELIFECYCLE
            21 error errno 134
            22 error magicmirror@2.10.0 start: `./run-start.sh`
            22 error Exit status 134
            23 error Failed at the magicmirror@2.10.0 start script.
            23 error This is probably not a problem with npm. There is likely additional logging output above.
            24 verbose exit [ 134, true ]
            
            
            S 1 Reply Last reply Jan 11, 2020, 1:08 PM Reply Quote 0
            • S Offline
              sdetweil @jorgnyg
              last edited by Jan 11, 2020, 1:08 PM

              @jorgnyg said in Error [ERR_STREAM_DESTROYED]:

              Exit status 134

              when this happens can u use a terminal window and do

              ps -ef | grep -v color | grep chromium
              

              I think the chromium browser is hung
              and we keep trying to restart and it fails

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • S Offline
                sdetweil @jorgnyg
                last edited by Jan 17, 2020, 12:03 AM

                @jorgnyg this is a bug in the run-start.sh script

                get a new one here

                cd !/MagicMirror
                curl -sL  https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/run-start.sh >run-start.sh
                

                Sam

                How to add modules

                learning how to use browser developers window for css changes

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