Hi guys, I just wanted to say thank you to @bhepler and @sdetweil for trying to help me with this problem.
In the end I just used a very old backup at first and updated it, which worked fine at first and yesterday I tried setting my RPi up from scratch again and it worked perfectly!
I’m sorry for anybody who encounters the same error and tries finding answers here, sadly there doesn’t seem to be a perfect solution for this.
MrKnight230
@sdetweil I did run npm install again now and the output looks like this:
pi@raspberrypi:~/MagicMirror $ npm install
> magicmirror@2.7.1 install /home/pi/MagicMirror
> cd vendor && npm install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
audited 219 packages in 10.29s
found 5 vulnerabilities (4 low, 1 high)
run `npm audit fix` to fix them, or `npm audit` for details
> magicmirror@2.7.1 postinstall /home/pi/MagicMirror
> sh installers/postinstall/postinstall.sh && npm run install-fonts
MagicMirror installation successful!
> magicmirror@2.7.1 install-fonts /home/pi/MagicMirror
> cd fonts && npm install
audited 1 package in 1.092s
found 0 vulnerabilities
npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.
added 7 packages from 10 contributors, updated 6 packages and audited 3468 packages in 63.499s
found 0 vulnerabilities
But it again didn’t change anything.
@sdetweil I actually didn’t but the result stays the same with “DISPLAY=:0”
@sdetweil Well I deactivated VNC, restarted and plugged my keyboard in the RasPi and this too didn’t change anything sadly.
@sdetweil Thanks for the suggestion, it successfully installed version 6.9.0 but sadly didn’t solve or even change anything about the problem.
@sdetweil
The RasPi is connected via HDMI to a Display and I’m using VNC to configure it. I had a previous install where everything worked with pm2 and manually using the command “npm start”.
Hi,
I encountered a problem that was already mentioned in this post:
https://forum.magicmirror.builders/topic/7183/mm-not-loading-on-startup-or-manually
But because this thread is unsolved and the last answer is more than 11 Months old I would like to try asking again for answers in this thread.
I am currently setting my RasPi 3 B up from start.
I downloaded the newest Raspbian with Desktop, installed and updated it and ran the one-line-command provided on the homepage.
While installing I got 29 “vulnerabilities” which I solved with this “npm audit” and the recommended commands (somehow it threw these vulnerabilities stuff two times and as far as i understand the audit command only solved the vulnerabilities mentioned the second time).
But now when trying to start the MagicMirror it tells me, there is an ELIFECYCLE error, probably not a problem with npm (see command prompt output).
pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm start
> magicmirror@2.7.1 start /home/pi/MagicMirror
> sh run-start.sh
run-start.sh: 1: run-start.sh: ����������������������������������������������������������������������������������������������������������������������������������������������: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.7.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/2019-04-14T07_20_07_609Z-debug.log
As you might notice there is a log created, but somehow the files in this directory change every few seconds so I didn’t manage to attach it. If you could tell me how to get the log I’ll be happy to upload it in this thread!
I already tried running “DISPLAY:=0 npm start” and “npm start” all with the same result. Furthermore I also tried “npm rebuild” without success.
I am very thankful for every answer and appreciate your effort!
Kind regards,
MrKnight230