I´ve tried to change the fotos into the same format 1280x1024 and I´ve changed the ending *.jpeg to *.jpg. Now the mirror runs since three days without black screen. I hope the problem is solved.
Read the statement by Michael Teeuw here.
Posts made by Hakupapa
-
RE: Black screen after some time
-
RE: Black screen after some time
Here is the log after black screen. Putty already works so I think the pi is not crashed:
pi@raspberrypi:~ $ pm2 logs mm [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 | Module helper loaded: newsfeed 0|mm | All module helpers loaded. 0|mm | Starting server on port 8080 ... 0|mm | Server started ... 0|mm | Connecting socket for: calendar 0|mm | Starting node helper for: calendar 0|mm | Connecting socket for: MMM-ImagesPhotos 0|mm | Starting node helper for: MMM-ImagesPhotos 0|mm | Connecting socket for: newsfeed 0|mm | Starting module: newsfeed 0|mm | Sockets connected & modules started ... 0|mm | Launching application. 0|mm | Create new news fetcher for url: http://www.n-tv.de/rss - Interval: 300000 0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/htschetschorke%40gmail.com/private-0b52e66697c4e6bfeca31befce749cc2/basic.ics - Interval: 300000 0|mm | Create new news fetcher for url: http://www.tagesschau.de/xml/rss2 - Interval: 300000
/home/pi/.pm2/logs/mm-error.log last 15 lines: 0|mm | [893:1023/053104.910263:FATAL:memory.cc(22)] Out of memory. size=79265792 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | [865:1024/144331.033064:FATAL:memory.cc(22)] Out of memory. size=97656832 0|mm | [832:1024/171926.281460:FATAL:bus.cc(1152)] D-Bus connection was disconnected. Aborting. 0|mm | [815:1024/172851.280816:FATAL:bus.cc(1152)] D-Bus connection was disconnected. Aborting. 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | [872:1024/191309.306465:FATAL:memory.cc(22)] Out of memory. size=109969408 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | [865:1024/231803.240907:FATAL:memory.cc(22)] Out of memory. size=109969408 0|mm | Invalid SOS parameters for sequential JPEG 0|mm | [855:1025/081629.946605:FATAL:memory.cc(22)] Out of memory. size=89653248
Maybe it has to do with MMM-Images Photos and problems with some jpg Files. Does anybody has an idea?
-
Black screen after some time
Hey there,
I have installed the mirror new two or three month ago. Since this time I become black screens after some time. The Mirror doesn´t crash, the screen just turn to black. My old Mirror (1 year old) with same modules but without any updates does not have this problem. So I think the reason could be an update. Does anyone else knows this problem and a solution. I´ve tried different things (os update, MM update) but it is becoming worser.
here my pm2 log without black screen
pi@raspberrypi:~ $ Use `pm2 logs mm [--lines 1000]` to display logs status │ online │ │ name │ mm │ │ restarts │ 0 │ │ uptime │ 14m │ │ script path │ /home/pi/mm.sh │ │ script args │ N/A │ │ error log path │ /home/pi/.pm2/logs/mm-error.log │ │ out log path │ /home/pi/.pm2/logs/mm-out.log │ │ pid path │ /home/pi/.pm2/pids/mm-0.pid │ │ interpreter │ bash │ │ interpreter args │ N/A │ │ script id │ 0 │ │ exec cwd │ /home/pi │ │ exec mode │ fork_mode │ │ node.js version │ N/A │ │ watch & reload │ ✘ │ │ unstable restarts │ 0 │ │ created at │ 2018-10-25T05:27:10.221Z │ └───────────────────┴─────────────────────────────────┘ Add your own code metrics: http://bit.ly/code-metrics Use `pm2 logs mm [--lines 1000]` to display logs Use `pm2 monit` to monitor CPU and Memory usage mm
Now I am wating for the next black screen, then I will post the logfile again.
Greetings
Hakupapa -
RE: Problems with installing the Mirror new
Thx for the answer. I attempted a little bit and I found the problems.
The biggest problem was the new but cheap 128 GB card. I had also problems while starting. That seems to be also the problem for other Installations.
The error in my first thread is not important. I used another smaller sd card and I got the error too but the mm works allright. So the problem seems to be solved.
Greetings from Hakupapa -
Problems with installing the Mirror new
Hi there,
because I was not able to move to a sd card with bigger size, I tried a new Installation. This also did not worked.
I took the actually raspian full streich, just like recommended. This works perfect. Then I used ssh and installed MM automatic with Code from michmich. Everything fine.Question about using pm2 I answered with y. I saw no errors. After starting with the command on the last line I got these errors After sockets connected & modules startet.Whoops! There was an uncaught exception…
{ Error: listen EADDRINUSE 127.0.0.1:8080
at Object._errnoException (util.js:1024:11)
at _exceptionWithHostPort (util.js:1046:20)
at Server.setupListenHandle [as _listen2] (net.js:1351:14)
at listenInCluster (net.js:1392:12)
at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)
at GetAddrInfoReqQrap.onlookup [as oncomplete] (dns.js:97:10)
code: ´EADDRINUSE´,
errno: ´EADDRINUSE´,
syscall: ´listen´,
address: ´127.0.0.1´,
port: 8080 }
MagicMirror will not quit, but it might be a good Idea to check why this happend. Maybe not internet connection?
If you think this really is an issue, please open an issue on …
Launching application.
After that there was no way for ssh. System hangs on. Mirror doesnt start. There was allready the raspian Desktop also after power off.
Please help. Dont know what I made wrong. -
RE: Change to another SD with bigger size
@sean
thx for the link. I tried something like this. But this is much harder and there were a lot of possible mistakes I could make. I think it is easyer to reinstall a new raspian an the magicmirror. I had never thougt, that there is no easy way to move to a bigger sd card, but it seems to be this way. -
RE: Change to another SD with bigger size
Hello sean,
the question is not stupid. I tried but there is no choice in raspi config, because I use noobs. That is also the reason why does fdisk cant write new partitionetable after reboot. -
Change to another SD with bigger size
Hey there,
I have a MM working since ca. 1,5 years with the standard modules and I am very happy about it. Now me wife would like to have family photos on the MM. I found some good modules like MMM-ImagesPhotos and in one hour I had some Photos on the mirror. So far so good.
Then the problems started when I found out, that there isn´t enoug space for more then 10 Fotos. So I bought a bigger card and played the image to this new card. Unfortunately the partition size do not changes automaticly. I´ve tried differend ways to change the partition table but nothing worked (fdisk, gparted, acronis backup).
So I read a lot and found out that the problem is noobs and there is no solution.The Idea now is to create a new partition with fat32 and create a folder in this new Partition. Then I would like to link from the modul (MMM-ImagesPhotos) to this new folder.
There is a link in the MMM-ImagesPhotos.js
getPhotos: function() { var urlApHelper = "/Modules/MMM-ImagesPhotos/Photos"; var self = this; var retry = true;
I´ve changed to this
getPhotos: function() {
var urlApHelper = “/media/pi/B82B-6FB6/fotos”;
var self = this;
var retry = true;but it doesn´t work.
Now the questions:
-
Does here anybody knows a way to move to a bigger sd card without new installing everything?
-
Does anybody knows how to say in MMM-ImagesPhotos.js that the photos are in another directory (on another partition)?
I would be very happe for every idea.
-