bug-linux-win(java.sql.SQLException: null, message from server: “Host ‘192.168.1.66‘ is not allowe)_caused by: java.sql.sqlexception: null, message fr-优快云博客

本文链接：https://blog.youkuaiyun.com/computer408/article/details/123920935

本文档描述了如何在Linux上查看和管理进程，使用`ps`和`kill`命令，以及处理MySQL连接错误。在启动Java应用时，提到了`nohup`的使用，并展示了日志输出，包括SpringBoot应用的启动过程。当遇到`Host '192.168.1.66' is not allowed to connect to this MySQL server`错误时，讨论了可能的解决方案，如检查MySQL用户权限。最后，提到了IP更改可能导致的访问问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

查看进程，经常使用ps axu|grep 应用或者项目名

kill -9 端口号----9强制杀死某进程

确保yml配置了sql所在的电脑ip，linux,win的防火墙关闭了

[root@localhost myproject]# ps axu|grep boot01

root 10385 0.4 17.1 2306596 173868 pts/1 Sl 16:41 0:22 java -jar -Dlogging.file=yyy.log boot01-0.0.1-SNAPSHOT.jar

root 10485 0.0 0.0 112808 968 pts/1 R+ 18:06 0:00 grep --color=auto boot01

[root@localhost myproject]# kill -9 10385

[root@localhost myproject]# ps axu|grep boot01

root 10487 0.0 0.0 112808 968 pts/1 R+ 18:07 0:00 grep --color=auto boot01

[1]+ Killed nohup java -jar -Dlogging.file=yyy.log boot01-0.0.1-SNAPSHOT.jar

nohup java -jar -Dlogging.file=yyy.log boot01-0.0.1-SNAPSHOT.jar &

&必须要

nohup java -jar -Dserver.port=yyy -Dlogging.file=/xx/xx/yyy.log yyy.jar &

nohup java -jar -Dlogging.file=yyy.log boot01-0.0.1-SNAPSHOT.jar &

[root@localhost myproject]# ll

total 29992

-rw-r--r--. 1 root root 30708526 Apr 1 18:00 boot01-0.0.1-SNAPSHOT.jar

[root@localhost myproject]# nohup java -jar -Dlogging.file=yyy.log boot01-0.0.1-SNAPSHOT.jar &

[1] 10491

[root@localhost myproject]# nohup: ignoring input and appending output to ‘nohup.out’

total 29996

-rw-r--r--. 1 root root 30708526 Apr 1 18:00 boot01-0.0.1-SNAPSHOT.jar

-rw-------. 1 root root 1987 Apr 1 18:16 nohup.out

查看日志输出（可以查错）

[root@localhost myproject]# cat nohup.out

. ____ _ __ _ _

/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \

( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \

\\/ ___)| |_)| | | | | || (_| | ) ) ) )

' |____| .__|_| |_|_| |_\__, | / / / /

=========|_|==============|___/=/_/_/_/

:: Spring Boot :: (v2.6.5)

2022-04-01 18:15:54.824 INFO 10491 --- [ main] com.hzit.boot01.Boot01Application : Starting Boot01Application v0.0.1-SNAPSHOT using Java 1.8.0_144 on localhost.localdomain with PID 10491 (/usr/local/myproject/boot01-0.0.1-SNAPSHOT.jar started by root in /usr/local/myproject)

2022-04-01 18:15:54.827 INFO 10491 --- [ main] com.hzit.boot01.Boot01Application : No active profile set, falling back to 1 default profile: "default"

2022-04-01 18:15:59.484 INFO 10491 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8001 (http)

2022-04-01 18:15:59.515 INFO 10491 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]

2022-04-01 18:15:59.529 INFO 10491 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.60]

2022-04-01 18:15:59.939 INFO 10491 --- [ main] o.a.c.c.C.[.[localhost].[/boot01] : Initializing Spring embedded WebApplicationContext

2022-04-01 18:15:59.940 INFO 10491 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 4930 ms

2022-04-01 18:16:03.841 INFO 10491 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path '/actuator'

2022-04-01 18:16:04.104 INFO 10491 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8001 (http) with context path '/boot01'

2022-04-01 18:16:04.186 INFO 10491 --- [ main] com.hzit.boot01.Boot01Application : Started Boot01Application in 10.739 seconds (JVM running for 12.07)

-------------------------------------------------