Read the statement by Michael Teeuw here.
my mirror freezes!
-
@Bugsounet so far my 10 different mm systems have been running fine since upgrade (using my upgrade script)
-
weird, thx, i will inspect more
-
@sdetweil Hello, as agreed I deleted the automatic reboot and this morning the MM is blocked (as usual) I use WinScp and when I wanted to quit it he offered to create a folder "my workspace "that’s what I did, I then opened this new file which connects me directly to the MMM-Logging module and after that I don’t know what to do!
-
@Manu85 said in my mirror freezes!:
and when I wanted to quit it he offered to create a folder
sorry, what does that mean?
by adding the mmm-logging module
you get enhanced messages on the terminal window console like this with timestamps[24253:0406/055023.243727:INFO:CONSOLE(107)] "clearing timer", source: http://0.0.0.0:8080/modules/MyCovid19//MyCovid19.js (107) [24253:0406/055023.243800:INFO:CONSOLE(110)] "starting timer", source: http://0.0.0.0:8080/modules/MyCovid19//MyCovid19.js (110) [24253:0406/055023.243847:INFO:CONSOLE(112)] "timer started", source: http://0.0.0.0:8080/modules/MyCovid19//MyCovid19.js (112)
so, you should have started your mirror like this to capture all the traces
npm start >somefile
now that the app is hung, you can open another winscp terminal window and then
cd ~/.MagicMirror
tail somefilewhich will show the last 15 lines of somefile by default
tail -n number somefile
where number is something like 20, 40, 50 will show more linesif you started with pm2, then the output is on the logs…
pm2 logs --lines=100 >somefile
will dump the last 100 lines into somefile so you can examine them -
I have a report which was created in MM “somfile” but I cannot send it because I have this error on the forum
Error
Post content was flagged as spam by Akismet.com -
@Manu85 u can send it to me by email, to my same userid as here at gmail
-
when placing your order I have this:
pi@raspberrypi:~/MagicMirror $ npm start >somefile
[2020-04-06 14:36:28.593] [ERROR] 2020-04-06T14:36:28 { Error: listen EADDRINUSE 127.0.0.1:8080
at Server.setupListenHandle [as _listen2] (net.js:1330:14)
at listenInCluster (net.js:1378:12)
at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
errno: ‘EADDRINUSE’,
code: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘127.0.0.1’,
port: 8080 } (/home/pi/MagicMirror/js/app.js:40 process.)
pi@raspberrypi:~/MagicMirror $ npm start >somefile
[2020-04-06 14:36:28.593] [ERROR] 2020-04-06T14:36:28 { Error: listen EADDRINUSE 127.0.0.1:8080
at Server.setupListenHandle [as _listen2] (net.js:1330:14)
at listenInCluster (net.js:1378:12)
at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
errno: ‘EADDRINUSE’,
code: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘127.0.0.1’,
port: 8080 } (/home/pi/MagicMirror/js/app.js:40 process.) -
@Manu85 that means the mirror is already running, probably cause of pm2… need to stop it first, can’t run two at the same time
-
ok you can tell me how to do it?
-
@Manu85 pm2 stop 0