Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when I run npm start on fresh raspbian stretch install #1103

Closed
abacon118 opened this Issue Dec 13, 2017 · 43 comments

Comments

Projects
None yet
@abacon118
Copy link

abacon118 commented Dec 13, 2017

When I run npm start on a fresh install on raspbian stretch install i get the following in the debug file.

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@3.10.10
3 info using node@v4.2.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.1.3prestart: magicmirror@2.1.3
6 silly lifecycle magicmirror@2.1.3
prestart: no script for prestart, continuing
7 info lifecycle magicmirror@2.1.3start: magicmirror@2.1.3
8 verbose lifecycle magicmirror@2.1.3
start: unsafe-perm in lifecycle true
9 verbose lifecycle magicmirror@2.1.3start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
10 verbose lifecycle magicmirror@2.1.3
start: CWD: /home/pi/MagicMirror
11 silly lifecycle magicmirror@2.1.3start: Args: [ '-c', 'sh run-start.sh' ]
12 silly lifecycle magicmirror@2.1.3
start: Returned: code: 1 signal: null
13 info lifecycle magicmirror@2.1.3~start: Failed to exec start script
14 verbose stack Error: magicmirror@2.1.3 start: sh run-start.sh
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:87:13)
14 verbose stack at EventEmitter.emit (events.js:172:7)
14 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:87:13)
14 verbose stack at ChildProcess.emit (events.js:172:7)
14 verbose stack at maybeClose (internal/child_process.js:818:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid magicmirror@2.1.3
16 verbose cwd /home/pi/MagicMirror
17 error Linux 4.9.59-v7+
18 error argv "/usr/local/bin/node" "/usr/bin/npm" "start"
19 error node v4.2.1
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error magicmirror@2.1.3 start: sh run-start.sh
22 error Exit status 1
23 error Failed at the magicmirror@2.1.3 start script 'sh run-start.sh'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the magicmirror package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error sh run-start.sh
23 error You can get information on how to open an issue for this project with:
23 error npm bugs magicmirror
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls magicmirror
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

@mfread

This comment has been minimized.

Copy link

mfread commented Dec 28, 2017

I did a manual install. I got a warning during installation onto my RPi2B with a new install of Raspbian Stretch.

npm WARN deprecated coffee-script@1.10.0: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN prefer global coffee-script@1.10.0 should be installed with -g
npm WARN prefer global jsonlint@1.0.2 should be installed with -g

The installation continued, and after some 5 mins, finished.

I'm a Linux & RPi newbie so I've no idea if I should now run 'npm install coffeescript' or not.

'npm start' worked and up popped the default mirror.

@pravine

This comment has been minimized.

Copy link

pravine commented Dec 29, 2017

Got same issue with a fresh installation for Rasbian Strech Lite. Any workaround on this issue ?

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Dec 30, 2017

Lite is not supported. Please state all the required version numbers to allow us to find an solution. Thanks!

See: https://github.com/MichMich/MagicMirror/blob/master/.github/ISSUE_TEMPLATE.md

@abacon118

This comment has been minimized.

Copy link
Author

abacon118 commented Dec 31, 2017

@mfread

This comment has been minimized.

Copy link

mfread commented Dec 31, 2017

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Dec 31, 2017

You can ignore the coffee script warning. So considering the mirror works. Can I close this issue?

@mfread

This comment has been minimized.

Copy link

mfread commented Dec 31, 2017

@abacon118

This comment has been minimized.

Copy link
Author

abacon118 commented Dec 31, 2017

@abacon118

This comment has been minimized.

Copy link
Author

abacon118 commented Jan 2, 2018

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Jan 2, 2018

Could you try reinstalling MagicMirror? We made some changes to the dependencies. Make sure you backup your config.js file (and modules).

@eugenelai

This comment has been minimized.

Copy link

eugenelai commented Jan 3, 2018

@MichMich,

I've just done a fresh install of MagicMirror and also encountered those errors above.

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@5.5.1
3 info using node@v9.3.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.2.2~prestart: magicmirror@2.2.2
6 info lifecycle magicmirror@2.2.2~start: magicmirror@2.2.2
7 verbose lifecycle magicmirror@2.2.2~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.2.2~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/b$
9 verbose lifecycle magicmirror@2.2.2~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.2.2~start: Args: [ '-c', 'sh run-start.sh' ]
11 silly lifecycle magicmirror@2.2.2~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.2.2~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.2.2 start: 'sh run-start.sh'
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
13 verbose stack at EventEmitter.emit (events.js:159:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:159:13)
13 verbose stack at maybeClose (internal/child_process.js:943:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid magicmirror@2.2.2
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 4.9.73-v7+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v9.3.0
19 verbose npm v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.2.2 start: 'sh run-start.sh'
22 error Exit status 1
23 error Failed at the magicmirror@2.2.2 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Info as follows:
Platform: Raspberry Pi 3

Node Version: v9.3.0

MagicMirror Version: v2.2.2

Description: Upon boot, I have errors in my log file as seen above.

Steps to Reproduce: Boot up RPi3

Expected Results: No errors

Actual Results: No actually degradation. Still works ok but thought you might like to know.

Configuration: Config file can be seen here https://hastebin.com/efinepepek.js

Additional Notes: Also getting a Fontconfig error:
0|mm | Fontconfig warning: ignoring UTF-8: not a valid region tag
0|mm | Fontconfig warning: ignoring UTF-8: not a valid region tag

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Jan 6, 2018

I just did all this yesterday on the latest full Raspbian Stretch on a Rpi3, and it works fine.
However, you must make sure you have first successfully installed and updated

  • Node.js (v9.3.0)
  • NPM (5.6.0)
  • PM2 (2.9.1)

Yes, the installation script may need some tweaking for the Stretch...but it shouldn't fail.
If the script fails try installing everything manually. Did you setup your Rpi3 according to docs here?

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Jan 6, 2018

An updated installer script PR is extremely welcome! And would be rewarded with a bunch of internet-hugs!

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Jan 6, 2018

@MichMich
Yeah, I've been working on one, but I don't have an ETA yet.

What has been most annoying in the installation process, was to make sure all the node stuff was already installed properly, before running anything else. And that is the more HW and OS (release) dependent aspect of it. There are simply too many contorted, wrong and outdated descriptions of how to do that out there.

@leveneg

This comment has been minimized.

Copy link

leveneg commented Jan 7, 2018

I too am getting about the same error log on full stretch.

Node.js (v9.3.0)
NPM (5.6.0)
PM2 (2.9.1)

4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.2.2~prestart: magicmirror@2.2.2
6 info lifecycle magicmirror@2.2.2~start: magicmirror@2.2.2
7 verbose lifecycle magicmirror@2.2.2~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.2.2~start: PATH: /home/pi/.nvm/versions/node/v9.3.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/home/pi/.nvm/versions/node/v9.3.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle magicmirror@2.2.2~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.2.2~start: Args: [ '-c', 'sh run-start.sh' ]
11 silly lifecycle magicmirror@2.2.2~start: Returned: code: 1  signal: null
12 info lifecycle magicmirror@2.2.2~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.2.2 start: `sh run-start.sh`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/home/pi/.nvm/versions/node/v9.3.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
13 verbose stack     at EventEmitter.emit (events.js:159:13)
13 verbose stack     at ChildProcess.<anonymous> (/home/pi/.nvm/versions/node/v9.3.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:159:13)
13 verbose stack     at maybeClose (internal/child_process.js:943:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid magicmirror@2.2.2
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 4.9.59-v7+
17 verbose argv "/home/pi/.nvm/versions/node/v9.3.0/bin/node" "/home/pi/.nvm/versions/node/v9.3.0/bin/npm" "start"
18 verbose node v9.3.0
19 verbose npm  v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.2.2 start: `sh run-start.sh`
22 error Exit status 1
23 error Failed at the magicmirror@2.2.2 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Jan 9, 2018

@leveneg Without seeing the exact command you did before getting this error log, its prety much useless. Also describe and post the exact commands you used for installing/updating.

@leveneg

This comment has been minimized.

Copy link

leveneg commented Jan 9, 2018

@E3V3A my apologies- I thought that had been included. I was running DISPLAY=:0 npm start, as specified in the install output.

Initial installation was done on a fresh stretch install via install script.

After that didn't work I reflashed stretch, installed latest node / npm, then installed once again via the installation script with the same result.

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Jan 19, 2018

Just FYI, I didn't use the full installation script. I basically went through it manually and skipping things that I had already changed or seemed irrelevant. That's why I can't be of much help here. Especially I recall skipping the part changing the bootup splash screen and themes. These are not ncessary, and seemed suspicious. Instead I just replaced the spalsh image manually later, once MM was working.

@Mabu2

This comment has been minimized.

Copy link

Mabu2 commented Jan 28, 2018

I think one reason why people seem to be having issues is, whether or not they're booting into X or the CLI.

I finally tracked down the problem I was having to trying to start MM without having X running first. This needs to be made clearer.

@nhubbard

This comment has been minimized.

Copy link
Contributor

nhubbard commented Jan 30, 2018

@MichMich For now, we should tag this issue cantfix because it does not come from a problem with our codebase, instead coming from Stretch and Electron compatibility.

@leveneg

This comment has been minimized.

Copy link

leveneg commented Jan 30, 2018

I got back around to this the other day, and a manual installation on a fresh stretch stretch install did do the job. I was also able to confirm that Mabu2's claim that MM needs to be started with X running first.

At a minimum, it would be nice if README were updated to reflect that the installer problematic on stretch, and that X does in fact need to be running before starting MM.

@Mabu2

This comment has been minimized.

Copy link

Mabu2 commented Jan 30, 2018

Perhaps the start up sequence should check to make sure X is running, and if not throw a specific error?

Another thing is when you're installing the OS, there is the option to boot to CLI or GUI. If someone installs the boot to CLI option, they may never know why it won't work. The error messages are ambiguous.

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Jan 31, 2018

I agree, we should add some info to the README and add a check to the nam run start method. If anyone would be willing to send a PR, I would be very grateful. :)

@MichMich MichMich added the pr welcome label Feb 1, 2018

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Feb 13, 2018

Hmm, yeah, IDK why people would try to install MM on a non-gui (no-X) machine, unless they start out from scratch trying to do serveronly install. Two other things:

  1. After you do git clone ..., the run-start.sh script is not executable:
-rw-r--r-- 1 pi pi 142 Jan  6 01:58 run-start.sh
  1. There is no shebang in the script and electron is not in the path, unless provided a new PATH before execution.
  2. DISPLAY of course is not well defined if not running in GUI mode.
# cat run-start.sh
if [ -z "$DISPLAY" ]; then #If not set DISPLAY is SSH remote or tty
        export DISPLAY=:0 # Set by default display
fi
electron js/electron.js $1

well, i guess that was 3.
Not sure how much this would influence, but surely worth looking into.

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Feb 13, 2018

Please send a PR.

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Feb 13, 2018

Hi @MichMich ,
I'm sure you address this to anyone, but this need to be tested by the people having the issues, before posting a PR. First, I'd suggest them to do this:

#!/bin/bash
if [ -z "$DISPLAY" ]; then #If not set DISPLAY is SSH remote or tty
        export DISPLAY=:0 # Set by default display
fi
electron js/electron.js $1

then do:

$ chmod 755 ~/MagicMirror/run-start.sh

now, try to re-run the installation.

@d-Rickyy-b

This comment has been minimized.

Copy link
Contributor

d-Rickyy-b commented Feb 16, 2018

I got the same issue on Debian Jessie and Stretch. I tried to install the MagicMirror application as a new user magicmirror into the directory /opt/MagicMirror/, which didn't work.

Even after installing it into the /home/magicmirror directory it's not possible to run the mirror.

Only after installing it into the /home/pi/ directory with user pi the installation succeeded and I am able to run the mirror. Can you please look into it? I used the installation script you provide in the readme file.

@saburishindaria

This comment has been minimized.

Copy link

saburishindaria commented Feb 19, 2018

We tried install npm using npm start command and although it launches the application, the new screen is just a blank black page.

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Feb 22, 2018

@d-Rickyy-b Yeah, MM should not be installed in root owned directories! Any directory above /home/pi/ is considered owned by root, AFAICR. There is absolutely no good reason, I can think of, to run MM as root.

But, this issue is important for people on other machines than RPi's, where default user has a different name and directories have different root permissions.

@d-Rickyy-b

This comment has been minimized.

Copy link
Contributor

d-Rickyy-b commented Feb 22, 2018

@E3V3A That's correct, especially on other machines, or even on the pi where the user goes with a different username (may it be for security reasons or whatsoever), it's not possible to use MM. I would highly appreciate a fix :)

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Feb 22, 2018

Just curious: did any of you try sudo npm start?

@d-Rickyy-b

This comment has been minimized.

Copy link
Contributor

d-Rickyy-b commented Feb 22, 2018

@MichMich Yes, and it produces the same outcome for me. If needed I can provide you with the log and command line output, but It's basically the same as in the initial bug report.

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Mar 5, 2018

To prevent some of the installation "problems". It might help to merge the README file from the developer branch to the very outdated current master README. I would guess that many new MM users don't even know about branches.

And for all of the rest of you, who end up here with problems:

  • please don't forget to tell us what exact commands you ran before you had errors.
  • please use the triple back-ticks (```) to enclose your copy/paste errors or code.
@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Mar 5, 2018

April 1st the next master will be released. So if you can just wait a little bit longer ... ;)

@d-Rickyy-b

This comment has been minimized.

Copy link
Contributor

d-Rickyy-b commented Mar 5, 2018

@E3V3A If you're interested in the steps I did before the issue happened:

$ sudo adduser magicmirror
$ sudo usermod -G sudo magicmirror
$ sudo su magicmirror
$ mkdir /opt/magicmirror; chown magicmirror: /opt/magicmirror; chmod 755 /opt/magicmirror
$ cd /opt/magicmirror
$ git clone https://github.com/MichMich/MagicMirror /opt/magicmirror
$ npm install && npm start

Even when I then tried sudo npm start it didn't work.
The error message and log message was basically the same as the issue creator posted in his report.

If you need further information, don't hesitate to ask.

PS: I am installing it on my RasPi 3, but would love to use another account (e.g. magicmirror) for it.

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Mar 5, 2018

I think we should just add to the readme that MagicMirror should be installed with the default user (Pi).

@d-Rickyy-b

This comment has been minimized.

Copy link
Contributor

d-Rickyy-b commented Mar 5, 2018

That would be a workaround ofc. May I ask what's the issue with installing it with another user? I mean it shouldn't be different than the default user, should it? Also do other systems need to create a user "pi" when they want to use MM?

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Mar 5, 2018

It works fine on my Mac on my regular user account. I don’t see any reason why it shouldn’t work on an other account on a Raspberry Pi as well.

That being said: I got a few reports like yours. And since it’s an edge case, it doesn’t really make sense to spent a lot of time investigating it (since it’s probably OS related, not mm related). My guess is it has something to do with the user rights of the node executables which electron uses.

@d-Rickyy-b

This comment has been minimized.

Copy link
Contributor

d-Rickyy-b commented Mar 5, 2018

I'll try to investigate further. Will report my findings back (if I find any).

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Mar 5, 2018

@d-Rickyy-b IDK why you seem to insist running this as root. Please explain, because earlier you mentioned security concerns with using a default username?? To me running as root seem far more insecure and in addition, the root environment is totally different from any other users, including missing environment variables.

@d-Rickyy-b

This comment has been minimized.

Copy link
Contributor

d-Rickyy-b commented Mar 5, 2018

@E3V3A I don't know where you see that I want to run it as root?! I want to run it as no login and no shell user (e.g. "magicmirror"). If you are asking because I added magicmirror to group sudo, that was for testing purposes.

I agree and know that it's totally insecure running it as root user. I just want another user than "pi". I don't want to use the user "pi" as a user at all - if possible. I don't want to use the root user and I never said so in any previous comment.

@E3V3A

This comment has been minimized.

Copy link
Contributor

E3V3A commented Mar 21, 2018

@d-Rickyy-b Try changing the /home/pi in the first two files from here.

@MichMich

This comment has been minimized.

Copy link
Owner

MichMich commented Mar 25, 2018

I don't think this is a real issue in the code. If you really want to make it work with an other user, feel free to fix it and send a PR so others can benefit. Fo now, my suggestion is to just use Pi. Never use Root (not saying you do).

Closing this for now, feel free to reopen or ask for some help on the forum.

@MichMich MichMich closed this Mar 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.