The mirror starts every day automatically with pm2 throw a smart plug and the raspberry shuts down throw corn every day.
At the first start, he wont run with the log above, when i reboot the pi he is working without any problems till he shuts down at the end of the day.
All updates were made by me, none automatically.
@thedk said in Mirror starts not correct:
Jusat am month ago, it starts again, but with an other fault
0|mm | > magicmirror@2.8.0 start /home/pi/MagicMirror 0|mm | > sh run-start.sh 0|mm | /home/pi/MagicMirror/node_modules/electron/dist/electron: relocation error: /home/pi/MagicMirror/node_modules/electron/dist/libffmpeg.so: symbol cnprantf, version GLIBC_2.4 not defined in file libc.so.6 with link time reference 0|mm | npm 0|mm | ERR! file sh 0|mm | npm ERR! code ELIFECYCLE 0|mm | npm ERR! errno ENOENT 0|mm | npm ERR! syscall spawn 0|mm | npm 0|mm | ERR! magicmirror@2.8.0 start: `sh run-start.sh` 0|mm | npm ERR! spawn ENOENT 0|mm | npm 0|mm | ERR! 0|mm | npm ERR! Failed at the magicmirror@2.8.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-08-12T05_54_45_996Z-debug.logI didnt changed anything, the error came from one day to the other an i just see the startscreen and the mirror wont start.
Could somebody help?
About a month ago and now again…
Everything is up to date but the issue is still there. Each day when the Mirror starts, the error comes second for second. A reboot solves the problem the mirror is runinng without problems.
Are there people where the Mirror is working für ober two months without issues? ^^
I didnt upgrade, i made an complete new installation cause of the issue i had before.
Since two days the mirror has no error and everything goes fine, dont know why. I made no upgrade or similar but will do this now. Maybe the issue is gone with that.
Thanks for your help.
Jusat am month ago, it starts again, but with an other fault
0|mm | > magicmirror@2.8.0 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm | /home/pi/MagicMirror/node_modules/electron/dist/electron: relocation error: /home/pi/MagicMirror/node_modules/electron/dist/libffmpeg.so: symbol cnprantf, version GLIBC_2.4 not defined in file libc.so.6 with link time reference
0|mm | npm
0|mm | ERR! file sh
0|mm | npm ERR! code ELIFECYCLE
0|mm | npm ERR! errno ENOENT
0|mm | npm ERR! syscall spawn
0|mm | npm
0|mm | ERR! magicmirror@2.8.0 start: `sh run-start.sh`
0|mm | npm ERR! spawn ENOENT
0|mm | npm
0|mm | ERR!
0|mm | npm ERR! Failed at the magicmirror@2.8.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-08-12T05_54_45_996Z-debug.log
I didnt changed anything, the error came from one day to the other an i just see the startscreen and the mirror wont start.
Could somebody help?
@Mykle1
No i cant. I just can reboot or shutdown the Pi by Terminal.
I know i shouldnt unplug the Pi ^^
@Mykle1
I just unplug the Pi sometimes since he is not starting anymore
I know thats not the best way, it’s my 4th Pi ;)
A reinstall wouldnt be the Problem. It is not the first time i have to do this ^^
But i really dont unterstand why he wont start anymore. I also had this before the update, forgot to write. From one to the other the Mirror doesnt starts just with the first start of the day. When i reboot or just unplug the Pi, the mirror starts correct
Could somebody help with this fault?
[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-Remote-Control
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-Remote-Control-Repository
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-ModuleScheduler
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-PIR-Sensor
0|mm | No helper found for module: MMM-EyeCandy.
0|mm | Whoops! There was an uncaught exception...
0|mm | MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm | If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
0|mm | Whoops! There was an uncaught exception...
0|mm | MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm | If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm | at tryModuleLoad (internal/modules/cjs/loader.js:559:12)
0|mm | at Function.Module._load (internal/modules/cjs/loader.js:551:3)
0|mm | at Module.require (internal/modules/cjs/loader.js:658:17)
0|mm | at require (internal/modules/cjs/helpers.js:20:18)
0|mm | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
0|mm | TypeError: Invalid item
0|mm | at Menu.insert (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/browser/api/menu.js:109:11)
0|mm | at Menu.append (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/browser/api/menu.js:104:15)
0|mm | at sorted.forEach (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/browser/api/menu.js:171:10)
0|mm | at Array.forEach (<anonymous>)
0|mm | at Function.Menu.buildFromTemplate (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/browser/api/menu.js:167:10)
0|mm | at App.app.once (/home/pi/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js:240:21)
0|mm | at Object.onceWrapper (events.js:273:13)
0|mm | at App.emit (events.js:187:15)
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
Yesterday i made the update to 2.8.0 and now the mirror starts but i cant see it. I just see the startscreen.
The Log doesnt make sence to me.
The black screen was my fault :(
I did a lil mistake. After setting up a other Pi with MMM and copying my config i had the same problem. So i was checking my config (no syntax error), and everything i could rember was, that i changed this:
var config = {
address: "localhost", // Address to listen on, can be:
// - "localhost", "127.0.0.1", $
// - another specific IPv4/6 to$
// - "", "0.0.0.0", "::" to lis$
// Default, when address config$
port: 8080,
address: "0.0.0.0",
ipWhitelist: [],
to this:
var config = {
address: ["localhost", "0.0.0.0"], // Address to listen on, can be:
// - "localhost", "127.0.0.1", $
// - another specific IPv4/6 to$
// - "", "0.0.0.0", "::" to lis$
// Default, when address config$
port: 8080,
ipWhitelist: [],
And that was everything and cost me a lot of time ^^
This is not possible over a terminal programm?
The Error is back…
0|mm | [9898:0407/121438.093751:FATAL:bus.cc(1151)] D-Bus connection was disconnected. Aborting.
0|mm | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | npm ERR! code ELIFECYCLE
0|mm | npm ERR! errno 1
0|mm | npm ERR! magicmirror@2.7.1 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.7.1 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-04-07T10_21_07_746Z-debug.log
0|mm | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
Tried it, but still the same.
No error in the log but just the black screen.
Dont know what i can try now. Has anybod a idea?
Ah ok.
I just did it in the modul folder and for the PIR modul, not for the rest.
Will try this later.
Hey Guys.
After the Update i got a black screen and it seems not to be the PIR. With the Remote Module i see everything in the Browser, but the screen shows nothing.
This is the LOG
/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm | at IncomingMessage.emit (events.js:187:15)
0|mm | at endReadableNT (_stream_readable.js:1090:12)
0|mm | at process._tickCallback (internal/process/next_tick.js:63:19)
0|mm | npm ERR! code ELIFECYCLE
0|mm | npm ERR! errno 1
0|mm | npm ERR! magicmirror@2.7.1 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.7.1 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-04-06T11_59_36_840Z-debug.log
0|mm | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
the complete Log:
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@6.8.0
3 info using node@v9.11.2
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.7.1~prestart: magicmirror@2.7.1
6 info lifecycle magicmirror@2.7.1~start: magicmirror@2.7.1
7 verbose lifecycle magicmirror@2.7.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.7.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/$
9 verbose lifecycle magicmirror@2.7.1~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.7.1~start: Args: [ ‘-c’, ‘sh run-start.sh’ ]
11 silly lifecycle magicmirror@2.7.1~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.7.1~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.7.1 start: sh run-start.sh
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:180:13)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:180:13)
13 verbose stack at maybeClose (internal/child_process.js:936:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid magicmirror@2.7.1
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 4.14.79-v7+
17 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
18 verbose node v9.11.2
19 verbose npm v6.8.0
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.7.1 start: sh run-start.sh
22 error Exit status 1
23 error Failed at the magicmirror@2.7.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Also with max-width and max-height the map doesnt get smaller, it just moves out of the Display.
A fan wouldnt be a solution. The 5-10 seconds waiting would be ok.
tested it and i dont know why, but it doesnt work.
Thats my custom.css
body {
}
.normal {
color: #fff;
}
.region.top.right,
.region.top.left,
.region.top.center {
top: 80%;
}
.region.bottom.right,
.region.bottom.center,
.region.bottom.left {
bottom: 80%;
}
Nice discussion :)
My thought just was to reduce the temperature of the CPU when the display switches of.
But the point with the network requests is also good!
Thanks for your help.
So i have to change the size of the region where the modul is i guess.
To end this. I tried both, you dont really see any different.