Error starting server
See original GitHub issueHey guys I’m setting up my server for the very first time and I’m having this issue that I don’t understand how to solve, maybe you can lend a hand, please? I tried the troubleshooting tips, but still no luck.
Are “grunt” and related grunt task modules installed locally? Run
npm install
if you’re not sure. Or maybe you don’t have permissions to access the.tmp
directory?
About malformed LESS, SASS, CoffeeScript file, etc. I haven’t edited or created any files yet. Any ideas? Thanks!
npm start
> electron-release-server@1.3.1 start /var/www/node
> node app.js
info:
info: .-..-.
info:
info: Sails <| .-..-.
info: v0.12.4 |\
info: /|.\
info: / || \
info: ,' |' \
info: .-'.-==|/_--'
info: `--'-------'
info: __---___--___---___--___---___--___
info: ____---___--___---___--___---___--___-__
info:
info: Server lifted in `/var/www/node`
info: To see your app, visit http://localhost:6000
info: To shut down Sails, press <CTRL> + C at any time.
debug: -------------------------------------------------------
debug: :: Wed Sep 07 2016 06:17:54 GMT+0000 (UTC)
debug: Environment : development
debug: Port : 6000
debug: -------------------------------------------------------
error: ** Grunt :: An error occurred. **
error:
------------------------------------------------------------------------
Aborted due to warnings.
Running "sass:dev" (sass) task
>> Error: File to import not found or unreadable: ../bower_components/bootstrap-sass-official/assets/stylesheets/_bootstrap.scss
>> Parent style sheet: /var/www/node/assets/styles/importer.scss
>> on line 4 of assets/styles/importer.scss
>> >> @import '../bower_components/bootstrap-sass-official/assets/stylesheets/_boots
>> ^
Warning:
------------------------------------------------------------------------
error: Looks like a Grunt error occurred--
error: Please fix it, then **restart Sails** to continue running tasks (e.g. watching for changes in assets)
error: Or if you're stuck, check out the troubleshooting tips below.
error: Troubleshooting tips:
error:
error: *-> Are "grunt" and related grunt task modules installed locally? Run `npm install` if you're not sure.
error:
error: *-> You might have a malformed LESS, SASS, CoffeeScript file, etc.
error:
error: *-> Or maybe you don't have permissions to access the `.tmp` directory?
error: e.g., `/var/www/node/.tmp` ?
error:
error: If you think this might be the case, try running:
error: sudo chown -R 500 /var/www/node/.tmp
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Could not start Appium server. It's showing [Error Starting ...
I have found the solution. After restarting my computer, i could successfully run the Appium server. If anyone face the same problem.
Read more >Unable to Start the Server Service - Microsoft Support
When you attempt to start the Server service from a command prompt, you may receive the following error message: System error 1058 has...
Read more >Could not start Appium server. It's showing ... - Appium Discuss
Check if the port is listening to any other services. Open command prompt: Type netstat -a -b · Either kill that service or...
Read more >Error starting server at operating system startup - IBM
In IBM® Security Directory Server, the server (the ibmslapd process) is started manually through the Services window or by the ibmslapd command.
Read more >Error Starting Server (Code: 1) in PrivateArk Server
If you had an automatic failover, it means that data was already updated on the DR vault. Depending on your configuration, your components ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Well, installing everything from scratch did the job. Thanks!
Not sure to be honest. I’d first advise doing a
git clean -fdx
and running npm install again.