Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
@sdetweil Everything has appeared to be simpler than we thought. I moved the files which were the obstacle on the way of working of your script to another folder, then updated the mirror using your script. After that I moved those files back and now mirror is working.
-
@bobwilliams What files? My script should handle it. So I want to understand.
-
@sdetweil /MagicMirror/installers/mm.sh
/MagicMirror/modules/default/calendar/calendar.js
/MagicMirror/modules/default/currentweather/currentweather.js
/MagicMirror/modules/default/weather/weather.js /MagicMirror/modules/default/weatherforecast/weatherforecast.js
/MagicMirror/package-lock.json
/MagicMirror/run-start.sh
when updating, your script asked to save these files or not. if I wrote yes, it was not updated, if I wrote no, the update went fine but the mirror stopped working. I just moved these files, updated the mirror, and put them back in place. and the mirror works -
@bobwilliams Ok. I put a fix in for Save=yes. Save=No should replace them w local repo version…and then upgrade.
Will have to build test. Really want to see the upgrade log, and pm2 logs for why it stoppexy
-
@sdetweil sent by mail
-
@bobwilliams got them thanks… you didn’t happen to save that ‘failing’ MagicMirror folder did you?
-
@sdetweil no, it didn’t work out
-
@sdetweil Have you looked at what was the problem?
-
@bobwilliams yes, the merge returns an error i don’t handle… but I don’t know what the error means…
so was hoping u had the folder saved, so I could get a copy to test with… -
I have submitted this script as part of pull request 1789
-
@sdetweil Idk why or if this is even the case but I updated MMM-EventHorizon and now I get a black screen and server shows errored below…any ideas how to fix?
pi@raspberrypi:~ $ pm2 restart mm Use --update-env to update environment variables [PM2] Applying action restartProcessId on app [mm](ids: 1) [PM2] [mm](1) ✓ ┌─────────────┬────┬──────┬────────┬─────────┬─────┬────────┬──────────┐ │ Name │ id │ mode │ status │ ↺ │ cpu │ memory │ ├─────────────┼────┼──────┼────────┼─────────┼─────┼────────┼──────────┤ │ mm │ 1 │ N/A │ fork │ online │ 5 │ 0% │ 2.5 MB │ │ omx_stream1 │ 2 │ N/A │ fork │ online │ 28 │ 0% │ 2.8 MB │ │ omx_stream2 │ 3 │ N/A │ fork │ online │ 28 │ 0% │ 2.7 MB │ │ omx_stream3 │ 4 │ N/A │ fork │ online │ 28 │ 0% │ 2.7 MB │ │ server │ 0 │ N/A │ fork │ errored │ 0 │ 0% │ 0 B │ -
@sdetweil Actually idk what the issue is…black screen even though all show online. Odd
-
@sdetweil I fixed the server issue and it shows online. But still get a black screen when start MM. So frustrating
-
@sdetweil I stand corrected I did not fix server issue…
-
This post is deleted! -
pi@raspberrypi:~ $ pm2 logs [TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option) /home/pi/.pm2/pm2.log last 15 lines: PM2 | 2019-12-07T15:03:42: PM2 log: App [omx_stream1:2] exited with code [1] via signal [SIGINT] PM2 | 2019-12-07T15:03:42: PM2 log: App [omx_stream1:2] starting in -fork mode- PM2 | 2019-12-07T15:03:42: PM2 log: App [omx_stream1:2] online PM2 | 2019-12-07T15:03:42: PM2 log: App [omx_stream2:3] exited with code [1] via signal [SIGINT] PM2 | 2019-12-07T15:03:42: PM2 log: App [omx_stream2:3] starting in -fork mode- PM2 | 2019-12-07T15:03:42: PM2 log: App [omx_stream2:3] online PM2 | 2019-12-07T15:04:13: PM2 log: App [omx_stream3:4] exited with code [1] via signal [SIGINT] PM2 | 2019-12-07T15:04:13: PM2 log: App [omx_stream3:4] starting in -fork mode- PM2 | 2019-12-07T15:04:13: PM2 log: App [omx_stream3:4] online PM2 | 2019-12-07T15:04:14: PM2 log: App [omx_stream1:2] exited with code [1] via signal [SIGINT] PM2 | 2019-12-07T15:04:14: PM2 log: App [omx_stream1:2] starting in -fork mode- PM2 | 2019-12-07T15:04:14: PM2 log: App [omx_stream1:2] online PM2 | 2019-12-07T15:04:14: PM2 log: App [omx_stream2:3] exited with code [1] via signal [SIGINT] PM2 | 2019-12-07T15:04:14: PM2 log: App [omx_stream2:3] starting in -fork mode- PM2 | 2019-12-07T15:04:14: PM2 log: App [omx_stream2:3] online /home/pi/.pm2/logs/omx-stream2-error.log last 15 lines: /home/pi/.pm2/logs/omx-stream3-error.log last 15 lines: /home/pi/.pm2/logs/omx-stream1-error.log last 15 lines: 2|omx_stre | 2|omx_stre | # 2|omx_stre | # Fatal process OOM in heap setup 2|omx_stre | # 2|omx_stre | 2|omx_stre | /usr/bin/env: error while loading shared libraries: /usr/lib/arm-linux-gnueabihf/libarmmem.so: cannot make segment writable for relocation: Cannot allocate memory 2|omx_stre | /usr/bin/omxplayer: xmalloc: .././subst.c:3868: cannot allocate 131 bytes (159744 bytes allocated) 2|omx_stre | /usr/bin/omxplayer: line 67: 5417 Aborted (core dumped) LD_LIBRARY_PATH="$OMXPLAYER_LIBS${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" $OMXPLAYER_BIN "$@" 2|omx_stre | /usr/bin/omxplayer.bin: error while loading shared libraries: libmpg123.so.0: failed to map segment from shared object 2|omx_stre | /usr/bin/omxplayer: line 67: 9527 Aborted (core dumped) LD_LIBRARY_PATH="$OMXPLAYER_LIBS${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" $OMXPLAYER_BIN "$@" 2|omx_stre | /usr/bin/omxplayer: line 67: 10115 Killed LD_LIBRARY_PATH="$OMXPLAYER_LIBS${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" $OMXPLAYER_BIN "$@" 2|omx_stre | /usr/bin/omxplayer: line 67: 13967 Killed LD_LIBRARY_PATH="$OMXPLAYER_LIBS${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" $OMXPLAYER_BIN "$@" 2|omx_stre | process 25324: arguments to dbus_message_new_method_call() were incorrect, assertion "destination == NULL || _dbus_check_is_valid_bus_name (destination)" failed in file ../../../dbus/dbus-message.c line 1370. 2|omx_stre | This is normally a bug in some application using the D-Bus library. /home/pi/.pm2/logs/server-error.log last 15 lines: 0|server | at _handle.lookup (dgram.js:266:18) 0|server | at args.(anonymous function) (/usr/lib/node_modules/pm2/node_modules/event-loop-inspector/index.js:138:29) 0|server | at process._tickCallback (internal/process/next_tick.js:178:19) 0|server | Error: bind EADDRNOTAVAIL 10.30.1.223:1905 0|server | at _handle.lookup (dgram.js:266:18) 0|server | at args.(anonymous function) (/usr/lib/node_modules/pm2/node_modules/event-loop-inspector/index.js:138:29) 0|server | at process._tickCallback (internal/process/next_tick.js:178:19) 0|server | Error: bind EADDRNOTAVAIL 10.30.1.223:1905 0|server | at _handle.lookup (dgram.js:266:18) 0|server | at args.(anonymous function) (/usr/lib/node_modules/pm2/node_modules/event-loop-inspector/index.js:138:29) 0|server | at process._tickCallback (internal/process/next_tick.js:178:19) 0|server | Error: bind EADDRNOTAVAIL 10.30.1.223:1905 0|server | at state.handle.lookup (dgram.js:242:18) 0|server | at args.(anonymous function) (/usr/lib/node_modules/pm2/node_modules/event-loop-inspector/index.js:138:29) 0|server | at process._tickCallback (internal/process/next_tick.js:63:19) /home/pi/.pm2/logs/server-out.log last 15 lines: 0|server | { roomName: 'TV Room', volume: 15 } ], 0|server | playMode: { shuffle: true, repeat: 'all', crossfade: false }, 0|server | pauseOthers: false } } 0|server | 2019-12-07T19:32:42.519Z INFO http server listening on 0.0.0.0 port 5005 0|server | 2019-12-07T19:37:02.420Z INFO Could not find file /home/pi/node-sonos-http-api/settings.json 0|server | 2019-12-07T19:37:03.086Z INFO Presets loaded: { example: 0|server | { players: 0|server | [ { roomName: 'Bathroom', volume: 10 }, 0|server | { roomName: 'Kitchen', volume: 10 }, 0|server | { roomName: 'Office', volume: 10 }, 0|server | { roomName: 'Bedroom', volume: 10 }, 0|server | { roomName: 'TV Room', volume: 15 } ], 0|server | playMode: { shuffle: true, repeat: 'all', crossfade: false }, 0|server | pauseOthers: false } } 0|server | 2019-12-07T19:37:07.083Z INFO http server listening on 0.0.0.0 port 5005 /home/pi/.pm2/logs/mm-error.log last 15 lines: 1|mm | at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-RTSPStream/node_helper.js:563:3) 1|mm | at Module._compile (internal/modules/cjs/loader.js:711:30) 1|mm | at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10) 1|mm | at Module.load (internal/modules/cjs/loader.js:620:32) 1|mm | { Error: Cannot find module 'node_helper' 1|mm | at Module._resolveFilename (internal/modules/cjs/loader.js:602:15) 1|mm | at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12) 1|mm | at Function.Module._load (internal/modules/cjs/loader.js:528:25) 1|mm | at Module.require (internal/modules/cjs/loader.js:658:17) 1|mm | at require (internal/modules/cjs/helpers.js:20:18) 1|mm | at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-RTSPStream/node_helper.js:9:18) 1|mm | at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-RTSPStream/node_helper.js:563:3) 1|mm | at Module._compile (internal/modules/cjs/loader.js:711:30) 1|mm | at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10) 1|mm | at Module.load (internal/modules/cjs/loader.js:620:32) code: 'MODULE_NOT_FOUND' } /home/pi/.pm2/logs/mm-out.log last 15 lines: 1|mm | If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues 1|mm | Launching application. 1|mm | Shutting down server... 1|mm | 1|mm | > magicmirror@2.8.0 start /home/pi/MagicMirror 1|mm | > sh run-start.sh 1|mm | 1|mm | Starting MagicMirror: v2.8.0 1|mm | Loading config ... 1|mm | Loading module helpers ... 1|mm | Loading module helpers ... 1|mm | Whoops! There was an uncaught exception... 1|mm | MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? 1|mm | If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues 1|mm | Launching application. -
I updated MMM-EventHorizon and now I get a black screen and server shows errored . . .
If MMM-EventHorizon is the cause simply disable it.
We can troubleshoot in another topic instead of hijacking this one.
-
@swvalenti said in new update/upgrade script, ready for testing:
|server | Error: bind EADDRNOTAVAIL 10.30.1.223:1905
looks like the omxplayer task is hung, holding onto ports… reboot time…
-
@sdetweil Hi, do have to install the script in the MM Folder?
-
@Stoffbeuteluwe no… run the script from the web.
the update will now install the new scripts in the installers folder, for the future
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login