Read the statement by Michael Teeuw here.
Mirror starts not correct
-
@Mykle1 one of my sd cards suddenly became read only… no fix…
had to buy new sd card
-
@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 ;) -
@thedk said in Mirror starts not correct:
I just unplug the Pi sometimes since he is not starting anymore
You can’t choose “Shut Down” from the desktop? Once the shut down is complete, THEN pull the plug to power down the Pi
-
@sdetweil said in Mirror starts not correct:
one of my sd cards suddenly became read only… no fix…
had to buy new sd cardSux! :-(
-
@Mykle1
No i cant. I just can reboot or shutdown the Pi by Terminal.
I know i shouldnt unplug the Pi ^^ -
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?
-
@thedk Have you upgraded your installation of Raspbian before updating the MM? You would also have to check every module folder that has a package.json and run npm install in the module folder. This has generally worked for most of the guys with the same issue as you have.
-
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.
-
@thedk Please remember to check every module folder that has a package.json in it and run
npm installin those folders as well. -
I will do this.
Thanks.
-
@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? ^^
-
@thedk said in Mirror starts not correct:
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 problemssorry, I am not quite sure I am understanding…
you start the mirror (with pm2? or manually?), and it fails, with the above message
and then you reboot
and it runs ok…
and runs ok for how long?
i have 5 mirror instances, and all have been running for months without issues like this
did u put updates onto your operating system, or were some applied automatically?
libc.so.6 is a system library -
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.
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