Mac 电脑 IDEA 执行 Maven 出现 No route to host 问题

最新推荐文章于 2025-10-13 05:41:41 发布
原创 最新推荐文章于 2025-10-13 05:41:41 发布 · 347 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#macos #intellij-idea #maven

全网找不到资料，服了，给大家避坑吧～

  1. Mac 电脑打开本地网络：System Settings ->Privacy & Security -> Local Network -> IDEA ✅
  2. IDEA 关闭系统代理：Appearance & Behavior › System Settings > HTTP Proxy -> No proxy 🚫

在这里插入图片描述
在这里插入图片描述

chugyoyo
关注
docker-jenkins 构建项目执行mvn命令时出现 No route to host (Host unreachable)
qq_38127559的博客
09-21 680
spring-cloud微服务项目，采用gogs代码仓库，采用jenkins持续集成工具的自动构建配置。在配置完成后，执行构建任务时，出现：`Failed to deploy artifacts`，`Could not transfer artifact`，`No route to host (Host unreachable)`错误。
部署Maven工程的项目到Linux上（详细解读）
Monster丶ZF的博客
03-10 5659
文章目录1. 修改pom配置1.1修改JDK版本号1.2添加finalName标签2.将本机的sql导入到Linux上3.修改项目3.1修改druid.properties3.2修改绝对路径4.打war包5.将打好的war包上传到tomcat中的webapps目录6.启动Linux上的Tomcat ????大家好！我是近视的脚踏实地，这篇文章主要是介绍如何将写好的项目部署到Linux上  ...
MacOS局域网ping失败？5步解决No route错误
最新发布
KjR_rwnf的博客
10-13 433
该错误通常表示系统无法找到通往目标主机的有效路由路径，可能与网络配置、防火墙设置或ARP缓存问题有关。确认目标主机是否在线并允许ICMP请求。在另一台设备上尝试ping目标主机，或检查目标主机的防火墙设置。检查MacOS的IP地址、子网掩码和网关是否与局域网其他设备在同一子网。在MacOS系统中使用Warp终端工具ping局域网设备时，可能会遇到。ARP缓存可能导致路由表未及时更新。清除缓存并重新尝试ping操作。
MacOS 下 Warp ping 局域网设备报错 ping: sendto: No route to host 的解决方法
星空千代
10-05 524
升级到MacOS Sonoma 14+后，ping局域网主机报错 No route to host。经查，这是新系统默认禁止第三方应用访问本地网络的权限所致。
MacOS解决局域网“没有到达主机的路由 no route to host“
buyue
06-05 1385
可能原因：MacOS 15新增了"本地网络"访问权限，在 APP 第一次尝试访问本地网络的时候会请求权限，可能顺手选择了关闭。解决办法：给想要访问本地网络的 APP （例如 terminal、Ftp）添加访问权限。具体路径：设置 -> 隐私与安全性 -> 本地网络 -> 勾选要使用的 APP。
macOS 15使用VScode使用SSH连接远程服务器显示No route to host
qq_66026225的博客
10-29 1212
闲来无事把mac os更新了到了最新版sequoia，结果发现ssh连不上校园网环境下的服务器，vscode会报错“No route to host”，但是直接使用命令行ssh host@ip的方式是可以连接成功的，排除了远程服务器没问题，排查了DNS、大概率就是系统的导致vscode出现了问题。最快的想法是，卸载vscode，然后重新装一个呗，但是发现fail，重新安装后，插件和各种配置文件仍然没问题，查了一下百度，没什么结果，遂google了一下，结果第一条就是答案。
踩坑记录:ssh: connect to host gitlab.com port 22: No route to host（MAC环境下 ）
Yaoman753的博客
07-19 3008
在打算从远程仓库使用 git pull origin 更新代码到本地时，发送了如下错误。 ssh: connect to host gitlab.com port 22: No route to host fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. 解决办法： 终端输入 git config --l
MacOS 15 Sequoia 解决局域网“没有到达主机的路由 no route to host”
m0_38020248的博客
09-17 3935
解决办法：给想要访问本地网络的 APP （例如 terminal、vscode）添加访问权限。具体路径：设置 -> 隐私与安全性 -> 本地网络 -> 勾选要使用的 APP。可能原因：MacOS 15 新增“本地网络”访问权限，类似 IOS。在 APP 第一次尝试访问本地网络的时候会请求权限，可能被顺手点击关闭。
ssh连接MAC服务器显示No route to host解决方法
aff60756的博客
08-20 3758
首先MAC操作系统是10 　　其它电脑通过ssh访问一台mac服务器时，有时候可以登录进去，有显示显示no route to host 　　并且通过浏览器访问布署在mac上的jenkins，反应奇慢，后来做了如下修改，就可以正常使用了。 　　1.系统偏好设置>>共享>>勾选 文件共享，选程登录，远程管理 　　还有可能是因为电脑进入...
maven 报错No route to host: connect
02-14
### Maven No Route to Host 错误解决方案 #### 一、理解错误根源 Java应用程序尝试建立网络连接时遇到`java.net.NoRouteToHostException: No route to host (Host unreachable)`表明客户端与目标服务器之间不存在...
D:\Java\jdk\jdk8\bin\java.exe -XX:TieredStopAtLevel=1 -noverify -Dspring.output.ansi.enabled=always -Dcom.sun.management.jmxremote -Dspring.jmx.enabled=true -Dspring.liveBeansView.mbeanDomain -Dspring.application.admin.enabled=true "-Dmanagement.endpoints.jmx.exposure.include=*" "-javaagent:D:\Java\IDEA\idea_step\IntelliJ IDEA 2024.1.4\lib\idea_rt.jar=52637:D:\Java\IDEA\idea_step\IntelliJ IDEA 2024.1.4\bin" -Dfile.encoding=UTF-8 -classpath D:\Java\jdk\jdk8\jre\lib\charsets.jar;D:\Java\jdk\jdk8\jre\lib\deploy.jar;D:\Java\jdk\jdk8\jre\lib\ext\access-bridge-64.jar;D:\Java\jdk\jdk8\jre\lib\ext\cldrdata.jar;D:\Java\jdk\jdk8\jre\lib\ext\dnsns.jar;D:\Java\jdk\jdk8\jre\lib\ext\jaccess.jar;D:\Java\jdk\jdk8\jre\lib\ext\jfxrt.jar;D:\Java\jdk\jdk8\jre\lib\ext\localedata.jar;D:\Java\jdk\jdk8\jre\lib\ext\nashorn.jar;D:\Java\jdk\jdk8\jre\lib\ext\sunec.jar;D:\Java\jdk\jdk8\jre\lib\ext\sunjce_provider.jar;D:\Java\jdk\jdk8\jre\lib\ext\sunmscapi.jar;D:\Java\jdk\jdk8\jre\lib\ext\sunpkcs11.jar;D:\Java\jdk\jdk8\jre\lib\ext\zipfs.jar;D:\Java\jdk\jdk8\jre\lib\javaws.jar;D:\Java\jdk\jdk8\jre\lib\jce.jar;D:\Java\jdk\jdk8\jre\lib\jfr.jar;D:\Java\jdk\jdk8\jre\lib\jfxswt.jar;D:\Java\jdk\jdk8\jre\lib\jsse.jar;D:\Java\jdk\jdk8\jre\lib\management-agent.jar;D:\Java\jdk\jdk8\jre\lib\plugin.jar;D:\Java\jdk\jdk8\jre\lib\resources.jar;D:\Java\jdk\jdk8\jre\lib\rt.jar;D:\Java\IDEA\space\SpringCloudProjectBuild\spring-cloud-alibaba-leaning\gateway\target\classes;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-starter-gateway\2.2.6.RELEASE\spring-cloud-starter-gateway-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-starter\2.2.6.RELEASE\spring-cloud-starter-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot-starter\2.3.2.RELEASE\spring-boot-starter-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot\2.3.2.RELEASE\spring-boot-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\spring-context\5.2.8.RELEASE\spring-context-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\spring-aop\5.2.8.RELEASE\spring-aop-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\spring-expression\5.2.8.RELEASE\spring-expression-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot-autoconfigure\2.3.2.RELEASE\spring-boot-autoconfigure-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot-starter-logging\2.3.2.RELEASE\spring-boot-starter-logging-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\ch\qos\logback\logback-classic\1.2.3\logback-classic-1.2.3.jar;D:\Java\Maven\newrepository\ch\qos\logback\logback-core\1.2.3\logback-core-1.2.3.jar;D:\Java\Maven\newrepository\org\apache\logging\log4j\log4j-to-slf4j\2.13.3\log4j-to-slf4j-2.13.3.jar;D:\Java\Maven\newrepository\org\apache\logging\log4j\log4j-api\2.13.3\log4j-api-2.13.3.jar;D:\Java\Maven\newrepository\org\slf4j\jul-to-slf4j\1.7.30\jul-to-slf4j-1.7.30.jar;D:\Java\Maven\newrepository\jakarta\annotation\jakarta.annotation-api\1.3.5\jakarta.annotation-api-1.3.5.jar;D:\Java\Maven\newrepository\org\springframework\spring-core\5.2.8.RELEASE\spring-core-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\spring-jcl\5.2.8.RELEASE\spring-jcl-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\security\spring-security-rsa\1.0.9.RELEASE\spring-security-rsa-1.0.9.RELEASE.jar;D:\Java\Maven\newrepository\org\bouncycastle\bcpkix-jdk15on\1.64\bcpkix-jdk15on-1.64.jar;D:\Java\Maven\newrepository\org\bouncycastle\bcprov-jdk15on\1.64\bcprov-jdk15on-1.64.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-gateway-server\2.2.6.RELEASE\spring-cloud-gateway-server-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot-starter-validation\2.3.2.RELEASE\spring-boot-starter-validation-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\org\glassfish\jakarta.el\3.0.3\jakarta.el-3.0.3.jar;D:\Java\Maven\newrepository\org\hibernate\validator\hibernate-validator\6.1.5.Final\hibernate-validator-6.1.5.Final.jar;D:\Java\Maven\newrepository\jakarta\validation\jakarta.validation-api\2.0.2\jakarta.validation-api-2.0.2.jar;D:\Java\Maven\newrepository\org\jboss\logging\jboss-logging\3.4.1.Final\jboss-logging-3.4.1.Final.jar;D:\Java\Maven\newrepository\com\fasterxml\classmate\1.5.1\classmate-1.5.1.jar;D:\Java\Maven\newrepository\io\projectreactor\addons\reactor-extra\3.3.3.RELEASE\reactor-extra-3.3.3.RELEASE.jar;D:\Java\Maven\newrepository\io\projectreactor\reactor-core\3.3.8.RELEASE\reactor-core-3.3.8.RELEASE.jar;D:\Java\Maven\newrepository\org\reactivestreams\reactive-streams\1.0.3\reactive-streams-1.0.3.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot-starter-webflux\2.3.2.RELEASE\spring-boot-starter-webflux-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot-starter-json\2.3.2.RELEASE\spring-boot-starter-json-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\com\fasterxml\jackson\datatype\jackson-datatype-jdk8\2.11.1\jackson-datatype-jdk8-2.11.1.jar;D:\Java\Maven\newrepository\com\fasterxml\jackson\datatype\jackson-datatype-jsr310\2.11.1\jackson-datatype-jsr310-2.11.1.jar;D:\Java\Maven\newrepository\com\fasterxml\jackson\module\jackson-module-parameter-names\2.11.1\jackson-module-parameter-names-2.11.1.jar;D:\Java\Maven\newrepository\org\springframework\boot\spring-boot-starter-reactor-netty\2.3.2.RELEASE\spring-boot-starter-reactor-netty-2.3.2.RELEASE.jar;D:\Java\Maven\newrepository\io\projectreactor\netty\reactor-netty\0.9.10.RELEASE\reactor-netty-0.9.10.RELEASE.jar;D:\Java\Maven\newrepository\io\netty\netty-codec-http\4.1.51.Final\netty-codec-http-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-codec-http2\4.1.51.Final\netty-codec-http2-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-handler-proxy\4.1.51.Final\netty-handler-proxy-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-codec-socks\4.1.51.Final\netty-codec-socks-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-transport-native-epoll\4.1.51.Final\netty-transport-native-epoll-4.1.51.Final-linux-x86_64.jar;D:\Java\Maven\newrepository\io\netty\netty-transport-native-unix-common\4.1.51.Final\netty-transport-native-unix-common-4.1.51.Final.jar;D:\Java\Maven\newrepository\org\springframework\spring-web\5.2.8.RELEASE\spring-web-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\spring-beans\5.2.8.RELEASE\spring-beans-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\spring-webflux\5.2.8.RELEASE\spring-webflux-5.2.8.RELEASE.jar;D:\Java\Maven\newrepository\org\synchronoss\cloud\nio-multipart-parser\1.1.0\nio-multipart-parser-1.1.0.jar;D:\Java\Maven\newrepository\org\slf4j\slf4j-api\1.7.30\slf4j-api-1.7.30.jar;D:\Java\Maven\newrepository\org\synchronoss\cloud\nio-stream-storage\1.1.3\nio-stream-storage-1.1.3.jar;D:\Java\Maven\newrepository\com\alibaba\cloud\spring-cloud-starter-alibaba-nacos-discovery\2.2.6.RELEASE\spring-cloud-starter-alibaba-nacos-discovery-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\com\alibaba\cloud\spring-cloud-alibaba-commons\2.2.6.RELEASE\spring-cloud-alibaba-commons-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\com\alibaba\nacos\nacos-client\1.4.2\nacos-client-1.4.2.jar;D:\Java\Maven\newrepository\com\alibaba\nacos\nacos-common\1.4.2\nacos-common-1.4.2.jar;D:\Java\Maven\newrepository\commons-io\commons-io\2.7\commons-io-2.7.jar;D:\Java\Maven\newrepository\org\apache\httpcomponents\httpasyncclient\4.1.4\httpasyncclient-4.1.4.jar;D:\Java\Maven\newrepository\org\apache\httpcomponents\httpcore\4.4.13\httpcore-4.4.13.jar;D:\Java\Maven\newrepository\org\apache\httpcomponents\httpcore-nio\4.4.13\httpcore-nio-4.4.13.jar;D:\Java\Maven\newrepository\com\alibaba\nacos\nacos-api\1.4.2\nacos-api-1.4.2.jar;D:\Java\Maven\newrepository\com\google\guava\guava\29.0-jre\guava-29.0-jre.jar;D:\Java\Maven\newrepository\com\google\guava\failureaccess\1.0.1\failureaccess-1.0.1.jar;D:\Java\Maven\newrepository\com\google\guava\listenablefuture\9999.0-empty-to-avoid-conflict-with-guava\listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar;D:\Java\Maven\newrepository\com\google\code\findbugs\jsr305\3.0.2\jsr305-3.0.2.jar;D:\Java\Maven\newrepository\org\checkerframework\checker-qual\2.11.1\checker-qual-2.11.1.jar;D:\Java\Maven\newrepository\com\google\errorprone\error_prone_annotations\2.3.4\error_prone_annotations-2.3.4.jar;D:\Java\Maven\newrepository\com\google\j2objc\j2objc-annotations\1.3\j2objc-annotations-1.3.jar;D:\Java\Maven\newrepository\commons-codec\commons-codec\1.14\commons-codec-1.14.jar;D:\Java\Maven\newrepository\com\fasterxml\jackson\core\jackson-core\2.11.1\jackson-core-2.11.1.jar;D:\Java\Maven\newrepository\com\fasterxml\jackson\core\jackson-databind\2.11.1\jackson-databind-2.11.1.jar;D:\Java\Maven\newrepository\io\prometheus\simpleclient\0.5.0\simpleclient-0.5.0.jar;D:\Java\Maven\newrepository\org\yaml\snakeyaml\1.26\snakeyaml-1.26.jar;D:\Java\Maven\newrepository\com\alibaba\spring\spring-context-support\1.0.10\spring-context-support-1.0.10.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-commons\2.2.6.RELEASE\spring-cloud-commons-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\security\spring-security-crypto\5.3.3.RELEASE\spring-security-crypto-5.3.3.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-context\2.2.6.RELEASE\spring-cloud-context-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-starter-netflix-ribbon\2.2.6.RELEASE\spring-cloud-starter-netflix-ribbon-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-netflix-ribbon\2.2.6.RELEASE\spring-cloud-netflix-ribbon-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-netflix-archaius\2.2.6.RELEASE\spring-cloud-netflix-archaius-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\org\springframework\cloud\spring-cloud-starter-netflix-archaius\2.2.6.RELEASE\spring-cloud-starter-netflix-archaius-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\com\netflix\archaius\archaius-core\0.7.6\archaius-core-0.7.6.jar;D:\Java\Maven\newrepository\commons-configuration\commons-configuration\1.8\commons-configuration-1.8.jar;D:\Java\Maven\newrepository\com\netflix\ribbon\ribbon\2.3.0\ribbon-2.3.0.jar;D:\Java\Maven\newrepository\com\netflix\ribbon\ribbon-transport\2.3.0\ribbon-transport-2.3.0.jar;D:\Java\Maven\newrepository\io\reactivex\rxnetty-contexts\0.4.9\rxnetty-contexts-0.4.9.jar;D:\Java\Maven\newrepository\io\reactivex\rxnetty-servo\0.4.9\rxnetty-servo-0.4.9.jar;D:\Java\Maven\newrepository\com\netflix\hystrix\hystrix-core\1.5.18\hystrix-core-1.5.18.jar;D:\Java\Maven\newrepository\org\hdrhistogram\HdrHistogram\2.1.9\HdrHistogram-2.1.9.jar;D:\Java\Maven\newrepository\javax\inject\javax.inject\1\javax.inject-1.jar;D:\Java\Maven\newrepository\io\reactivex\rxnetty\0.4.9\rxnetty-0.4.9.jar;D:\Java\Maven\newrepository\com\netflix\ribbon\ribbon-core\2.3.0\ribbon-core-2.3.0.jar;D:\Java\Maven\newrepository\commons-lang\commons-lang\2.6\commons-lang-2.6.jar;D:\Java\Maven\newrepository\com\netflix\ribbon\ribbon-httpclient\2.3.0\ribbon-httpclient-2.3.0.jar;D:\Java\Maven\newrepository\commons-collections\commons-collections\3.2.2\commons-collections-3.2.2.jar;D:\Java\Maven\newrepository\org\apache\httpcomponents\httpclient\4.5.12\httpclient-4.5.12.jar;D:\Java\Maven\newrepository\com\sun\jersey\jersey-client\1.19.1\jersey-client-1.19.1.jar;D:\Java\Maven\newrepository\com\sun\jersey\jersey-core\1.19.1\jersey-core-1.19.1.jar;D:\Java\Maven\newrepository\javax\ws\rs\jsr311-api\1.1.1\jsr311-api-1.1.1.jar;D:\Java\Maven\newrepository\com\sun\jersey\contribs\jersey-apache-client4\1.19.1\jersey-apache-client4-1.19.1.jar;D:\Java\Maven\newrepository\com\netflix\servo\servo-core\0.12.21\servo-core-0.12.21.jar;D:\Java\Maven\newrepository\com\netflix\netflix-commons\netflix-commons-util\0.3.0\netflix-commons-util-0.3.0.jar;D:\Java\Maven\newrepository\com\netflix\ribbon\ribbon-loadbalancer\2.3.0\ribbon-loadbalancer-2.3.0.jar;D:\Java\Maven\newrepository\com\netflix\netflix-commons\netflix-statistics\0.1.1\netflix-statistics-0.1.1.jar;D:\Java\Maven\newrepository\io\reactivex\rxjava\1.3.8\rxjava-1.3.8.jar;D:\Java\Maven\newrepository\com\alibaba\cloud\spring-cloud-alibaba-sentinel-gateway\2.2.6.RELEASE\spring-cloud-alibaba-sentinel-gateway-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-api-gateway-adapter-common\1.8.1\sentinel-api-gateway-adapter-common-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-core\1.8.1\sentinel-core-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-parameter-flow-control\1.8.1\sentinel-parameter-flow-control-1.8.1.jar;D:\Java\Maven\newrepository\com\googlecode\concurrentlinkedhashmap\concurrentlinkedhashmap-lru\1.4.2\concurrentlinkedhashmap-lru-1.4.2.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-zuul-adapter\1.8.1\sentinel-zuul-adapter-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-spring-cloud-gateway-adapter\1.8.1\sentinel-spring-cloud-gateway-adapter-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-reactor-adapter\1.8.1\sentinel-reactor-adapter-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\cloud\spring-cloud-alibaba-sentinel-datasource\2.2.6.RELEASE\spring-cloud-alibaba-sentinel-datasource-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\com\alibaba\cloud\spring-cloud-starter-alibaba-sentinel\2.2.6.RELEASE\spring-cloud-starter-alibaba-sentinel-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-transport-simple-http\1.8.1\sentinel-transport-simple-http-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-transport-common\1.8.1\sentinel-transport-common-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-datasource-extension\1.8.1\sentinel-datasource-extension-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\fastjson\1.2.75\fastjson-1.2.75.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-annotation-aspectj\1.8.1\sentinel-annotation-aspectj-1.8.1.jar;D:\Java\Maven\newrepository\org\aspectj\aspectjrt\1.9.6\aspectjrt-1.9.6.jar;D:\Java\Maven\newrepository\org\aspectj\aspectjweaver\1.9.6\aspectjweaver-1.9.6.jar;D:\Java\Maven\newrepository\com\alibaba\cloud\spring-cloud-circuitbreaker-sentinel\2.2.6.RELEASE\spring-cloud-circuitbreaker-sentinel-2.2.6.RELEASE.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-spring-webflux-adapter\1.8.1\sentinel-spring-webflux-adapter-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-spring-webmvc-adapter\1.8.1\sentinel-spring-webmvc-adapter-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-cluster-server-default\1.8.1\sentinel-cluster-server-default-1.8.1.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-cluster-common-default\1.8.1\sentinel-cluster-common-default-1.8.1.jar;D:\Java\Maven\newrepository\io\netty\netty-handler\4.1.51.Final\netty-handler-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-common\4.1.51.Final\netty-common-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-resolver\4.1.51.Final\netty-resolver-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-buffer\4.1.51.Final\netty-buffer-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-transport\4.1.51.Final\netty-transport-4.1.51.Final.jar;D:\Java\Maven\newrepository\io\netty\netty-codec\4.1.51.Final\netty-codec-4.1.51.Final.jar;D:\Java\Maven\newrepository\com\alibaba\csp\sentinel-cluster-client-default\1.8.1\sentinel-cluster-client-default-1.8.1.jar;D:\Java\Maven\newrepository\org\projectlombok\lombok\1.18.12\lombok-1.18.12.jar;D:\Java\Maven\newrepository\com\fasterxml\jackson\core\jackson-annotations\2.11.1\jackson-annotations-2.11.1.jar com.example.GatewayApplication . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.3.2.RELEASE) 2025-06-13 20:01:13.131 INFO 19824 --- [ main] com.example.GatewayApplication : No active profile set, falling back to default profiles: default 2025-06-13 20:01:13.545 INFO 19824 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=60fdbe5f-1650-3cc5-946f-7b7773a6e1fd 2025-06-13 20:01:13.710 INFO 19824 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.cloud.sentinel-com.alibaba.cloud.sentinel.SentinelProperties' of type [com.alibaba.cloud.sentinel.SentinelProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-06-13 20:01:13.746 INFO 19824 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.sentinel.custom.SentinelAutoConfiguration' of type [com.alibaba.cloud.sentinel.custom.SentinelAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-06-13 20:01:13.750 INFO 19824 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-06-13 20:01:13.751 INFO 19824 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactiveLoadBalancerConfig' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactiveLoadBalancerConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-06-13 20:01:13.753 INFO 19824 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'deferringLoadBalancerExchangeFilterFunction' of type [org.springframework.cloud.client.loadbalancer.reactive.DeferringLoadBalancerExchangeFilterFunction] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-06-13 20:01:13.853 WARN 19824 --- [ main] c.n.c.sources.URLConfigurationSource : No URLs will be polled as dynamic configuration sources. 2025-06-13 20:01:13.853 INFO 19824 --- [ main] c.n.c.sources.URLConfigurationSource : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath. 2025-06-13 20:01:13.856 WARN 19824 --- [ main] c.n.c.sources.URLConfigurationSource : No URLs will be polled as dynamic configuration sources. 2025-06-13 20:01:13.857 INFO 19824 --- [ main] c.n.c.sources.URLConfigurationSource : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath. 2025-06-13 20:01:15.133 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [After] 2025-06-13 20:01:15.133 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Before] 2025-06-13 20:01:15.133 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Between] 2025-06-13 20:01:15.133 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Cookie] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Header] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Host] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Method] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Path] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Query] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [ReadBody] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [RemoteAddr] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [Weight] 2025-06-13 20:01:15.134 INFO 19824 --- [ main] o.s.c.g.r.RouteDefinitionRouteLocator : Loaded RoutePredicateFactory [CloudFoundryRouteService] 2025-06-13 20:01:15.155 INFO 19824 --- [ main] c.a.c.s.g.s.SentinelSCGAutoConfiguration : [Sentinel SpringCloudGateway] using AnonymousBlockRequestHandler, responseStatus: 419, responseBody: 限流了 2025-06-13 20:01:15.155 INFO 19824 --- [ main] c.a.c.s.g.s.SentinelSCGAutoConfiguration : [Sentinel SpringCloudGateway] register SentinelGatewayFilter with order: -2147483648 2025-06-13 20:01:15.300 INFO 19824 --- [ main] c.a.c.s.g.s.SentinelSCGAutoConfiguration : [Sentinel SpringCloudGateway] register SentinelGatewayBlockExceptionHandler 2025-06-13 20:01:15.314 INFO 19824 --- [ main] o.s.s.c.ThreadPoolTaskScheduler : Initializing ExecutorService 'Nacos-Watch-Task-Scheduler' 2025-06-13 20:01:16.278 INFO 19824 --- [ main] o.s.b.web.embedded.netty.NettyWebServer : Netty started on port(s): 9000 2025-06-13 20:01:16.820 INFO 19824 --- [ main] c.a.c.n.registry.NacosServiceRegistry : nacos registry, DEFAULT_GROUP gateway 192.168.2.116:9000 register finished 2025-06-13 20:01:16.836 INFO 19824 --- [ main] com.example.GatewayApplication : Started GatewayApplication in 4.932 seconds (JVM running for 5.764) INFO: Sentinel log output type is: file INFO: Sentinel log charset is: utf-8 INFO: Sentinel log base directory is: C:\Users\COMBATZONE\logs\csp\ INFO: Sentinel log name use pid is: false 2025-06-13 20:01:37.314 INFO 19824 --- [ctor-http-nio-2] c.netflix.config.ChainedDynamicProperty : Flipping property: service1.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647 2025-06-13 20:01:37.334 INFO 19824 --- [ctor-http-nio-2] c.netflix.loadbalancer.BaseLoadBalancer : Client: service1 instantiated a LoadBalancer: DynamicServerListLoadBalancer:{NFLoadBalancer:name=service1,current list of Servers=[],Load balancer stats=Zone stats: {},Server stats: []}ServerList:null 2025-06-13 20:01:37.340 INFO 19824 --- [ctor-http-nio-2] c.n.l.DynamicServerListLoadBalancer : Using serverListUpdater PollingServerListUpdater 2025-06-13 20:01:37.354 INFO 19824 --- [ctor-http-nio-2] c.netflix.config.ChainedDynamicProperty : Flipping property: service1.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647 2025-06-13 20:01:37.355 INFO 19824 --- [ctor-http-nio-2] c.n.l.DynamicServerListLoadBalancer : DynamicServerListLoadBalancer for client service1 initialized: DynamicServerListLoadBalancer:{NFLoadBalancer:name=service1,current list of Servers=[192.168.2.116:9001],Load balancer stats=Zone stats: {unknown=[Zone:unknown; Instance count:1; Active connections count: 0; Circuit breaker tripped count: 0; Active connections per server: 0.0;] },Server stats: [[Server:192.168.2.116:9001; Zone:UNKNOWN; Total Requests:0; Successive connection failure:0; Total blackout seconds:0; Last connection made:Thu Jan 01 08:00:00 CST 1970; First connection made: Thu Jan 01 08:00:00 CST 1970; Active Connections:0; total failure count in last (1000) msecs:0; average resp time:0.0; 90 percentile resp time:0.0; 95 percentile resp time:0.0; min resp time:0.0; max resp time:0.0; stddev resp time:0.0] ]}ServerList:com.alibaba.cloud.nacos.ribbon.NacosServerList@593421ee 2025-06-13 20:01:38.345 INFO 19824 --- [erListUpdater-0] c.netflix.config.ChainedDynamicProperty : Flipping property: service1.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647 分析一下日志
06-14
Mapped [Route{id='order-route'}] to GatewayFilterChain 2023-XX-XX XX:XX:XX.XXX INFO o.s.c.g.f.AdaptCachedBodyGlobalFilter Global filters initialized: 12 in total ``` **关键点**： - `Routes: [id: ...
黑马旅游网项目总结与完善后端（非maven构建）
monkeylvjava
12-12 2981
项目介绍：仿黑马旅游网，项目不是用maven构建的项目，数据库连接池使用的是c3p0不是druid，操作操作sql用的不是jdbcTemplate而是Apache的DBUtlis工具，json工具用的是阿里的fastjson，redis并没有用到，后期学习了但是，确实不错！后期对项目进行了完善，其实只要认真学完了黑马教程的这期案例，尽管后面没有完善，后期所有的分析设计都和前面的大同小异。 我的完善...
MacOS 使用go-cqhttp时出现connect: no route to host错误的解决方法
jes5a的博客
08-19 1897
在MacOS使用go-cqhttp时遇到的某种错误的解决方法
intellij start failed no route to host
HarretLee的专栏
09-12 924
google结果：https://intellij-support.jetbrains.com/hc/en-us/articles/360007568559https://www.jetbrains.com/help/idea/tuning-the-ide.html?_ga=2.86198555.204967701.1599821395-121923466.1599821395#system-directory Resolution Please try the following steps one
关于启动hive时异常：Caused by: java.net.NoRouteToHostException: 没有到主机的路由
derriklove的博客
06-28 2708
启动hive时我们会遇到路由器无法连接问题，这时首先最可能的问题是防火墙打开了，这时只要去关掉就可以了，自行百度很简单。 另外一种问题可能就是我们ip地址问题了，这是我们先启动Hadoop所有集群：start-all.sh, 看是否有5个进程显示，如果缺少就可能是我们i的ip地址发生了改变，这时，我们就要修改Hadoop-env.sh文件， cd ~/hadoop/etc/hadoop vi hadoop-env.sh 更改我们的ip地址就行了。 ...
MacOS下的IntelliJ IDEA突然无法访问本机的虚拟机
oarsman的专栏
03-21 570
挠了半天头，又觉得是程序的问题，但是程序明明没有动过啊，于是试着在idea的terminal里面ping了一下，果然有问题，idea 报告“ping: sendto: No route to host” 路由不可达。今天在开发的过程中，突然遇到一个怪事，之前运行的好好的程序，突然间报无法连接redis服务器，一开始以为是网络问题，在OS的terminal里又是ping 又是telnet的，一切正常，可是程序就是连不上。于是，破案了啊，打开IDEA的权限，一切终于恢复了正常。
Mac下 查询网络ip状态的原理与指令
qq_42603181的博客
10-11 2341
操作系统拥有一套通用的实用程序来查明本地主机的有线或者无线链路状态和IP的连接情况。如果本机有IP连接，那么就意味着有线或者无线是正常工作的。在Mac OS X系统中，有以下几个实用的程序来确认连接状态： ifconfig: 查找本机IP地址和网络接口。 netstat: 使用-r来找到特定网络接口的默认网关。 ping: 用来测试本机之间的端对端的IP连接。 arp: 管理本地的ARP缓存。 以下是连接状态和IP连接的例子： 打开Terminal（译者附：可以通过Spotlight或者实用工具->终
该怎么解决no route to host
热门推荐
fygkchina的专栏
12-06 22万+
出现No route to host 的时候，有如下几种可能： 1、对方的域名确实不通 2、本机自己开了防火墙 3、本机的etc/hosts 里面没有配置本机的机器名和ip（可能性最大） 其中第三点是最猫腻的，在不配置的时候是间断性的（可能1个月都正常，然后突然几天不正常）。修改方案如下： 在结尾加上：机器名和机器ip（用空格隔开） 扩展资料： # telnet虚拟机N...
mac ping: sendto: Host is down PING不通别人的ip，可以ping通路由器  
weixin_33897722的博客
09-01 1万+
mac ping: sendto: Host is down PING不通别人的ip，可以ping通路由器 PING 192.168.1.131 (192.168.1.131): 56 data bytesRequest timeout for icmp_seq 0Request timeout for icmp_seq 1Request timeout for icmp...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值