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

Problem with running npm start - listening to default 8081 port #705

Closed
erinjerri opened this issue Apr 6, 2015 · 6 comments
Closed

Problem with running npm start - listening to default 8081 port #705

erinjerri opened this issue Apr 6, 2015 · 6 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@erinjerri
Copy link

These threads helped me identify the problem:
#12

figuring out I needed to take steps in iOS app delegate:
#240

First I had to make sure I added the main.jsbundle to the project (the reference in the thread )

image

figuring out it was the 8081 port officiallyL
https://github.com/facebook/react-native/blob/master/packager/packager.js#L35

But I still kept getting the same problem and @mbrgm helped me through it.

After that I tried
sudo lsof -nP -iTCP:8081 -sTCP:LISTEN

So I wrote in $PID, typed in my admin password:

We located that on node this was the issue '3960'

kill 3960 and the sudo command above.
then I finally got the packager to run.

image

image

@frantic
Copy link
Contributor

frantic commented Apr 6, 2015

note that your kill $pid command didn't actually kill anything, you need to run pkill 3960. But before that, try ps aux | grep 3960 to see full path to the process that is taking that port.

@erinjerri
Copy link
Author

Yup, I did that this morning too. Still not working unfortunately.

@erinjerri
Copy link
Author

Finally got it to work, plus the curl thing I couldn't do. I had to recomment out things and do a fresh restart since I think OSX was locking up everything.

@frantic frantic closed this as completed Apr 6, 2015
@mbrgm
Copy link

mbrgm commented Apr 8, 2015

@frantic Should I send a PR adding a hint about the EADDRINUSE error to the troubleshooting section of the docs?

@frantic
Copy link
Contributor

frantic commented Apr 8, 2015

@mbrgm - as of #736 we provide better error message. Also the troubleshooting page already has instructions how to find out which process is taking the port and what to do. Or am I missing something?

@mbrgm
Copy link

mbrgm commented Apr 8, 2015

@frantic Sorry, I missed that. This project is progressing so fast, I should've looked there before ;)

@facebook facebook locked as resolved and limited conversation to collaborators May 29, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants