Finding process using ports

To find out which process is using port number 35541 in a CentOS 7 system (or any Linux distribution), you can use the following methods:

1. Using lsof (List Open Files)

The lsof command can list all open files and network connections, and you can filter by the specific port:

bash 复制代码
sudo lsof -i :35541

This will show the process that is using port 35541. The output will contain columns for the command, PID (process ID), and other information.

2. Using netstat

If netstat is installed, you can use it to check for connections on a specific port:

bash 复制代码
sudo netstat -tuln | grep 35541

This will show which process is listening on that port. If you need the process ID (PID), use the following command:

bash 复制代码
sudo netstat -tulnp | grep 35541

3. Using ss (Socket Statistics)

The ss command is often recommended as a modern replacement for netstat:

bash 复制代码
sudo ss -tuln | grep 35541

To include the process ID:

bash 复制代码
sudo ss -tulnp | grep 35541

4. Using fuser

You can also use fuser, which shows which processes are using files or sockets:

bash 复制代码
sudo fuser 35541/tcp

35541/tcp: 30408

Using fuser to identify the process occupying the port and then restarting it is an effective approach to address such conflicts.

This will return the process ID (PID) that is using the port.

Once you get the PID, you can get more information about the process by running:

bash 复制代码
ps -p <PID>

Replace <PID> with the actual process ID obtained from one of the above methods.

If netstat didn't show the process as listening on port 35541, then it's likely that the port was being used by a client connection rather than a server process.

In TCP/IP networking, a process can bind to a local ephemeral port when making outbound connections as a client. The fact that port 35541 was in use by process 30408 suggests that it was likely a client-side connection, where the process was using 35541 as the source port for an outbound connection.

Here's a more detailed breakdown:

  • Listening port (server) : The process listens on a specific port, usually waiting for incoming connections. This would show up in netstat as LISTEN if it were a server process.
  • Client-side port : When a process initiates an outgoing TCP connection, the operating system assigns a source port , often from a range of ephemeral ports. These ports are usually dynamically assigned and temporary. The port 35541 was likely used in this capacity by process 30408.

To confirm this hypothesis:

  1. You could check all active connections, not just listening ones:

    bash 复制代码
    sudo netstat -anp | grep 30408

    This would show any connections (both listening and established) made by the process with PID 30408.

  2. Similarly, using ss to list all connections for this process:

    bash 复制代码
    sudo ss -ap | grep 30408

    This should show both inbound and outbound connections, confirming the client-side use of port 35541.

By restarting the process, the client-side connection was reset, likely freeing up the port.

相关推荐
likfishdn几秒前
Linux的文件与目录管理
linux·运维·服务器
chian-ocean20 分钟前
Linux 文件缓冲区:高效数据访问的幕后推手
linux·运维·服务器
加油=^_^=22 分钟前
【Linux】进程优先级 | 进程调度(三)
linux·运维·服务器
吃汤圆的抹香鲸1 小时前
GoLand 安装包 绿色版 Win,Mac,Linux 包含IntelliJ全家桶 专为Go语言设计的集成开发环境(IDE)
linux·windows·macos·go·intellij-idea·go1.19
追寻光1 小时前
Cannot find a valid baseurl for repo: base/7/x86_64
linux
元气满满的热码式1 小时前
Docker数据卷操作实战
linux·运维·docker·云原生·容器
陆沙1 小时前
deepseek-r1-centos-本地服务器配置方法
linux·服务器·centos
吃汤圆的抹香鲸1 小时前
Rider 安装包 绿色版 Win/Mac/Linux 适合.NET和游戏开发者使用 2025全栈开发终极指南:从零配置到企业级实战
linux·运维·windows·sql·游戏·macos·.net
sz66cm2 小时前
Linux基础 -- ARM 32 位架构动态注入代码技术文档
linux·arm开发·架构
Mr.pyZhang4 小时前
Android构建系统 - 04 编译产物
android·linux