[NPMCLI-184] mgnl start fails and gives errors Created: 28/May/18 Updated: 23/Jan/19 Resolved: 23/Jan/19 |
|
| Status: | Closed |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Frank Messie | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Open Suse Leap |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Running mgnl start fails with following result. ERR! spawn EACCES |
| Comments |
| Comment by Christopher Zimmermann [ 28/Aug/18 ] |
|
Hi os57741 can you please update to CLI version 3.0.3 and let us know if you still experience this problem? You can update with: npm update @magnolia/cli -g{{}} - It could be a problem with file permissions. If you are still having the problem then please provide more details as to how you installed the CLI (did you have to use sudo?), and the exact steps you took to install magnolia and start it. |
| Comment by Christopher Zimmermann [ 23/Jan/19 ] |
|
os57741 Closing since we have no further input from you or other reports of this issue. Feel free to reopen if you can reproduce it on version 3.0.3 of CLI. |