You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

无法执行killall deluged,deluged服务端口占用及进程操作失败求助

Fixing Deluged Port Conflict & Killall Issues for New Server Setup

Hey there, let's work through these Deluge daemon issues step by step—since you're new to server setup, I'll keep this straightforward so you can get your media download system up and running smoothly.

1. Resolving "Address already in use" Error

The error [Errno 98] Address already in use means another process is hogging port 58846, which Deluged uses for RPC connections. Here's how to fix it:

  • Identify the process using the port
    Run either of these commands to find out which process is occupying port 58846:

    lsof -i :58846
    # Or alternatively
    ss -tulpn | grep 58846
    

    Look for the PID (process ID) in the output—it might be a leftover Deluged process or an unrelated app.

  • Kill the conflicting process
    If it's a Deluged process, use its PID to terminate it (replace <PID> with the actual number from the previous step):

    # First try a graceful shutdown
    sudo kill <PID>
    # If that doesn't work, force terminate it
    sudo kill -9 <PID>
    
  • Switch Deluged to a different port (if needed)
    If another app is using 58846, edit Deluged's core config file to use a new port:

    nano ~/.config/deluge/core.conf
    

    Find the line "daemon_port": 58846 and change the number to something unused (like 58847). Save the file and restart Deluged.

2. Fixing "Operation not permitted" / "no process found" with killall

The killall issues stem from either missing permissions or the process not actually running:

  • Add sudo for elevated permissions
    Deluged might be running under a different user (especially if you launched it with system services earlier). Use sudo to gain the necessary access:

    sudo killall deluged
    
  • Verify if Deluged is actually running
    If you get "no process found", double-check with these commands to confirm the process exists:

    ps aux | grep deluged
    # Or use the port check commands from earlier
    

    If no Deluged process shows up, the port conflict might have come from a stale socket file—delete it with:

    rm ~/.config/deluge/deluged.sock
    

Pro Tip for New Server Admins: Use Systemd to Manage Deluged

Instead of manually starting/killing Deluged, use systemd to make it a persistent, manageable service. This avoids most permission and process lifecycle issues:

  1. Create a systemd service file:
    sudo nano /etc/systemd/system/deluged.service
    
  2. Paste this content (replace your_username with your actual server username):
    [Unit]
    Description=Deluge BitTorrent Daemon
    After=network.target
    
    [Service]
    User=your_username
    Group=your_username
    Type=simple
    ExecStart=/usr/bin/deluged -d
    Restart=on-failure
    RestartSec=5
    TimeoutStopSec=30
    
    [Install]
    WantedBy=multi-user.target
    
  3. Reload systemd and enable the service:
    sudo systemctl daemon-reload
    sudo systemctl enable --now deluged
    
  4. Now you can manage Deluged easily with:
    sudo systemctl start deluged
    sudo systemctl stop deluged
    sudo systemctl restart deluged
    

内容的提问来源于stack exchange,提问作者Hawoona

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.21 07:32:01