堆棧內存溢出
  簡體   English   中英

創建反應應用程序 - 某些東西已經在端口上運行

[英]create react app - something is already running on port

 原文  2019-04-30 10:02:56  7   1    node.js/ macos/ npm/ create-react-app/ macos-mojave

問題描述

我已經遇到這個問題一段時間了，我似乎無法找到根本原因。 我已經重新安裝了 node 和 npm（使用 nvm），但不幸的是，我仍然面臨同樣的問題。

當我在我的create-react-app庫上運行npm start ，我總是收到Something is already running on port <port>但它實際上似乎不是正在使用的端口。 在這種情況下，端口是5056 。

運行時sudo lsof -i -n -P | grep TCP 來自這個問題的sudo lsof -i -n -P | grep TCP ： 誰正在偵聽 Mac OS X 上的給定 TCP 端口？ 我得到以下信息：

CrashPlan    48                 root   71u  IPv6 0x2c25a5583eff58c1      0t0  TCP 127.0.0.1:4244 (LISTEN)
CrashPlan    48                 root   85u  IPv6 0x2c25a5583eff3c01      0t0  TCP 127.0.0.1:4244->127.0.0.1:61721 (FIN_WAIT_2)
CrashPlan    48                 root   86u  IPv6 0x2c25a5583eff41c1      0t0  TCP 127.0.0.1:4244->127.0.0.1:53768 (ESTABLISHED)
vpnagentd    55                 root    5u  IPv4 0x2c25a5583d8b2181      0t0  TCP 127.0.0.1:29754 (LISTEN)
ciscod       58                 root    3u  IPv4 0x2c25a5583d8b2b01      0t0  TCP 127.0.0.1:1023 (LISTEN)
apsd         91                 root   13u  IPv4 0x2c25a55862e8cb01      0t0  TCP 9.240.44.255:60294->17.249.12.152:5223 (ESTABLISHED)
apsd         91                 root   15u  IPv4 0x2c25a55862e8cb01      0t0  TCP 9.240.44.255:60294->17.249.12.152:5223 (ESTABLISHED)
rapportd    462 myusername    3u  IPv4 0x2c25a5586329f481      0t0  TCP *:60276 (LISTEN)
rapportd    462 myusername    4u  IPv6 0x2c25a55861ba8301      0t0  TCP *:60276 (LISTEN)
identitys   466 myusername   32u  IPv6 0x2c25a5583eff5301      0t0  TCP [fe80:c::992:b67a:e838:6f09]:1024->[fe80:c::d5c2:7935:1b0d:c90f]:1024 (ESTABLISHED)
identitys   466 myusername   33u  IPv6 0x2c25a5583eff5301      0t0  TCP [fe80:c::992:b67a:e838:6f09]:1024->[fe80:c::d5c2:7935:1b0d:c90f]:1024 (ESTABLISHED)
identitys   466 myusername   34u  IPv6 0x2c25a5583eff2ac1      0t0  TCP [fe80:c::992:b67a:e838:6f09]:1025->[fe80:c::d5c2:7935:1b0d:c90f]:9304 (ESTABLISHED)
identitys   466 myusername   35u  IPv6 0x2c25a5583eff2ac1      0t0  TCP [fe80:c::992:b67a:e838:6f09]:1025->[fe80:c::d5c2:7935:1b0d:c90f]:9304 (ESTABLISHED)
expressvp   805                 root   11u  IPv4 0x2c25a55847c2d481      0t0  TCP 127.0.0.1:2015 (LISTEN)
expressvp   805                 root   12u  IPv4 0x2c25a5586031d481      0t0  TCP 9.240.44.255:61661->3.212.116.79:443 (CLOSE_WAIT)
expressvp   805                 root   16u  IPv4 0x2c25a55868fb3b01      0t0  TCP 9.240.44.255:61662->3.212.116.79:443 (CLOSE_WAIT)
CrashPlan   814 myusername   51u  IPv4 0x2c25a5584b21c181      0t0  TCP 127.0.0.1:53768->127.0.0.1:4244 (ESTABLISHED)
CrashPlan   814 myusername   53u  IPv4 0x2c25a558807adb01      0t0  TCP 127.0.0.1:61721->127.0.0.1:4244 (CLOSE_WAIT)
Postman   22459 myusername   59u  IPv4 0x2c25a55862309801      0t0  TCP 9.240.44.255:60336->34.224.76.239:443 (CLOSED)
Postman   22459 myusername   73u  IPv4 0x2c25a5586031c181      0t0  TCP 9.240.44.255:60337->34.224.76.239:443 (ESTABLISHED)
Discord   36658 myusername   59u  IPv4 0x2c25a5583d8b0e81      0t0  TCP 9.240.44.255:60423->104.16.60.37:443 (ESTABLISHED)
Discord   36658 myusername   67u  IPv4 0x2c25a558807ae481      0t0  TCP 9.240.44.255:61654->104.16.59.5:443 (ESTABLISHED)
Discord   36658 myusername   97u  IPv4 0x2c25a55857e86181      0t0  TCP 9.240.44.255:60359->35.186.224.47:443 (ESTABLISHED)
Discord   36664 myusername   49u  IPv4 0x2c25a5586ce46b01      0t0  TCP 127.0.0.1:6463 (LISTEN)
Slack     51840 myusername   73u  IPv4 0x2c25a5586329ce81      0t0  TCP 9.240.44.255:60383->52.37.243.173:443 (ESTABLISHED)
Slack     51840 myusername  112u  IPv4 0x2c25a5586329d801      0t0  TCP 9.240.44.255:60333->52.37.243.173:443 (ESTABLISHED)
Slack     51840 myusername  117u  IPv4 0x2c25a55847c2ae81      0t0  TCP 9.240.44.255:60339->52.37.243.173:443 (ESTABLISHED)
Slack     51840 myusername  118u  IPv4 0x2c25a5586914a181      0t0  TCP 9.240.44.255:60338->52.37.243.173:443 (ESTABLISHED)
Slack     51840 myusername  119u  IPv4 0x2c25a55854de1481      0t0  TCP 9.240.44.255:60342->52.37.243.173:443 (ESTABLISHED)
firefox   76426 myusername   95u  IPv4 0x2c25a55858abae81      0t0  TCP 9.240.44.255:60326->34.209.103.65:443 (ESTABLISHED)
firefox   76426 myusername  120u  IPv4 0x2c25a55857e87481      0t0  TCP 9.240.44.255:60361->159.203.171.189:443 (ESTABLISHED)
Google    76844 myusername   30u  IPv4 0x2c25a558807f0481      0t0  TCP 9.240.44.255:61632->104.16.28.34:443 (ESTABLISHED)
Google    76844 myusername   35u  IPv4 0x2c25a558807c7481      0t0  TCP 9.240.44.255:60837->159.203.171.189:443 (ESTABLISHED)
Google    76844 myusername   36u  IPv4 0x2c25a5588079a181      0t0  TCP 9.240.44.255:61218->192.30.253.125:443 (ESTABLISHED)
Google    76844 myusername   38u  IPv4 0x2c25a5587a432481      0t0  TCP 9.240.44.255:61724->52.207.60.84:443 (ESTABLISHED)
Google    76844 myusername   41u  IPv4 0x2c25a55880798e81      0t0  TCP 9.240.44.255:61728->192.184.69.195:443 (ESTABLISHED)
Google    76844 myusername   44u  IPv4 0x2c25a5586167c801      0t0  TCP 9.240.44.255:61651->162.247.242.21:443 (ESTABLISHED)
Google    76844 myusername   46u  IPv4 0x2c25a5583d8b1801      0t0  TCP 9.240.44.255:60305->165.160.13.20:80 (CLOSED)
Google    76844 myusername   50u  IPv4 0x2c25a55863665481      0t0  TCP 9.240.44.255:61726->52.207.32.1:443 (ESTABLISHED)
Google    76844 myusername   60u  IPv4 0x2c25a55868fb4481      0t0  TCP 9.240.44.255:60306->165.160.13.20:80 (CLOSED)
Google    76844 myusername   63u  IPv4 0x2c25a55863662e81      0t0  TCP 9.240.44.255:60308->165.160.15.20:80 (ESTABLISHED)
Google    76844 myusername   64u  IPv4 0x2c25a5586031ae81      0t0  TCP 9.240.44.255:60309->165.160.13.20:80 (ESTABLISHED)
Google    76844 myusername   66u  IPv4 0x2c25a5586329eb01      0t0  TCP 9.240.44.255:60310->165.160.13.20:80 (ESTABLISHED)
Google    76844 myusername   69u  IPv4 0x2c25a5586f554481      0t0  TCP 9.240.44.255:61646->23.222.172.234:443 (ESTABLISHED)
Google    76844 myusername   74u  IPv4 0x2c25a5588085e481      0t0  TCP 9.240.44.255:61647->23.222.172.234:443 (ESTABLISHED)
Google    76844 myusername   77u  IPv4 0x2c25a5588085be81      0t0  TCP 9.240.44.255:61706->198.252.206.25:443 (ESTABLISHED)
Google    76844 myusername   79u  IPv4 0x2c25a558807c6b01      0t0  TCP 9.240.44.255:61729->198.252.206.25:443 (ESTABLISHED)
Google    76844 myusername   81u  IPv4 0x2c25a558807c6181      0t0  TCP 9.240.44.255:61629->151.101.1.69:443 (ESTABLISHED)
Google    76844 myusername   85u  IPv4 0x2c25a55880792b01      0t0  TCP 9.240.44.255:61712->198.252.206.25:443 (ESTABLISHED)
Google    76844 myusername   86u  IPv4 0x2c25a558807d9481      0t0  TCP 9.240.44.255:61727->52.207.32.1:443 (ESTABLISHED)
Google    76844 myusername   93u  IPv4 0x2c25a558807b1e81      0t0  TCP 9.240.44.255:61630->192.0.73.2:443 (ESTABLISHED)
Google    76844 myusername  100u  IPv4 0x2c25a55863664181      0t0  TCP 9.240.44.255:61634->184.30.231.203:443 (ESTABLISHED)
Google    76844 myusername  114u  IPv4 0x2c25a55880791801      0t0  TCP 9.240.44.255:61522->151.101.41.140:443 (ESTABLISHED)
Google    76844 myusername  123u  IPv4 0x2c25a55853feab01      0t0  TCP 9.240.44.255:61544->104.244.42.200:443 (ESTABLISHED)
Google    76844 myusername  146u  IPv4 0x2c25a5586172e181      0t0  TCP 9.240.44.255:61584->151.101.40.84:443 (ESTABLISHED)
Spotify   92621 myusername   69u  IPv4 0x2c25a5588085db01      0t0  TCP *:61682 (LISTEN)
Spotify   92621 myusername   71u  IPv4 0x2c25a55847c2b801      0t0  TCP *:57621 (LISTEN)
Spotify   92621 myusername   79u  IPv4 0x2c25a5584b21b801      0t0  TCP 9.240.44.255:60556->104.199.65.177:4070 (ESTABLISHED)
Spotify   92621 myusername  112u  IPv4 0x2c25a5586167d181      0t0  TCP 9.240.44.255:60562->35.186.224.53:443 (ESTABLISHED)
Spotify   92621 myusername  139u  IPv4 0x2c25a55858abb801      0t0  TCP 9.240.44.255:60566->151.101.40.246:443 (CLOSED)
Spotify   92621 myusername  140u  IPv4 0x2c25a55858abcb01      0t0  TCP 9.240.44.255:60567->151.101.40.246:443 (CLOSED)
Spotify   92621 myusername  141u  IPv4 0x2c25a55858abd481      0t0  TCP 9.240.44.255:60568->151.101.40.246:443 (CLOSED)

我似乎無法找到該端口的任何用途，並且我一直在尋找導致此問題的原因。 如果我通過修改scripts/start.js文件將端口強制為5056 ，它確實會按預期加載，但是會出現代理請求問題，因此我的狀態數據都不會從模擬 API 加載。 如果我選擇在另一個端口上運行應用程序，情況也是如此。

我收到一個ETIMEDOUT錯誤，說它無法代理請求。

如果有人對問題的原因有任何想法，那么我將非常感激。 值得一提的是，其他人能夠按預期運行相同的存儲庫，而不會出現任何上述問題。

編輯：

運行lsof -i:5056不會返回任何內容。

運行lsof -n -i4TCP:3000 | grep LISTEN lsof -n -i4TCP:3000 | grep LISTEN也不返回任何內容。

運行最新的 XCode 更新似乎已經解決了這個問題......

1 個解決方案

解決方案1
 -1  2019-12-10 20:16:37

這可能會有所幫助： http : //johnharbison.net/something-is-already-running-on-port-3000-mac檢查您的本地主機是否在 /etc/hosts 中配置正確。

暫無
暫無

聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

相關問題 有些東西已經在端口上運行了 NODE - 其他東西已經在端口上運行 Heroku 部署：某些內容已經在端口 **** 上運行 啟動我的本機腳本，它顯示一個錯誤：端口3000上已在運行某些內容 運行 nodejs 應用程序時端口已在使用中 無法將調試器附加到端口 3000 上已運行的 nodejs Web 應用程序 App.listen 在已運行的共享主機端口上 無論 XXX 是什么， npm start 都會報告“端口 XXX 上已經有東西在運行” 運行 npm/npm 以創建反應應用程序的問題 運行 React 應用程序的 docker 容器在哪個端口？ Reacts 的默認端口或來自 Dockerfile 的 EXPOSE？
相關標簽
 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM