Read the statement by Michael Teeuw here.
MagicMirror restarts all the time
-
Hello,
I have to admit, that I´m an absolute noob. I was able to run the MagicMirror on a raspi3 with different modules. Yesterday I installed some updates (MM and ioserver) and since then, I have the problem, that my MM stops after 78 seconds everytime after a restart. What did I do wrong?
Thanks for your help,
Laurids -
@laurids need to see the messages where u start mm. either npm start or pm2. if pm2, then the
pm2 logs --lines=100
will provide the info -
@sdetweil thank you for your reply. I´m sorry for this stupid question, but how can i copy text out of a log-file, when I use ssh? My pm2.log has more than 10000 lines, which are important for you?
-
@laurids something near the end that shows around the time of the failure
-
@sdetweil I hope that this is helping
2021-05-08T17:37:34: PM2 log: PM2 successfully stopped 2021-05-08T17:38:09: PM2 log: =============================================================================== 2021-05-08T17:38:09: PM2 log: --- New PM2 Daemon started ---------------------------------------------------- 2021-05-08T17:38:09: PM2 log: Time : Sat May 08 2021 17:38:09 GMT+0200 (GMT+02:00) 2021-05-08T17:38:09: PM2 log: PM2 version : 4.2.3 2021-05-08T17:38:09: PM2 log: Node.js version : 10.24.1 2021-05-08T17:38:09: PM2 log: Current arch : arm 2021-05-08T17:38:09: PM2 log: PM2 home : /home/pi/.pm2 2021-05-08T17:38:09: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid 2021-05-08T17:38:09: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock 2021-05-08T17:38:09: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock 2021-05-08T17:38:09: PM2 log: Application log path : /home/pi/.pm2/logs 2021-05-08T17:38:09: PM2 log: Worker Interval : 30000 2021-05-08T17:38:09: PM2 log: Process dump file : /home/pi/.pm2/dump.pm2 2021-05-08T17:38:09: PM2 log: Concurrent actions : 2 2021-05-08T17:38:09: PM2 log: SIGTERM timeout : 1600 2021-05-08T17:38:09: PM2 log: =============================================================================== 2021-05-08T17:38:10: PM2 log: App [mm:0] starting in -fork mode- 2021-05-08T17:38:10: PM2 log: App [mm:0] online 2021-05-08T18:09:01: PM2 log: Stopping app:mm id:0 2021-05-08T18:09:03: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:03: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:03: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:04: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:05: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:05: PM2 log: pid=890 msg=failed to kill - retrying in 100ms 2021-05-08T18:09:05: PM2 log: Process with pid 890 still alive after 1600ms, sending it SIGKILL now... 2021-05-08T18:09:05: PM2 log: App [mm:0] exited with code [0] via signal [SIGKILL] 2021-05-08T18:09:06: PM2 log: pid=890 msg=process killed 2021-05-08T18:09:07: PM2 log: PM2 successfully stopped 2021-05-08T18:09:43: PM2 error: TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an in at Object.writeFileSync (fs.js:1460:5) at module.exports.Daemon.innerStart (/usr/local/lib/node_modules/pm2/lib/Daemon.js:90:8) at Domain.<anonymous> (/usr/local/lib/node_modules/pm2/lib/Daemon.js:62:10) at Domain.run (domain.js:370:15) at module.exports.Daemon.start (/usr/local/lib/node_modules/pm2/lib/Daemon.js:61:5) at Object.<anonymous> (/usr/local/lib/node_modules/pm2/lib/Daemon.js:455:10) at Module._compile (internal/modules/cjs/loader.js:1063:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10) at Module.load (internal/modules/cjs/loader.js:928:32) at Function.Module._load (internal/modules/cjs/loader.js:769:14) 2021-05-08T18:09:43: PM2 log: =============================================================================== 2021-05-08T18:09:43: PM2 log: --- New PM2 Daemon started ---------------------------------------------------- 2021-05-08T18:09:43: PM2 log: Time : Sat May 08 2021 18:09:43 GMT+0200 (Mitteleuropäische Sommerzeit)2021-05-08T18:09:43: PM2 log: PM2 version : 4.2.3 2021-05-08T18:09:43: PM2 log: Node.js version : 14.16.1 2021-05-08T18:09:43: PM2 log: Current arch : arm 2021-05-08T18:09:43: PM2 log: PM2 home : /home/pi/.pm2 2021-05-08T18:09:43: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid 2021-05-08T18:09:43: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock 2021-05-08T18:09:43: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock 2021-05-08T18:09:43: PM2 log: Application log path : /home/pi/.pm2/logs -
@laurids sadly no. pm2 splits output inyo two logs
errors and output. this looks like the output.
errors are printed first
send the output to a file
pm2 logs --lines=100 >somefile
then edit somfile
-
@sdetweil here are some lines of the error.log. They repeat all the time:
[17:05:32.926] [ERROR] error: cannot lock ref 'refs/tags/v2.12.0': unable to resolve reference 'refs/tags/v2.12.0': Von https://github.com/MichMich/MagicMirror ! [neues Tag] v2.12.0 -> v2.12.0 (kann lokale Referenz nicht aktualisieren) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! magicmirror@2.10.1 start: `./run-start.sh` npm ERR! Exit status 1 npm ERR!. npm ERR! Failed at the magicmirror@2.10.1 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2021-05-08T15_37_28_171Z-debug.log /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT [08.05.2021 17:39.18.396] [WARN] The module 'currentweather' is deprecated in favor of the 'weather'-module, please [08.05.2021 17:39.18.402] [WARN] The module 'weatherforecast' is deprecated in favor of the 'weather'-module, please[08.05.2021 17:40.30.779] [ERROR] Whoops! There was an uncaught exception... [08.05.2021 17:40.30.812] [ERROR] Error: connect ECONNREFUSED 192.168.178.1:1012 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { errno: 'ECONNREFUSED', code: 'ECONNREFUSED', syscall: 'connect', address: '192.168.178.1', port: 1012 } [08.05.2021 17:40.30.816] [ERROR] MagicMirror will not quit, but it might be a good idea to check why this happened. [08.05.2021 17:40.30.819] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://githu[08.05.2021 17:40.36.632] [ERROR] Failed to fetch git data for MMM-ioBroker: Error: block timeout reached [08.05.2021 17:40.37.844] [ERROR] Failed to fetch git data for default: Error: block timeout reached [08.05.2021 17:50.40.859] [ERROR] Failed to fetch git data for default: Error: block timeout reached [08.05.2021 17:53.34.562] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [08.05.2021 17:53.34.564] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087and
[09.05.2021 11:28.04.125] [ERROR] MagicMirror will not quit, but it might be a good idea to check why this happened. [09.05.2021 11:28.04.126] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://githu[09.05.2021 11:28.04.676] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:28.04.679] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:28.04.681] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:28.04.683] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:28.04.686] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:28.04.691] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:28.06.421] [ERROR] Failed to fetch git data for MMM-FRITZ-Box-Callmonitor: Error: block timeout reache[09.05.2021 11:29.04.732] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:29.04.737] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:29.04.740] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:29.04.743] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:29.04.746] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:29.04.751] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087 [09.05.2021 11:29.30.532] [WARN] The module 'currentweather' is deprecated in favor of the 'weather'-module, please [09.05.2021 11:29.30.535] [WARN] The module 'weatherforecast' is deprecated in favor of the 'weather'-module, please[09.05.2021 11:29.34.824] [ERROR] Whoops! There was an uncaught exception... [09.05.2021 11:29.34.836] [ERROR] Error: connect ECONNREFUSED 192.168.178.1:1012 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { errno: 'ECONNREFUSED', code: 'ECONNREFUSED', syscall: 'connect', address: '192.168.178.1', port: 1012 -
@laurids said in MagicMirror restarts all the time:
errno: ‘ECONNREFUSED’,
code: ‘ECONNREFUSED’,
syscall: ‘connect’,
address: ‘192.168.178.1’,and
[09.05.2021 11:29.04.737] [ERROR] Got error: connect ECONNREFUSED 127.0.0.1:8087look like the indicators…
whatever is using 192.168.178.1 looks like it didn’t handle the error
this 127.0.0.1:8087 is localhost, on the same machine, some server maybe related to above…
-
@sdetweil thanks for your help. I have to admit, that I don´t have a clue how to fix the errors ;) I think I just give it another try with a new installation.
-
@laurids I’m assuming it’s some module you’ve installed, so looking at the config.js may give a clue
-
@sdetweil I really don´t know what was wrong. Now I´ve made a new installation, copied my old config.js and it works. Thanks for your help.
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