Closed spacemonkey closed 10 years ago
Hey Mitch, seems you have a process already started on port 9000.
could you try to check this?
$ netstat -tulpn | grep :9000
You should find the locking process, then you can decide to kill it, or change the port in use in /build/build.config.js
Let me know ;)
Yeah, it's called php-fpm. :-D
I think that's a pretty major collision there, as port 9000 is the default for socket-based installs including osx, debian, ubuntu, homebrew, macports, and probably many others. Might want to set the default to something else?
Yep, setting another default port may be the right solution. I' didn't think about collision.
Which port should be better? 9001?
Running "injector:dev" (injector) task
Missing option template
, using dest
as template instead
Injecting css files (2 files)
Nothing changed
Running "concurrent:tasks" (concurrent) task Running "connect:server" (connect) task Waiting forever... Fatal error: Port 4000 is already in use by another process.
Execution Time (2017-05-25 17:47:46 UTC+5:30)
loading tasks 587ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 96%
connect:server 24ms ▇▇ 4%
Total 612ms
Running "watch" task
Waiting...
Warning: Used --force, continuing.
Done, but with warnings.
Execution Time (2017-05-25 17:47:45 UTC+5:30) loading tasks 532ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 27% injector:dev 393ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 20% concurrent:tasks 1s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 53% Total 2s
how to solve this error in linux?
Ciao Alessandro! A clean install results in grunt serve failing with port 9000 already in use, and I'm assuming test or some such is hogging that port when the server tries to fire up.
Might have something to do with angular-generator? See https://github.com/yeoman/yeoman/issues/1118